TEXAS · WELLS · LOVING COUNTY · BIG HORN 57-1-11 LEASE · API 42-301-33392 · DISTRICT 7B

Big Horn 57-1-11 #1H

Y

Loving County · Phantom (Wolfcamp) field · Producing  · Horizontal

Big Horn 57-1-11 #1H (API 42-301-33392) is a horizontal well in Loving County operated by Bpx Operating Company, completed April 19, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued June 2, 2017, permitted to 10,256 ft.

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

Its lease has reported 77.5K barrels of oil and 388K mcf of gas since September 2017, last reporting volume in April 2026.

Operator of record

BPX Operating Company

Based in
Denver, CO
P-5 status
Active – Extension (X)
P-5 last filed
Jun 24, 2026
Permits on file
1,576
Phone
(720) 439-5104

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBPX Operating Company
Production reportsBPX Operating Companythrough Apr 2026
Latest permitBPX Operating CompanyJun 2, 2017
10,256
total depth, ft
2
permits on file
Jun 2, 2017
last permit issued
Apr 19, 2025
completed
77.5K
cumulative oil, bbl
388K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2025 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 19, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

Surface location

31.984324, -103.924271 NAD27, as filed

31.984449, -103.924750 WGS84

Google Maps ↗

Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Loving County.

Wells nearby

Every well with a location on file around this one, in any state, nearest first.

Loading the wells nearby…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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
Big Horn 57-1-11 G-10-283674Phantom (Wolfcamp)BPX Operating Company177.5K388KSep 2017 – Apr 2026

Gas, mcf lease total

Last 12 months 373,170 · prior 12 14,865

020K40K60K202420252026

Chain of custody

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

  1. 1BPX Operating CompanyApr 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
826911-98DrillBPX Operating CompanyNov 20, 2025Jun 2, 2017Aug 29, 201711,000
826911-99DrillAnadarko E&P Onshore LLCMay 18, 2017Jun 2, 2017Aug 29, 201711,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 19, 2025Big Horn 57-1-11 G-10-283674Phantom (Wolfcamp)BPX Operating CompanyProducing10,256

Formation tops

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

FormationMD ftSubsea
Delaware3,074-193
Bell Canyon3,099-218
Cherry Canyon4,030-1,149
Brushy Canyon5,242-2,361
Bone SpringBONE SPRINGS6,862-3,981
Wolfcamp10,060-7,179
AtokaATOKA - HIGH PRESSURE——
Pennsylvanian——
Red Bluff——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
10,37214,765Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37596017.5977 S
9.6253,15012.25838 S
710,3218.75702 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Dec 5, 2025Oct 21, 2025—
00Apr 10, 2018Feb 14, 2018Yes

Well logs

1 log loaded from the RRC's log index, 1 of it with a digital LAS file, the latest received Sep 28, 2020. Gamma ray. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Gamma RaySpans Bone Spring, WolfcampLAS + TIFF9,400 to 14,905Sep 28, 20201.29 + 6.14

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its search.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbors, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Pillard SWD42-301-34316

1.0 KM · Solaris Water Midstream, LLC · Section with this well →

Delaware3,115-221
Bell Canyon3,147-253
Cherry Canyon4,089-1,195
Bone Spring—
Atoka—
Wolfcamp—
Brushy Canyon—
Pennsylvanian—

10 TOPS · FIRST 8

Red Bluff 13-24A-57-142-301-36914

1.7 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon3,097-220
Delaware3,097-220
Cherry Canyon4,128-1,251
Brushy Canyon5,242-2,365
Bone Spring6,884-4,007
Bone Spring8,159-5,282
Bone Spring8,882-6,005
Wolfcamp—

11 TOPS · FIRST 8

Red Bluff 13-24B-57-142-301-36915

1.7 KM · WPX Energy Permian, LLC · Section with this well →

Delaware3,111-234
Bell Canyon3,111-234
Cherry Canyon4,159-1,282
Brushy Canyon5,245-2,368
Bone Spring6,905-4,028
Bone Spring8,161-5,284
Atoka—
Wolfcamp—

11 TOPS · FIRST 8

Red Bluff 57-T1-1X1242-301-36091

1.7 KM · Mewbourne Oil Company · Section with this well →

Delaware3,103-213
Bell Canyon3,124-234
Cherry Canyon4,046-1,156
Brushy Canyon5,162-2,272
Bone Spring6,913-4,023
Bone Spring7,826-4,936
Bone Spring8,477-5,587
Bone Spring9,751-6,861

10 TOPS · FIRST 8

Red Bluff 57-T1-1X1242-301-36066

1.7 KM · Mewbourne Oil Company · Section with this well →

Delaware3,102-211
Bell Canyon3,122-231
Cherry Canyon4,045-1,154
Brushy Canyon5,158-2,267
Bone Spring6,920-4,029
Bone Spring7,831-4,940
Bone Spring8,474-5,583
Bone Spring—

10 TOPS · FIRST 8

Red Bluff 13-24C-57-142-301-36916

1.7 KM · WPX Energy Permian, LLC · Section with this well →

Delaware3,107-230
Bell Canyon3,107-230
Cherry Canyon4,172-1,295
Brushy Canyon5,251-2,374
Bone Spring6,919-4,042
Bone Spring8,200-5,323
Bone Spring8,951-6,074
Wolfcamp—

10 TOPS · FIRST 8

Red Bluff 57-T1-1X1242-301-36064

1.7 KM · Mewbourne Oil Company · Section with this well →

Delaware3,104-213
Bell Canyon3,124-233
Cherry Canyon4,053-1,162
Brushy Canyon5,154-2,263
Bone Spring6,920-4,029
Bone Spring7,837-4,946
Bone Spring8,481-5,590
Pennsylvanian—

10 TOPS · FIRST 8

Red Bluff 57-T1-1X1242-301-36090

1.7 KM · Mewbourne Oil Company · Section with this well →

Delaware3,107-215
Bell Canyon3,131-239
Cherry Canyon4,049-1,157
Brushy Canyon5,171-2,279
Bone Spring6,916-4,024
Bone Spring7,843-4,951
Bone Spring8,489-5,597
Bone Spring9,760-6,868

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