WELL · 42-135-43989 · DISTRICT 8

Witcher J. E. 19 #3R

Y

Ector County · Cowden South (Canyon 8790) field · Producing  · Directional

Witcher J. E. 19 #3R (API 42-135-43989) is a well in Ector County operated by Oxy USA Wtp LP, completed June 21, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued October 27, 2023, permitted to 10,257 ft.

Completion filings report 10 formation tops, including Santa Rosa, Yates, Seven Rivers, Queen.

Its lease has reported 819K barrels of oil and 886K mcf of gas since March 2003, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

OXY USA WTP LP

Houston, TX · P-5 Y, filed Sep 4, 2025 · 2,289 permits on file · (713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOXY USA WTP LP
Production reportsOXY USA WTP LPthrough Apr 2026
Latest permitOXY USA WTP LPOct 27, 2023
10,257
total depth, ft
3
permits on file
Oct 27, 2023
last permit issued
Jun 21, 2025
completed
819K
cumulative oil, bbl
886K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2003 THROUGH Jul 2026

Regulatory status · RRC wellbore file

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

Operator's P-5 on the schedule: Active

Surface location

31.856768, -102.419068

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Ector 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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Witcher, J. E. 19 O-10-37061Cowden, South (Canyon 8790)OXY USA WTP LP2819K886KMar 2003 – Jul 2026

Oil, barrels lease total

Last 12 months 40,162 · prior 12 13,163(+205%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 7,328 · prior 12 553(+1225%)

01K2K3K202420252026

Chain of custody

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

  1. 1OXY USA WTP LPMar 2003 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
894843-97DrillOXY USA WTP LPJun 4, 2024Oct 27, 2023Nov 10, 202310,257
894843-98DrillOXY USA WTP LPOct 30, 2023Oct 27, 2023—10,000
894843-99DrillOXY USA WTP LPOct 26, 2023Oct 27, 2023Nov 10, 202310,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-37061————

Formation tops

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

FormationMD ftSubsea
Santa RosaSANTA ROSA BASE1,0881,837
Yates2,88738
Seven Rivers3,110-185
Queen3,675-750
Grayburg4,173-1,248
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO4,595-1,670
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO4,598-1,673
Holt5,583-2,658
Glorieta5,785-2,860
Clear ForkCLEARFORK6,004-3,079
Tubb6,464-3,539

Perforations

Perforated and open-hole intervals.

FromToType
9,0289,903Perforated
9,5819,903Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,69917.51,420 S
9.6255,34812.251,360 S
5.510,2908.751,110 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
00Sep 11, 2025Aug 13, 2025—
00Aug 12, 2025Jul 22, 2025—
00Aug 27, 2024May 29, 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 →

Foster, H.42-135-43981

0.0 KM · Occidental Permian Ltd. · Section with this well →

Santa Rosa1,0991,826
Yates2,89926
Seven Rivers3,123-198
Queen3,679-754
Grayburg4,176-1,251
San Andres4,644-1,719
Holt5,560-2,635
Glorieta5,715-2,790

10 TOPS · FIRST 8

Witcher, J. E.42-135-35568

0.8 KM · Occidental Permian Ltd. · Section with this well →

Rustler1,6601,263
Yates2,820103
Queen3,600-677
Grayburg3,850-927
San Andres4,120-1,197
Glorieta5,835-2,912

Henderson42-135-43485

1.3 KM · Occidental Permian Ltd. · Section with this well →

Santa Rosa3342,593
Yates2,83097
Seven Rivers3,000-73
Queen3,370-443
Grayburg3,640-713
San Andres4,100-1,173
San Andres4,100-1,173
Holt5,100-2,173

16 TOPS · FIRST 8

Foster 842-135-38780

3.2 KM · OXY USA WTP LP · Section with this well →

Yates2,807142
Clear Fork5,346-2,397
Canyon8,657-5,708

Cowden, Elliott F., -A-42-135-34413

3.4 KM · Occidental Permian Ltd. · Section with this well →

Canyon8,456-5,520

Cowden, Elliott F., -B-42-135-34457

3.4 KM · Occidental Permian Ltd. · Section with this well →

Grayburg3,964-1,020
San Andres4,337-1,393
Canyon8,471-5,527
Holt—

Cowden, Elliott F., -B-42-135-31667

3.9 KM · Occidental Permian Ltd. · Section with this well →

Grayburg3,964-1,004
San Andres4,337-1,377
Holt5,325-2,365
Pennsylvanian8,022-5,062
Canyon8,612-5,652
Devonian—

South BR Odessa42-135-43693

4.1 KM · OXY USA Inc. · Section with this well →

Santa Rosa1,2021,754
Yates2,818138
Seven Rivers3,117-161
Queen3,589-633
San Andres4,365-1,409
Holt5,461-2,505
Clear Fork5,855-2,899
Tubb—

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