WELL · 42-169-32968 · DISTRICT 8

Exxon A #1

Y

Garza County · Post (Glorieta) field · Producing  · Vertical

Exxon A #1 (API 42-169-32968) is a well in Garza County operated by D & D Enterprises, completed June 5, 1990 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 27, 1990, permitted to 2,700 ft.

It was permitted by Burns, Bill C. and has since transferred to D & D Enterprises on the wellbore schedule.

Completion filings report 4 formation tops, including San Andres, L. San Andres, Glorieta, Clear Fork.

Its lease has reported 7.38K barrels of oil and 760 mcf of gas since January 1993, last reporting in July 2026.

Operator of record

D & D Enterprises

Permitted by Burns, Bill C.; the EWA schedule now lists a different operator.

Post, TX · P-5 Y, filed Apr 4, 2026 · (806) 549-1619

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleD & D Enterprises
Production reportsD & D Enterprisesthrough Apr 2026
Latest permitBurns, Bill C.Feb 27, 1990

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

2,700
total depth, ft
1
permits on file
Feb 27, 1990
last permit issued
Jun 5, 1990
completed
7.38K
cumulative oil, bbl
760
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 5, 1990
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
Exxon "A" O-11-66526Post (Glorieta)D & D Enterprises17.38K760Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 72 · prior 12 66(+9%)

01020202420252026

Chain of custody

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

  1. 1Burns, Bill C.Jan 1993 → Feb 1993
  2. 2Hair, Roger D.Apr 1993 → May 1998
  3. 3Success Oil Company, Inc.Jul 1998 → Sep 2002
  4. 4D & D EnterprisesAug 2008 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
370259-99DrillBurns, Bill C.Feb 26, 1990Feb 27, 1990—2,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-66526————

Formation tops

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

FormationMD ftSubsea
San Andres1,654721
L. San Andres2,202173
Glorieta2,498-123
Clear ForkCLEARFORK2,606-231

Perforations

Perforated and open-hole intervals.

FromToType
2,5072,552Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62531412.25200 S
4.52,6417.875375 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
00Aug 6, 1990Jul 5, 1990Yes
00Jul 20, 1990——

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/16932968, documented in the API reference.