WELL · 42-301-36909 · DISTRICT 8

Constrictor 53-35 I #B103HC

Y

Loving County · Sandbar (Bone Spring) field · Shut IN  · Horizontal

Constrictor 53-35 I #B103HC (API 42-301-36909) is a horizontal well in Loving County operated by Petro-Hunt Permian LLC, completed June 29, 2025 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued April 22, 2024, permitted to 11,067 ft.

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

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

Operator of record

Petro-Hunt Permian LLC

Dallas, TX · P-5 Y, filed Dec 4, 2025 · 250 permits on file · (432) 251-2097

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetro-Hunt Permian LLC
Production reportsPetro-Hunt Permian, LLCthrough Apr 2026
Latest permitPetro-Hunt Permian, LLCApr 22, 2024
11,067
total depth, ft
2
permits on file
Apr 22, 2024
last permit issued
Jun 29, 2025
completed
0
cumulative oil, bbl
4.14K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2025 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 29, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.792513, -103.521270

OpenStreetMap → ·  Google Maps →

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

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
Constrictor 53-35 I G-10-300317Sandbar (Bone Spring)Petro-Hunt Permian, LLC104.14KJun 2025 – Jul 2026

Gas, mcf lease total

Last 12 months 4,136 · prior 12 0

02K4K6K202420252026

Chain of custody

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

  1. 1Petro-Hunt Permian, LLCApr 2026 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
899013-98DrillPetro-Hunt Permian, LLCOct 16, 2024Apr 22, 2024Apr 6, 202511,067
899013-99DrillPetro-Hunt Permian, LLCApr 18, 2024Apr 22, 2024—9,885

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-300317————

Formation tops

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

FormationMD ftSubsea
Delaware4,724-1,835
Cherry Canyon5,708-2,819
Brushy Canyon6,887-3,998
Bone Spring8,357-5,468
AtokaATOKA - HIGH PRESSURE——
Bell Canyon——
Pennsylvanian——
Red Bluff——
Strawn——
Wolfcamp——

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,08417.5937 S
8.6259,16710.6251,983 S
5.518,1997.8751,264 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 14, 2025Nov 3, 2025Yes

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.

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 neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Constrictor 53-35 H42-301-36908

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,734-1,845
Cherry Canyon5,711-2,822
Brushy Canyon6,877-3,988
Bone Spring8,355-5,466
Pennsylvanian—
Red Bluff—
Strawn—
Wolfcamp—

10 TOPS · FIRST 8

Constrictor 53-35 J42-301-36910

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,731-1,842
Cherry Canyon5,718-2,829
Brushy Canyon6,891-4,002
Bone Spring8,378-5,489
Bell Canyon—
Atoka—
Pennsylvanian—
Red Bluff—

10 TOPS · FIRST 8

Constrictor 53-35 G42-301-36907

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Salado9551,933
Delaware4,735-1,847
Cherry Canyon5,715-2,827
Brushy Canyon6,882-3,994
Bone Spring8,351-5,463
Bell Canyon—
Pennsylvanian—
Red Bluff—

10 TOPS · FIRST 8

Constrictor 53-35 K42-301-37142

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,727-1,838
Cherry Canyon5,723-2,834
Brushy Canyon6,892-4,003
Bone Spring8,376-5,487
2ND BS9,862-6,973
Wolfcamp—
Bell Canyon—
Pennsylvanian—

10 TOPS · FIRST 8

Constrictor 53-35 X42-301-37143

0.0 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,733-1,844
Cherry Canyon5,714-2,825
Brushy Canyon6,896-4,007
Bone Spring8,382-5,493
Red Bluff—
Pennsylvanian—
Bell Canyon—
2ND BS—

10 TOPS · FIRST 8

Constrictor 53-35 D42-301-36904

0.3 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,718-1,829
Cherry Canyon5,681-2,792
Brushy Canyon6,873-3,984
1 BS8,332-5,443
Bone Spring8,332-5,443
2ND BS9,784-6,895
Red Bluff—
Bell Canyon—

10 TOPS · FIRST 8

Constrictor 53-35 C42-301-36903

0.3 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,716-1,827
Cherry Canyon5,678-2,789
Brushy Canyon6,877-3,988
Bone Spring8,331-5,442
1ST BS8,331-5,442
Strawn—
Wolfcamp—
Pennsylvanian—

10 TOPS · FIRST 8

Constrictor 53-35 A42-301-36901

0.3 KM · Petro-Hunt Permian, LLC · Section with this well →

Delaware4,711-1,822
Cherry Canyon5,673-2,784
Brushy Canyon6,863-3,974
Bone Spring8,317-5,428
Red Bluff—
Strawn—
Wolfcamp—
Pennsylvanian—

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