TEXAS · WELLS · GAINES COUNTY · SEMINOLE SAN ANDRES UNIT LEASE · API 42-165-31354 · DISTRICT 7B
Seminole San Andres Unit #3116
Gaines County · Seminole (San Andres) field · Injection · Vertical
Seminole San Andres Unit #3116 (API 42-165-31354) is a well in Gaines County operated by Oxy USA Inc., completed April 4, 2024 and listed as injection on the RRC schedule.
The RRC has issued 2 drilling permits between 1978 and 2011, permitted to 5,607 ft.
It was permitted by Hess Corporation and has since transferred to Oxy USA Inc. on the wellbore schedule.
Completion filings report 5 formation tops, including Red Beds, Yates, Bottom Yates, Queen.
Its lease has reported 280M barrels of oil and 328M mcf of gas since January 1993, last reporting volume in April 2026. The lease carries 710 wells, so these are lease totals, not this well alone.
It holds an active disposal or injection permit, with 150K barrels injected in the 12 months reported through October 2025.
Operator of record
Permitted by Hess Corporation; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jan 26, 2026
- Permits on file
- 3,316
- Phone
- (713) 215-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | OXY USA Inc. |
| Production reports | OXY USA Inc.through Apr 2026 |
| Latest permit | Hess CorporationMar 15, 2011 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 5,607
- total depth, ft
- 2
- permits on file
- Mar 15, 2011
- last permit issued
- Apr 4, 2024
- completed
- 280M
- cumulative oil, bbl
- 328M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 4, 2024
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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 710 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Seminole San Andres Unit O-11-60475 | Seminole (San Andres) | OXY USA Inc. | 710 | 280M | 328M | Jan 1993 – Apr 2026 |
Oil, barrels lease total
Last 12 months 6,894,490 · prior 12 6,103,864(+13%)
Gas, mcf lease total
Last 12 months 7,765,270 · prior 12 7,395,533(+5%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Amerada Hess CorporationJan 1993 → Oct 2006
- 2Hess CorporationNov 2006 → Aug 2017
- 3OXY USA Inc.Sep 2017 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 711347-99 | Recompletion | Hess Corporation | Mar 2, 2011 | Mar 15, 2011 | Feb 22, 2012 | 6,462 |
| 20785-99 | Drill | Amerada Hess Corporation | Mar 17, 1978 | Mar 17, 1978 | Aug 25, 1978 | 5,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 4, 2024 | Seminole San Andres Unit O-11-60475 | Seminole (San Andres) | OXY USA Inc. | Injection | 5,607 |
Formation tops
As filed on W-2/G-1. Subsea from 3,389 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Red Beds | 1,000 | 2,389 |
| Yates | 2,430 | 959 |
| Bottom Yates | 4,180 | -791 |
| Queen | 4,180 | -791 |
| San Andres | 4,595 | -1,206 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,120 | 5,296 | Perforated |
| 5,334 | 5,480 | Open hole |
| 5,335 | 5,530 | Open hole |
| 5,390 | 5,560 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 299 | 13.75 | 300 S |
| 7 | 5,334 | 8.75 | 1,700 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Mar 21, 2025 | Apr 30, 2024 | — |
| 00 | Dec 6, 2021 | Nov 11, 2021 | — |
| 00 | Mar 25, 2020 | Oct 23, 2019 | — |
| 00 | Nov 26, 2012 | Jun 6, 2012 | — |
| 00 | Jan 12, 1984 | Oct 4, 1978 | — |
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.
- Wellbore filings for 42-165-31354 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-165-31354 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its search.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 150K
- bbl, last 12 reported months
- 1.58M
- bbl, all reported
- Oct 2025
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000104113 | H-1 Injection | Active | 10,000 | 2,200 | 4,741–6,462 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 149,584 · prior 12 111,513(+34%)
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/16531354, documented in the API reference.