WELL · 42-051-32990 · DISTRICT 3

Coffield B-10 A #5

Y

Burleson County · Milbur SE. (Navarro -A-) field · Producing  · Vertical

Coffield B-10 A #5 (API 42-051-32990) is a well in Burleson County operated by Betro Inc., completed February 17, 1988 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 4, 1987, permitted to 4,000 ft.

It was permitted by Ascent Oil & Gas Corp. and has since transferred to Betro Inc. on the wellbore schedule.

Completion filings report one formation top, including Navarro.

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

Operator of record

Betro Inc.

Permitted by Ascent Oil & Gas Corp.; the EWA schedule now lists a different operator.

Rockdale, TX · P-5 Y, filed Jan 4, 2026 · 68 permits on file · (512) 760-6835

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBetro Inc.
Production reportsBetro, Inc.through Apr 2026
Latest permitAscent Oil & Gas Corp.Nov 4, 1987

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

4,000
total depth, ft
1
permits on file
Nov 4, 1987
last permit issued
Feb 17, 1988
completed
14.9K
cumulative oil, bbl
49.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 17, 1988
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Coffield B-10 "A" O-3-20130Milbur, SE. (Navarro -A-)Betro, Inc.114.9K49.8KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 168 · prior 12 172(-2%)

0102030202420252026

Gas, mcf lease total

Last 12 months 625 · prior 12 788(-21%)

050100202420252026

Chain of custody

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

  1. 1Heartland Resources, Inc.Jan 1993 → Feb 1995
  2. 2Betro, Inc.Mar 1995 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
338022-99DrillAscent Oil & Gas Corp.Oct 28, 1987Nov 4, 1987—4,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-20130————

Formation tops

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

FormationMD ftSubsea
NavarroNAVARRO A3,050-2,514
NavarroNAVARRO B3,248-2,712

Perforations

Perforated and open-hole intervals.

FromToType
3,0503,095Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62517712.25115 S
4.53,3827.875665 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, 1988Jun 13, 1988Yes
00Jun 18, 1988——

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