WELL · 42-077-33610 · DISTRICT 9

Burmaster #1

Plugged

Clay County · GPK (Lower Atoka) field  · Vertical

Burmaster #1 (API 42-077-33610) is a plugged well in Clay County, plugged July 3, 2013, last operated by Primexx Operating Corporation.

The RRC has issued one drilling permit, issued November 16, 1984, permitted to 6,500 ft.

It was permitted by Emerald Petroleum Corporation and has since transferred to Primexx Operating Corporation on the wellbore schedule.

Completion filings report 4 formation tops, including Smithwick, Caddo, Atoka, Ellenburger.

Its lease has reported 9.66K barrels of oil and 42.5K mcf of gas since January 1993, last reporting in December 2013.

Operator of record

Primexx Operating Corporation

Permitted by Emerald Petroleum Corporation; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed Dec 4, 2025 · 310 permits on file · (214) 369-5909

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePrimexx Operating Corporation
Production reportsPrimexx Operating Corporationthrough Feb 2013
Latest permitEmerald Petroleum CorporationNov 16, 1984

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

6,500
total depth, ft
1
permits on file
Nov 16, 1984
last permit issued
Apr 1, 1985
completed
9.66K
cumulative oil, bbl
42.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2013

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 1, 1985
Shut in
—
Plugged
Jul 3, 2013

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
Burmaster O-13-25322GPK (Lower Atoka)Primexx Operating Corporation19.66K42.5KJan 1993 – Dec 2013

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. 1Fagadau Energy CorporationJan 1993 → Apr 2006
  2. 2Primexx Operating CorporationMay 2006 → Feb 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
258037-99DrillEmerald Petroleum CorporationNov 16, 1984Nov 16, 1984—6,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-25322————

Formation tops

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

FormationMD ftSubsea
Smithwick5,650-4,679
Caddo5,750-4,779
AtokaLOWER ATOKA6,014-5,043
EllenburgerELLENBERGER6,296-5,325

Perforations

Perforated and open-hole intervals.

FromToType
6,0166,040Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62539712.25225 S
4.56,1707.875200 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 14, 1985May 3, 1985—
00Jun 1, 1985——

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