TEXAS · WELLS · GAINES COUNTY · API 42-165-01116 · DISTRICT 7B

Amerada Coffey #1

Plugged

Gaines County · Wildcat field  · Vertical

Amerada Coffey #1 (API 42-165-01116) is a plugged well in Gaines County, plugged December 20, 2025, last operated by Oxy USA Inc..

The RRC has issued one drilling permit, issued September 18, 2025, permitted to 5,232 ft.

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

Operator of record

OXY USA Inc.

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

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitOXY USA Inc.Sep 18, 2025

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

5,232
total depth, ft
1
permits on file
Sep 18, 2025
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Dec 20, 2025

Surface location

32.753820, -102.718107

Google Maps ↗

Permit surface location from the RRC GIS record, in Gaines County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
910531-99ReenterOXY USA Inc.Sep 17, 2025Sep 18, 2025—5,232

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbors can.

Section of the neighbors →

Seminole San Andres Unit42-165-38999

0.2 KM · OXY USA Inc. · Section with this well →

Yates3,28642
Seven Rivers3,558-230
Queen4,125-797
San Andres4,868-1,540
Leonard—
Clear Fork—
Glorieta—
Wichita-Albany—

10 TOPS · FIRST 8

Seminole San Andres Unit42-165-39000

0.3 KM · OXY USA Inc. · Section with this well →

Tansill3,041287
Yates3,172156
Seven Rivers3,403-75
Queen3,972-644
Grayburg4,393-1,065
San Andres4,629-1,301
Wichita-Albany—
San Angelo—

10 TOPS · FIRST 8

Seminole San Andres Unit42-165-39001

0.3 KM · OXY USA Inc. · Section with this well →

Yates3,112215
Queen3,910-583
San Andres4,530-1,203
Seven Rivers—
Spraberry—
Wichita-Albany—
San Angelo—
Glorieta—

10 TOPS · FIRST 8

Seminole San Andres Unit42-165-39003

0.6 KM · OXY USA Inc. · Section with this well →

Rustler2,0751,292
Tansill3,068299
Yates3,195172
Seven Rivers3,451-84
Queen4,029-662
Grayburg4,486-1,119
San Andres4,768-1,401
Glorieta—

10 TOPS · FIRST 8

Seminole San Andres Unit42-165-38998

0.6 KM · OXY USA Inc. · Section with this well →

Rustler2,0881,279
Yates3,211156
Seven Rivers3,441-74
Queen4,054-687
Grayburg4,485-1,118
San Andres4,785-1,418
San Angelo—
Wichita-Albany—

10 TOPS · FIRST 8

Seminole San Andres Unit42-165-01852

0.8 KM · OXY USA Inc. · Section with this well →

Tansill3,053777
Yates3,182648
Grayburg4,426-596

Seminole San Andres Unit42-165-01847

0.8 KM · OXY USA Inc. · Section with this well →

Queen3,979
Grayburg4,413
San Andres4,712

Seminole San Andres Unit42-165-31217

0.9 KM · OXY USA Inc. · Section with this well →

Yates3,143236
Queen3,947-568
Grayburg4,380-1,001

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