WELL · 42-203-31595 · DISTRICT 6
Abercrombie Oil Unit #3
Harrison County · Vertical
Abercrombie Oil Unit #3 (API 42-203-31595) is a permitted well in Harrison County filed by Rbd-Shelby Agency; no completion report is on file yet.
The RRC has issued 2 drilling permits between 1987 and 1988, permitted to 6,300 ft.
Completion filings report one formation top, including Travis Peak.
Operator of record
Dallas, TX · P-5 Y, filed Jul 8, 1994 · 70 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Shelby Operating Companythrough Apr 2026 |
| Latest permit | RBD-Shelby AgencySep 30, 1988 |
- 6,300
- total depth, ft
- 2
- permits on file
- Sep 30, 1988
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 505K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 |
|---|---|---|---|---|---|---|
| Abercrombie G-6-124561 | Waskom (Travis Peak 6150) | Shelby Operating Company | 1 | 0 | 505K | Jan 1993 – Jul 2026 |
Gas, mcf lease total
Last 12 months 8,539 · prior 12 12,780(-33%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1RBD-Shelby AgencyFeb 1993 → Dec 1993
- 2Shelby Operating CompanyJan 1994 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 351831-99 | Recompletion | RBD-Shelby Agency | Sep 30, 1988 | Sep 30, 1988 | — | 6,300 |
| 327663-99 | Drill | RBD-Shelby Agency | Mar 12, 1987 | Mar 27, 1987 | May 13, 1987 | 6,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-6-124561 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 273 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Travis Peak | 6,098 | -5,825 |
| Travis Peak | 6,196 | -5,923 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,098 | 6,106 | Perforated |
| 6,200 | 6,210 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 551 | 12.25 | 350 S |
| 5.5 | 6,278 | 7.875 | 800 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 | Jan 18, 1989 | Nov 9, 1988 | — |
| 00 | Jul 31, 1987 | Jun 18, 1987 | Yes |
| 00 | Jul 18, 1987 | — | — |
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-203-31595 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-203-31595 → scanned completion filings
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/20331595, documented in the API reference.