TEXAS · WELLS · CULBERSON COUNTY · HH SW 3 LEASE · API 42-109-32855 · DISTRICT 7B

HH SW 3 #5HC

Y

Culberson County · Ford West (Wolfcamp) field · Producing  · Horizontal

HH SW 3 #5HC (API 42-109-32855) is a horizontal well in Culberson County operated by Chevron U. S. A. Inc., completed September 16, 2016 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued April 30, 2015, permitted to 9,762 ft.

Completion filings report 9 formation tops, including Rustler, Castile, Lamar, Bell Canyon.

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

Operator of record

Chevron U. S. A. Inc.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Jan 30, 2026
Permits on file
9,293
Phone
(866) 212-1212

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChevron U. S. A. Inc.
Production reportsChevron U. S. A. Inc.through Apr 2026
Latest permitChevron U. S. A. Inc.Apr 30, 2015
9,762
total depth, ft
2
permits on file
Apr 30, 2015
last permit issued
Sep 16, 2016
completed
0
cumulative oil, bbl
7.49M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2016 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 16, 2016
Shut in
—
Plugged
—

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

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
HH SW 3 G-10-281639Ford, West (Wolfcamp)Chevron U. S. A. Inc.107.49MSep 2016 – Jul 2026

Gas, mcf lease total

Last 12 months 461,083 · prior 12 388,156(+19%)

050K100K202420252026

Chain of custody

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

  1. 1Chevron U. S. A. Inc.Oct 2016 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
806006-98DrillChevron U. S. A. Inc.Dec 11, 2015Apr 30, 2015Feb 12, 201611,000
806006-99DrillChevron U. S. A. Inc.Apr 28, 2015Apr 30, 2015Feb 16, 201611,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 16, 2016HH SW 3 G-10-281639Ford West (Wolfcamp)Chevron U. S. A. Inc.Producing9,762

Formation tops

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

FormationMD ftSubsea
Rustler2283,001
CastileCASTILLE4332,796
Lamar2,259970
Bell Canyon2,291938
Cherry Canyon3,16960
Brushy Canyon4,381-1,152
Bone SpringBONE SPRINGS5,857-2,628
Avalon6,023-2,794
Delaware——
DelawareFORD-DELAWARE——

Perforations

Perforated and open-hole intervals.

FromToType
10,16714,461Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,22217.52,205 S
9.6258,45012.251,565 S
5.514,6758.51,740 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 18, 2017Dec 5, 2016Yes

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