WELL · 42-135-05538 · DISTRICT 8

TXL -P- #2

N

Ector County · Goldsmith (5600) field  · Vertical

Txl -P- #2 (API 42-135-05538) is a permitted well in Ector County filed by Oxy USA Inc.; no completion report is on file yet.

The RRC has issued one drilling permit, issued June 8, 1989, permitted to 5,800 ft.

It was permitted by Oxy USA Inc. and has since transferred to Cities Service Oil & Gas Corp. on the wellbore schedule.

Its lease has reported 53.1K barrels of oil and 234K mcf of gas since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Cities Service Oil & Gas Corp.

Permitted by OXY USA Inc.; the EWA schedule now lists a different operator.

Tulsa, OK · P-5 Y, filed Jan 13, 1989 · 584 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCities Service Oil & Gas Corp.
Production reportsOctane Energy Operating, LLCthrough Apr 2026
Latest permitOXY USA Inc.Jun 8, 1989

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

5,800
total depth, ft
1
permits on file
Jun 8, 1989
last permit issued
—
completed
53.1K
cumulative oil, bbl
234K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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 lease this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
TXL -P- O-10-19812Goldsmith, N. (San Andres, Con.)Octane Energy Operating, LLC253.1K234KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 918 · prior 12 826(+11%)

0100200300202420252026

Gas, mcf lease total

Last 12 months 2,213 · prior 12 2,258(-2%)

0100200300202420252026

Chain of custody

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

  1. 1OXY USA Inc.Jan 1993 → Dec 2000
  2. 2OXY USA WTP LPJan 2001 → Jun 2023
  3. 3Fivestones Energy LLCJul 2023 → Oct 2025
  4. 4Octane Energy Operating, LLCNov 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
360114-99RecompletionOXY USA Inc.Jun 6, 1989Jun 8, 1989—5,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-19812————

Perforations

Perforated and open-hole intervals.

FromToType
4,2265,768Perforated
5,7155,768Perforated
5,717—Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,51911600 S
25,737——
5.55,8007.875700 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 29, 1993Oct 30, 1992—
00Jul 13, 1989Jun 7, 1989—
00Jan 12, 1984Feb 1, 1963—
00Jan 12, 1984——

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