WELL · 42-009-43167 · DISTRICT 9

Richardson Trust Lease #4

Plugged

Archer County · Archer County Regular field  · Vertical

Richardson Trust Lease #4 (API 42-009-43167) is a plugged well in Archer County, plugged July 26, 2018, last operated by Bonfire Operating LLC.

The RRC has issued one drilling permit, issued June 25, 2018, permitted to 1,500 ft.

It was permitted by Bonfire Operating LLC and has since transferred to Bonfire Operating LLC on the wellbore schedule.

Operator of record

Bonfire Operating LLC

Permitted by Bonfire Operating LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitBonfire Operating LLCJun 25, 2018

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

1,500
total depth, ft
1
permits on file
Jun 25, 2018
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Jul 26, 2018

Surface location

33.430072, -98.803322

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Archer County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
841657-99DrillBonfire Operating LLCJun 25, 2018Jun 25, 2018Jul 25, 20181,500

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Richardson Trust Lease42-009-43150

0.3 KM · Bonfire Operating LLC · Section with this well →

Thomas Sand940296
Gunsight1,300-64
Davidson—
Delmar—
Megargel—
Strawn—
Bryson—
Cisco—

10 TOPS · FIRST 8

Steven Atchley Lease42-009-43423

1.0 KM · Guidance Oil DEVELOPERS,INC.(1) · Section with this well →

Gunsight1,132
Ward Sand—
Strawn—
Megargel—
Delmar—
Davidson—
Cisco—
Bryson—

10 TOPS · FIRST 8

Rose Lauster42-009-43259

2.6 KM · Guidance Oil DEVELOPERS,INC.(1) · Section with this well →

Gunsight1,195
Thomas Sand—
Megargel—
Delmar—
Davidson—
Cisco—
Canyon—
Bryson—

10 TOPS · FIRST 8

Klenk42-009-43152

3.1 KM · Palmer, John LLC · Section with this well →

Thomas Sand1,150
Gunsight1,290
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—
Megargel—

10 TOPS · FIRST 8

Kunkel, W.L.42-009-43381

3.1 KM · Olney Oil LLC · Section with this well →

Gunsight1,172
Canyon—
Cisco—
Bryson—
Ward Sand—
Thomas Sand—
Strawn—
Megargel—

10 TOPS · FIRST 8

Klenk42-009-43153

3.2 KM · Palmer, John LLC · Section with this well →

Thomas Sand1,150
Gunsight1,290
Bryson—
Ward Sand—
Strawn—
Megargel—
Delmar—
Davidson—

10 TOPS · FIRST 8

J. T. Richardson42-009-43227

3.5 KM · Palmer, Scott Oil · Section with this well →

Gunsight1,279
Thomas Sand—
Ward Sand—
Strawn—
Megargel—
Delmar—
Davidson—
Cisco—

10 TOPS · FIRST 8

R.E. Harbison42-009-43231

3.8 KM · Myers, James B. · Section with this well →

Thomas Sand1,035254
Gunsight1,390-101
Canyon—
Ward Sand—
Strawn—
Megargel—
Delmar—
Bryson—

10 TOPS · FIRST 8

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