WELL · 42-353-32325 · DISTRICT 7

Ussery #1

Plugged

Nolan County · Triple B (Palo Pinto) field  · Vertical

Ussery #1 (API 42-353-32325) is a plugged well in Nolan County, plugged March 15, 2013, last operated by Bustamante Oil Company.

The RRC has issued one drilling permit, issued January 27, 1995, permitted to 6,900 ft.

It was permitted by Clear Fork, Incorporated and has since transferred to Bustamante Oil Company on the wellbore schedule.

Completion filings report 3 formation tops, including Cisco, Palo Pinto, Caddo.

Its lease has reported 29.4K barrels of oil and 42.6K mcf of gas since March 1995, last reporting in July 2026.

Operator of record

Bustamante Oil Company

Permitted by Clear Fork, Incorporated; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed May 4, 2026 · 4 permits on file · (432) 664-1103

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBustamante Oil Company
Production reportsBustamante Oil Companythrough Aug 2011
Latest permitClear Fork, IncorporatedJan 27, 1995

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

6,900
total depth, ft
1
permits on file
Jan 27, 1995
last permit issued
Mar 6, 1995
completed
29.4K
cumulative oil, bbl
42.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 1995 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 6, 1995
Shut in
—
Plugged
Mar 15, 2013

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
Ussery O-8-27501Triple B (Palo Pinto)Bustamante Oil Company129.4K42.6KMar 1995 – Jul 2026

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. 1Clear Fork, IncorporatedMar 1995 → Jan 2003
  2. 2Sutton Oil Co.Jul 2003 → Jun 2005
  3. 3Bustamante Oil CoJul 2005 → Jul 2006
  4. 4Bustamante Oil CompanyAug 2006 → May 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
432261-99DrillClear Fork, IncorporatedJan 26, 1995Jan 27, 1995Feb 4, 19956,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-27501————

Formation tops

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

FormationMD ftSubsea
CiscoCISCO REEF4,081-1,607
Palo PintoPALO PINTO REEF5,706-3,232
Caddo6,561-4,087

Perforations

Perforated and open-hole intervals.

FromToType
5,7335,738Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62547412.25300 S
5.56,7777.875575 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
00Apr 7, 1995Mar 14, 1995Yes
00Mar 29, 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). 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/35332325, documented in the API reference.