WELL · 42-297-33009 · DISTRICT 2

Sanger Heirs #01

Y

Live Oak County · Cloeter (7300) field · Temp Abandoned  · Vertical

Sanger Heirs #01 (API 42-297-33009) is a well in Live Oak County operated by Anderson Petro-Equipment Inc., completed March 12, 1997 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued April 28, 1982, permitted to 7,750 ft.

It was permitted by Hilty Interests, Inc. and has since transferred to Anderson Petro-Equipment Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Queen City, Wilcox.

No lease production has been reported under this well’s leases.

Operator of record

Anderson Petro-Equipment Inc.

Permitted by Hilty Interests, Inc.; the EWA schedule now lists a different operator.

Montgomery, TX · P-5 Y, filed Nov 4, 2025 · 15 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAnderson Petro-Equipment Inc.
Production reportsAnderson Petro-Equipment, Inc.through Feb 2004
Latest permitHilty Interests, Inc.Apr 28, 1982

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

7,750
total depth, ft
1
permits on file
Apr 28, 1982
last permit issued
Mar 12, 1997
completed
0
cumulative oil, bbl
405K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 12, 1997
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sanger Heirs G-2-100913Cloeter (7300)Anderson Petro-Equipment, Inc.10405KJan 1993 – Jul 2026

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Alyndson Oil & Gas Inc.Jan 1993 → Jun 1995
  2. 2Anderson Petro-Equipment, Inc.Jul 1995 → Feb 2004

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
158430-99DrillHilty Interests, Inc.Apr 28, 1982Apr 28, 1982—7,750

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-100913————

Formation tops

As filed on W-2/G-1. Subsea from 450 ft elevation.Download CSV →

FormationMD ftSubsea
Queen City5,900-5,450
Wilcox7,298-6,848

Perforations

Perforated and open-hole intervals.

FromToType
7,3017,358Perforated
7,3587,369Perforated
7,3677,371Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62553712.25310 S
2.3757,204——
4.57,7027.875500 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jun 27, 1997Mar 27, 1997—
00Dec 8, 1995Aug 31, 1995—
00Jan 12, 1984Jun 18, 1982—

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/29733009, documented in the API reference.