WELL · 42-485-37298 · DISTRICT 9

Burnett S. B. #83

Y

Wichita County · Wichita County Regular field · Shut IN  · Vertical

Burnett S. B. #83 (API 42-485-37298) is a well in Wichita County operated by Olenox Corp., completed June 22, 1981 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued March 9, 1981, permitted to 1,900 ft.

It was permitted by Wallace, W. S. and has since transferred to Olenox Corp. on the wellbore schedule.

Its lease has reported 8.93K barrels of oil and 57 mcf of gas since January 1993, last reporting in July 2026. The lease carries 23 wells, so these are lease totals, not this well alone.

Operator of record

Olenox Corp.

Permitted by Wallace, W. S.; the EWA schedule now lists a different operator.

Austin, TX · P-5 Y, filed Feb 4, 2026 · (432) 923-2201

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOlenox Corp.
Production reportsRay Loveless Enterprises, L.L.C.through Mar 2022
Latest permitWallace, W. S.Mar 9, 1981

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

1,900
total depth, ft
1
permits on file
Mar 9, 1981
last permit issued
Jun 22, 1981
completed
8.93K
cumulative oil, bbl
57
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 22, 1981
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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; they carry 23 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Burnett, S. B. O-13-5713Wichita County RegularOlenox Corp.238.93K57Jan 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. 1Gantt, Joe, PropertiesJan 1993 → Jan 1996
  2. 2MRP Oil Co.Mar 1996 → Sep 1998
  3. 3Jaret Oil Co.Oct 1998 → Nov 2001
  4. 4Tri-Mc Oil Co.Dec 2001 → Nov 2004
  5. 5Well Recycling CompanyFeb 2005 → Feb 2005
  6. 6Leonard Brothers Operating Co.Nov 2009 → Oct 2010
  7. 7American Eagle Operating LLCNov 2010 → Jun 2013
  8. 8RRG Operating, LLCJul 2013 → Nov 2014
  9. 9Ray Loveless Enterprises, L.L.C.Feb 2016 → Mar 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
111292-99DrillWallace, W. S.Mar 9, 1981Mar 9, 1981—1,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-5713————

Perforations

Perforated and open-hole intervals.

FromToType
1,7661,787Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2.3751,785——
4.51,8807.875450 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
00Jan 12, 1984Jul 3, 1981—

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