WELL · 42-461-33973 · DISTRICT 7
Arco AB 3 #2
Upton County · Webb Ray field · Vertical
Arco AB 3 #2 (API 42-461-33973) is a plugged well in Upton County, plugged September 18, 2019, last operated by Sabine Oil & Gas Corporation.
The RRC has issued one drilling permit, issued August 21, 1999, permitted to 2,200 ft.
It was permitted by Arco Permian and has since transferred to Sabine Oil & Gas Corporation on the wellbore schedule.
Completion filings report 6 formation tops, including Yates, Grayburg, Wolfcamp, Devonian.
Operator of record
Permitted by Arco Permian; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Feb 3, 2025
- Permits on file
- 466
- Phone
- (832) 242-9600
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Sabine Oil & Gas Corporation |
| Production reports | none |
| Latest permit | Arco PermianAug 21, 1999 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 2,200
- total depth, ft
- 1
- permits on file
- Aug 21, 1999
- last permit issued
- Aug 26, 1999
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 1999 THROUGH Jan 2020
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Aug 26, 1999
- Shut in
- —
- Plugged
- Sep 18, 2019
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Arco "AB" 3 O-9-14919 | Webb Ray | Sabine Oil & Gas Corporation | 1 | 0 | 0 | Oct 1999 – Jan 2020 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 483948-99 | Drill | Arco Permian | Apr 19, 1999 | Aug 21, 1999 | Jun 17, 1999 | 2,200 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-9-14919 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,583 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,982 | 1,996 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 454 | 11 | 380 S |
| 4.5 | 2,188 | 7.875 | 500 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Nov 22, 1999 | Oct 15, 1999 | Yes |
| 00 | Oct 27, 1999 | — | — |
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-461-33973 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-461-33973 → scanned completion filings
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/46133973, documented in the API reference.