WELL · 42-109-33135 · DISTRICT 8

HH SW 5 #20HA

Y

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

HH SW 5 #20HA (API 42-109-33135) is a horizontal well in Culberson County operated by Chevron U. S. A. Inc., completed July 12, 2018 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 7, 2017, permitted to 12,000 ft.

Completion filings report 13 formation tops, including Lamar, Bell Canyon, Cherry Canyon, Brushy Canyon.

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

Operator of record

Chevron U. S. A. Inc.

Midland, TX · P-5 Y, filed Nov 4, 2025 · 9,291 permits on file · (800) 231-0623

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.Jul 7, 2017
12,000
total depth, ft
1
permits on file
Jul 7, 2017
last permit issued
Jul 12, 2018
completed
0
cumulative oil, bbl
7.34M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2018 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 12, 2018
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.998286, -104.189153

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Culberson 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
HH SW 5 G-10-284086Ford, West (Wolfcamp)Chevron U. S. A. Inc.107.34MJan 2018 – Jul 2026

Gas, mcf lease total

Last 12 months 382,542 · prior 12 556,569(-31%)

020K40K60K202420252026

Chain of custody

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

  1. 1Chevron U. S. A. Inc.Jul 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
827227-99DrillChevron U. S. A. Inc.May 26, 2017Jul 7, 2017Nov 16, 201712,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-284086————

Formation tops

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

FormationMD ftSubsea
Lamar2,1201,105
Bell Canyon2,1701,055
Cherry Canyon3,054171
Brushy Canyon4,344-1,119
Bone SpringBONE SPRINGS5,819-2,594
Avalon5,855-2,630
Bone SpringFIRST BONE SPRING6,683-3,458
Atoka——
Bone SpringBONE SPRINGS——
Cherry Canyon——
Delaware——
DelawareFORD-DELAWARE——
Mississippian——
Morrow——
Rustler——
Strawn——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
9,44514,134Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3752,16517.52,237 S
9.6258,48512.251,788 S
5.514,3128.52,475 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, 2019Dec 3, 2018—
00Jan 2, 2019Nov 8, 2018—
00Jun 11, 2018Apr 9, 2018Yes

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 →

HH SW 542-109-33130

0.0 KM · Chevron U. S. A. Inc. · Section with this well →

Lamar2,1041,121
Bell Canyon2,1601,065
Cherry Canyon3,034191
Brushy Canyon4,197-972
Rustler—
Morrow—
Mississippian—
Delaware—

14 TOPS · FIRST 8

HH SW 542-109-33129

0.0 KM · Chevron U. S. A. Inc. · Section with this well →

Lamar2,1011,123
Bell Canyon2,1451,079
Cherry Canyon3,028196
Bone Spring6,647-3,423
Bone Spring6,865-3,641
Bone Spring7,229-4,005
Bone Spring8,425-5,201
Strawn—

15 TOPS · FIRST 8

HH SW 542-109-33128

0.0 KM · Chevron U. S. A. Inc. · Section with this well →

Rustler3252,899
Lamar2,0941,130
Bell Canyon2,1491,075
Cherry Canyon2,997227
Brushy Canyon4,172-948
Bone Spring5,783-2,559
Avalon5,835-2,611
Bone Spring6,601-3,377

15 TOPS · FIRST 8

HH SW 542-109-33131

0.3 KM · Chevron U. S. A. Inc. · Section with this well →

Lamar2,1371,101
Bell Canyon2,1711,067
Cherry Canyon3,045193
Brushy Canyon4,163-925
Bone Spring5,819-2,581
Avalon5,908-2,670
Bone Spring6,660-3,422
Delaware—

15 TOPS · FIRST 8

HH SW 542-109-33132

0.4 KM · Chevron U. S. A. Inc. · Section with this well →

Lamar2,1511,087
Bell Canyon2,1791,059
Cherry Canyon2,955283
Brushy Canyon4,140-902
Bone Spring5,874-2,636
Avalon6,040-2,802
Strawn—
Wolfcamp—

14 TOPS · FIRST 8

HH SW 542-109-33133

0.4 KM · Chevron U. S. A. Inc. · Section with this well →

Cherry Canyon3,019219
Bone Spring5,801-2,563
Wolfcamp8,805-5,567
Delaware—
Atoka—
Delaware—
Mississippian—
Morrow—

10 TOPS · FIRST 8

HH SW 542-109-33134

0.4 KM · Chevron U. S. A. Inc. · Section with this well →

Bell Canyon2,2141,023
Cherry Canyon3,085152
Bone Spring5,861-2,624
Wolfcamp8,849-5,612
Morrow—
Rustler—
Strawn—
Atoka—

11 TOPS · FIRST 8

HTX SW DMG SWD Sec 542-109-33985

1.3 KM · Chevron U. S. A. Inc. · Section with this well →

Delaware2,1901,104
Delaware2,304990
Cherry Canyon3,122172
Morrow—
Rustler—
Strawn—
Atoka—
Wolfcamp—

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