WELL · 42-237-40538 · DISTRICT 9

Hensley #1

Plugged

Jack County · Jack County Reg field  · Vertical

Hensley #1 (API 42-237-40538) is a plugged well in Jack County, plugged June 14, 2019, last operated by Best Petroleum Explorations Inc..

The RRC has issued one drilling permit, issued May 24, 2019, permitted to 5,000 ft.

It was permitted by Best Petroleum Explorations,Inc. and has since transferred to Best Petroleum Explorations Inc. on the wellbore schedule.

Operator of record

Best Petroleum Explorations Inc.

Permitted by Best Petroleum Explorations,inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitBest Petroleum Explorations,inc.May 24, 2019

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

5,000
total depth, ft
1
permits on file
May 24, 2019
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
Jun 14, 2019

Surface location

33.149271, -98.158076

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Jack 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
853387-99DrillBest Petroleum Explorations,inc.May 22, 2019May 24, 2019Jun 11, 20195,000

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 →

Hall42-237-40543

0.4 KM · Best Petroleum Explorations,inc. · Section with this well →

Weir1,872-574
Village Bend—
Canyon—
Caddo—
Atoka—
Bryson—
Butram—
Strawn—

10 TOPS · FIRST 8

Richards Ranch42-237-40180

0.9 KM · Newark E&P Operating, LLC · Section with this well →

Palo Pinto925347
Strawn1,160112
Caddo4,675-3,403
Atoka4,764-3,492
Butram—
Gunsight—
Bryson—
Weir—

10 TOPS · FIRST 8

Richards Ranch42-237-39661

1.4 KM · FX Energy Operating, LLC · Section with this well →

Pregnant Shale4,922-3,602
Atoka5,009-3,689
Atoka5,009-3,689
Marble Falls5,338-4,018

Stamper-Fowler42-237-39382

1.6 KM · Oakridge Oil and Gas, LP · Section with this well →

Caddo4,610-3,357
Atoka4,995-3,742
Barnett5,659-4,406
Ellenburger5,854-4,601

Richards Ranch42-237-40058

1.6 KM · Newark E&P Operating, LLC · Section with this well →

Palo Pinto928375
Strawn1,165138
Atoka4,747-3,444
Butram—
Bryson—
Caddo—
Canyon—
Gunsight—

10 TOPS · FIRST 8

Richards Ranch42-237-40059

2.2 KM · Newark E&P Operating, LLC · Section with this well →

Palo Pinto889364
Strawn1,118135
Caddo4,733-3,480
Atoka4,770-3,517
Bend5,010-3,757
Marble Falls5,310-4,057
Barnett5,828-4,575
Ellenburger6,058-4,805

Cook42-237-39560

2.3 KM · Swan PC, LP · Section with this well →

Buttram2,361-1,087
Strawn2,476-1,202
Strawn4,415-3,141
Caddo4,655-3,381
Atoka5,001-3,727
Marble Falls5,234-3,960
Comyn5,562-4,288
Forrestburg Lime5,562-4,288

Cook42-237-39328

2.4 KM · Swan PC, LP · Section with this well →

Marble Falls5,230-3,971
Forrestburg Lime5,576-4,317
Barnett5,676-4,417

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