WELL · 42-135-37764 · DISTRICT 8

Tomcat #1

N

Ector County · Jars (Ellenburger) field  · Vertical

Tomcat #1 (API 42-135-37764) is a well in Ector County operated by Oxy USA Wtp LP, completed December 17, 1999.

The RRC has issued 2 drilling permits between 1999 and 2012, permitted to 10,100 ft.

Completion filings report 4 formation tops, including Tubb, Devonian, Fusselman, Ellenburger.

Its 2 leases have reported 293K barrels of oil and 347K mcf of gas since December 1999, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

OXY USA WTP LP

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Oct 16, 2025
Permits on file
2,289
Phone
(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 LPMar 21, 2012
10,100
total depth, ft
2
permits on file
Mar 21, 2012
last permit issued
Dec 17, 1999
completed
293K
cumulative oil, bbl
347K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1999 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 17, 1999
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Tomcat O-10-44710Goldsmith (Devonian)OXY USA WTP LP2153K274KAug 2012 – Jul 2026
Tomcat O-10-36152Jars (Ellenburger)OXY USA WTP LP1140K72.8KDec 1999 – Oct 2014

Oil, barrels lease total

Last 12 months 7,603 · prior 12 8,910(-15%)

05001K202420252026

Gas, mcf lease total

Last 12 months 15,021 · prior 12 16,283(-8%)

01K2K202420252026

Chain of custody

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

  1. 1OXY USA Inc.Dec 1999 → Dec 2001
  2. 2OXY USA WTP LPJan 2002 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
734183-99RecompletionOXY USA WTP LPFeb 17, 2012Mar 21, 2012Apr 16, 20129,000
486806-99DrillOXY USA Inc.Aug 19, 1999Oct 13, 1999Nov 10, 199910,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-36152————
—— O-10-44710————

Formation tops

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

FormationMD ftSubsea
Tubb6,447-3,248
Devonian7,749-4,550
Fusselman8,720-5,521
Ellenburger9,800-6,601

Perforations

Perforated and open-hole intervals.

FromToType
7,9408,875Perforated
9,8009,910Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,53711610 S
5.56,4257.875670 S
5.59,8007.875700 S
5.5—7.875670 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
00Oct 1, 2014Dec 12, 2013—
00Jan 21, 2000Dec 23, 1999Yes
00Jan 14, 2000——

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