WELL · 42-301-32586 · DISTRICT 8

Bullhead State 55-1-44 #2H

N

Loving County · Phantom (Wolfcamp) field  · Horizontal

Bullhead State 55-1-44 #2H (API 42-301-32586) is a horizontal well in Loving County operated by Shell Western E&P, completed October 7, 2015.

The RRC has issued one drilling permit, issued May 7, 2015, permitted to 11,500 ft.

Completion filings report 10 formation tops, including Delaware, Bell Canyon, Cherry Canyon, Brushy Canyon.

No lease production has been reported under this well’s leases.

Operator of record

Shell Western E&P

Based in
Houston, TX
P-5 status
Delinquent (D)
P-5 last filed
Jan 4, 2021
Permits on file
1,756
Phone
(832) 337-0694

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleShell Western E&P
Production reportsPdeh LLCthrough Apr 2026
Latest permitShell Western E&PMay 7, 2015

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

11,500
total depth, ft
1
permits on file
May 7, 2015
last permit issued
Oct 7, 2015
completed
0
cumulative oil, bbl
1.68M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2015 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 7, 2015
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
Bullhead State 55-1-44 G-10-287565Phantom (Wolfcamp)Pdeh LLC101.68MOct 2015 – Jul 2026
Bullhead State 55-1-44 O-10-47186Phantom (Wolfcamp)Shell Western E&P100Oct 2015 – Mar 2020

Gas, mcf lease total

Last 12 months 57,629 · prior 12 81,822(-30%)

05K10K15K202420252026

Chain of custody

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

  1. 1Shell Western E&POct 2015 → Aug 2021
  2. 2Pdeh LLCSep 2021 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
806068-99DrillShell Western E&PApr 29, 2015May 7, 2015Jun 22, 201511,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-287565————
—— O-10-47186————

Formation tops

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

FormationMD ftSubsea
Delaware3,640-790
Bell Canyon3,679-829
Cherry Canyon4,571-1,721
Brushy Canyon5,794-2,944
Bone SpringBONE SPRINGS7,554-4,704
Wolfcamp10,623-7,773
AtokaATOKA - HIGH PRESSURE——
Pennsylvanian——
Red Bluff——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
11,16115,015Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6253,54712.25896 S
711,0808.75587 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 26, 2019Aug 19, 2019Yes
00Jan 26, 2016Dec 17, 2015Yes

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) and the University Lands library. 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/30132586, documented in the API reference.