WELL · 42-133-37890 · DISTRICT 7

Burns #1

N

Eastland County · Reb (Marble Falls) field  · Vertical

Burns #1 (API 42-133-37890) is a well in Eastland County operated by Byrne Oil Company, completed August 31, 2004.

The RRC has issued one drilling permit, issued July 21, 2004, permitted to 3,850 ft.

It was permitted by Byrne, Robert E. and has since transferred to Byrne Oil Company on the wellbore schedule.

Completion filings report 2 formation tops, including Caddo, Ranger.

Its 2 leases have reported 1.94K barrels of oil and 85.9K mcf of gas since September 2004, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Byrne Oil Company

Permitted by Byrne, Robert E.; the EWA schedule now lists a different operator.

Lubbock, TX · P-5 Y, filed Sep 4, 2025 · 42 permits on file · (254) 488-1053

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleByrne Oil Company
Production reportsByrne Oil Companythrough Apr 2026
Latest permitByrne, Robert E.Jul 21, 2004

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

3,850
total depth, ft
1
permits on file
Jul 21, 2004
last permit issued
Aug 31, 2004
completed
1.94K
cumulative oil, bbl
85.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 31, 2004
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Burns G-8-281325Reb (Marble Falls)Byrne Oil Company1014.2KSep 2016 – Jul 2026
Burns O-8-29448Reb (Marble Falls)Byrne Oil Company11.94K71.6KSep 2004 – Jul 2017

Gas, mcf lease total

Last 12 months 1,094 · prior 12 1,224(-11%)

050100150202420252026

Chain of custody

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

  1. 1Byrne, Robert E.Sep 2004 → Jan 2005
  2. 2Byrne Oil CompanyFeb 2005 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
548453-99DrillByrne, Robert E.Jul 19, 2004Jul 21, 2004—3,850

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-281325————
—— O-8-29448————

Formation tops

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

FormationMD ftSubsea
Caddo2,746-1,286
Ranger2,850-1,390

Perforations

Perforated and open-hole intervals.

FromToType
2,7612,796Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62516112.2595 S
4.52,8707.875120 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
00Nov 29, 2016Sep 20, 2016—
00Dec 28, 2004Sep 15, 2004Yes
00Oct 12, 2004——

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