WELL · 42-443-30549 · DISTRICT 7

Mitchell 9 #4

Plugged

Terrell County · Pakenham (Thrusted) field  · Vertical

Mitchell 9 #4 (API 42-443-30549) is a plugged well in Terrell County, plugged March 14, 2018, last operated by Oxy USA Inc..

The RRC has issued one drilling permit, issued February 13, 1995, permitted to 13,000 ft.

It was permitted by Chevron U. S. A. Inc. and has since transferred to Oxy USA Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Wolfcamp, Strawn.

Operator of record

OXY USA Inc.

Permitted by Chevron U. S. A. Inc.; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Jan 26, 2026
Permits on file
3,316
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOXY USA Inc.
Production reportsOXY USA Inc.through May 2017
Latest permitChevron U. S. A. Inc.Feb 13, 1995

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

13,000
total depth, ft
1
permits on file
Feb 13, 1995
last permit issued
Jul 19, 1995
completed
0
cumulative oil, bbl
2.76M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 1995 THROUGH Mar 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 19, 1995
Shut in
—
Plugged
Mar 14, 2018

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
Mitchell 9 G-9-155264South Branch (Wolfcamp)OXY USA Inc.102.76MJun 1995 – Mar 2018

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Chevron U. S. A. Inc.Jun 1995 → Aug 1999
  2. 2Athanor Texas Inc.Sep 1999 → Dec 2002
  3. 3Nuevo Texas Inc.Jan 2003 → Dec 2004
  4. 4PXP Texas Inc.Jan 2005 → Sep 2006
  5. 5Vintage Petroleum, LLCOct 2006 → Mar 2008
  6. 6OXY USA Inc.Apr 2008 → May 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
432769-99DrillChevron U. S. A. Inc.Feb 10, 1995Feb 13, 1995Apr 17, 199513,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-155264————

Formation tops

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

FormationMD ftSubsea
WolfcampWOLFCAMP SHALE5,355-2,680
WolfcampWOLFCAMP SAND7,660-4,985
Strawn11,378-8,703

Perforations

Perforated and open-hole intervals.

FromToType
10,65011,864Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,30017.51,300 S
9.6255,20012.25500 S
712,2008.51,260 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 27, 1995Aug 18, 1995Yes
00Sep 13, 1995——

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