WELL · 42-435-36842 · DISTRICT 7

Hill Wess #14

Y

Sutton County · Whitehead (Strawn) field · Producing  · Vertical

Hill Wess #14 (API 42-435-36842) is a well in Sutton County operated by Henry Petroleum LLC, completed August 23, 2004 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 5, 2004, permitted to 9,500 ft.

It was permitted by Range Production Company and has since transferred to Henry Petroleum LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Canyon, Strawn, Mississippian.

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

Operator of record

Henry Petroleum LLC

Permitted by Range Production Company; the EWA schedule now lists a different operator.

Flower Mound, TX · P-5 Y, filed Jun 4, 2026 · (972) 754-6281

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHenry Petroleum LLC
Production reportsHenry Petroleum LLCthrough Mar 2026
Latest permitRange Production CompanyMay 5, 2004

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

9,500
total depth, ft
1
permits on file
May 5, 2004
last permit issued
Aug 23, 2004
completed
0
cumulative oil, bbl
367K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 23, 2004
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hill, Wess G-9-204282Whitehead (Strawn)Henry Petroleum LLC10367KAug 2004 – Jul 2026

Gas, mcf lease total

Last 12 months 1,993 · prior 12 2,390(-17%)

05001K202420252026

Chain of custody

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

  1. 1Range Production CompanyAug 2004 → Jun 2014
  2. 2Range Production Company, LLCJul 2014 → Feb 2015
  3. 3Henry Petroleum LLCMar 2015 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
544996-99DrillRange Production CompanyApr 27, 2004May 5, 2004Aug 4, 20049,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-204282————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON SAND6,130-4,030
StrawnSTRAWN LIME8,280-6,180
MississippianMISS LIME8,730-6,630

Perforations

Perforated and open-hole intervals.

FromToType
8,2848,288Perforated
8,2908,294Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,34311375 S
5.58,8867.875595 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
00Feb 9, 2005Oct 4, 2004Yes
00Nov 23, 2004——

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.

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