WELL · 42-135-20081 · DISTRICT 8

Goldsmith C. A. Etal #1090

Plugged

Ector County · Goldsmith (5600) field  · Vertical

Goldsmith C. A. Etal #1090 (API 42-135-20081) is a plugged well in Ector County, plugged May 19, 2023, last operated by Xto Energy Inc..

The RRC has issued one drilling permit, issued March 30, 2015, permitted to 4,500 ft.

Its 3 leases have reported 41.7M barrels of oil and 73.4M mcf of gas since January 1993, last reporting in July 2026. The leases carry 2,304 wells, so these are lease totals, not this well alone.

Operator of record

XTO Energy Inc.

Based in
Spring, TX
P-5 status
Active – Extension (X)
P-5 last filed
Apr 8, 2026
Permits on file
16,156
Phone
(346) 502-1572

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXTO Energy Inc.
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitXTO Energy Inc.Mar 30, 2015

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

4,500
total depth, ft
1
permits on file
Mar 30, 2015
last permit issued
Aug 26, 1968
completed
41.7M
cumulative oil, bbl
73.4M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 26, 1968
Shut in
—
Plugged
May 19, 2023

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Goldsmith San Andres Unit O-10-2020GoldsmithHilcorp Energy Company72114.8M20.4MJan 1993 – Jul 2026
Goldsmith, C. A., Etal O-10-2100Goldsmith (Clear Fork)Hilcorp Energy Company88418.5M43.1MJan 1993 – Jul 2026
Goldsmith, C. A., Etal O-10-2290Goldsmith (5600)XTO Energy Inc.6998.37M9.94MJan 1993 – Jan 2007

Oil, barrels lease total

Last 12 months 393,598 · prior 12 321,214(+23%)

020K40K60K202420252026

Gas, mcf lease total

Last 12 months 881,375 · prior 12 450,470(+96%)

050K100K150K202420252026

Chain of custody

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

  1. 1Chevron U. S. A. Inc.Jan 1993 → Jul 2004
  2. 2XTO Energy Inc.Aug 2004 → Mar 2025
  3. 3Hilcorp Energy CompanyApr 2025 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
805049-99RecompletionXTO Energy Inc.Mar 26, 2015Mar 30, 2015Apr 2, 20154,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-2020————
—— O-10-2100————
—— O-10-2290————

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,44812.25500 S
5.55,8857.875600 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
00Jul 16, 2015Apr 10, 2015—
00Jan 31, 2007Sep 16, 1968—
00Jan 12, 1984Sep 16, 1968—

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