WELL · 42-301-36897 · DISTRICT 8

Viper 53-47 B #W302HB

Y

Loving County · Phantom (Wolfcamp) field · Shut IN  · Horizontal

Viper 53-47 B #W302HB (API 42-301-36897) is a horizontal well in Loving County operated by Petro-Hunt Permian LLC, completed August 18, 2024 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued April 22, 2024, permitted to 12,248 ft.

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

Its lease has reported 1.04K barrels of oil and 4.13K mcf of gas since August 2024, last reporting in July 2026.

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
12,248
total depth, ft
1
permits on file
Apr 22, 2024
last permit issued
Aug 18, 2024
completed
1.04K
cumulative oil, bbl
4.13K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2024 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 18, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.764431, -103.521581

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
Viper 53-47 B O-10-62338Phantom (Wolfcamp)Petro-Hunt Permian, LLC11.04K4.13KAug 2024 – Jul 2026

Oil, barrels lease total

Last 12 months 1,040 · prior 12 0

05001K1.5K202420252026

Gas, mcf lease total

Last 12 months 4,128 · 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
898980-99DrillPetro-Hunt Permian, LLCApr 18, 2024Apr 22, 2024Jun 3, 202412,248

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-62338————

Formation tops

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

FormationMD ftSubsea
Delaware4,665-1,803
Cherry Canyon5,657-2,795
Brushy Canyon6,844-3,982
Bone Spring8,297-5,435
Wolfcamp11,223-8,361
AtokaATOKA - HIGH PRESSURE——
Bell Canyon——
Pennsylvanian——
Red Bluff——
Strawn——

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,09117.5846 S
9.62511,52612.251,442 S
5.522,7078.54,002 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
00Jan 30, 2025Nov 25, 2024Yes

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 →

Viper 53-47 H42-301-36898

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

Delaware4,671-1,809
Cherry Canyon5,654-2,792
Brushy Canyon6,846-3,984
Bone Spring8,296-5,434
Wolfcamp11,217-8,355
Bell Canyon—
Strawn—
Red Bluff—

10 TOPS · FIRST 8

Viper 53-47 K42-301-36896

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

Delaware4,679-1,817
Cherry Canyon5,660-2,798
Brushy Canyon6,860-3,998
Bone Spring8,316-5,454
3RD BS Sand10,911-8,049
Wolfcamp11,221-8,359
Strawn—
Red Bluff—

11 TOPS · FIRST 8

Viper 53-47 C42-301-36899

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

Delaware4,671-1,809
Cherry Canyon5,664-2,802
Brushy Canyon6,896-4,034
Bone Spring8,318-5,456
Wolfcamp11,223-8,361
Atoka—
Strawn—
Red Bluff—

10 TOPS · FIRST 8

Viper 53-47 L42-301-36900

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

Delaware4,674-1,812
Cherry Canyon5,671-2,809
Brushy Canyon6,863-4,001
Bone Spring8,328-5,466
Wolfcamp11,231-8,369
Strawn—
Red Bluff—
Pennsylvanian—

10 TOPS · FIRST 8

Viper 53-47 O42-301-36813

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

Delaware4,665-1,808
Cherry Canyon5,659-2,802
Brushy Canyon6,841-3,984
Bone Spring8,278-5,421
3RD BS10,597-7,740
Bell Canyon—
Pennsylvanian—
Red Bluff—

10 TOPS · FIRST 8

Viper 53-47 U42-301-36815

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

Delaware4,667-1,810
Cherry Canyon5,656-2,799
Brushy Canyon6,828-3,971
Bone Spring8,281-5,424
Pennsylvanian—
Atoka—
Bell Canyon—
Wolfcamp—

10 TOPS · FIRST 8

Viper 53-47 Q42-301-36812

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

Delaware4,659-1,803
Cherry Canyon5,639-2,783
Brushy Canyon6,842-3,986
Bone Spring8,287-5,431
Wolfcamp—
Pennsylvanian—
Atoka—
Red Bluff—

10 TOPS · FIRST 8

Viper 53-47 W42-301-36811

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

Delaware4,652-1,796
Cherry Canyon5,636-2,780
Brushy Canyon6,827-3,971
Bone Spring8,266-5,410
Pennsylvanian—
Red Bluff—
Strawn—
Atoka—

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