WELL · 42-003-33115 · DISTRICT 8
Deep Rock B #2Y
Andrews County · Shafter Lake (Yates) field · Vertical
Deep Rock B #2Y (API 42-003-33115) is a plugged well in Andrews County, plugged November 24, 1993, last operated by Maralo Inc..
The RRC has issued 2 drilling permits between 1982 and 1988, permitted to 4,600 ft.
Completion filings report 2 formation tops, including Yates, San Andres.
Operator of record
Midland, TX · P-5 Y, filed Apr 5, 1999 · 412 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Maralo Inc. |
| Production reports | Maralo, Inc.through Oct 1993 |
| Latest permit | Maralo, Inc.Jul 27, 1988 |
- 4,600
- total depth, ft
- 2
- permits on file
- Jul 27, 1988
- last permit issued
- Jun 28, 1988
- completed
- 0
- cumulative oil, bbl
- 8.2K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 1993
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 28, 1988
- Shut in
- —
- Plugged
- Nov 24, 1993
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 |
|---|---|---|---|---|---|---|
| Deep Rock "B" G-10-127949 | Shafter Lake (Yates) | Maralo, Inc. | 1 | 0 | 8.2K | Jan 1993 – Nov 1993 |
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.
- 1Maralo, Inc.Jan 1993 → Oct 1993
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 349330-99 | Recompletion | Maralo, Inc. | Jul 25, 1988 | Jul 27, 1988 | — | 4,550 |
| 150456-99 | Drill | Maralo, Inc. | Feb 11, 1982 | Feb 11, 1982 | Mar 14, 1982 | 4,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-10-127949 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 3,184 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Yates | 2,740 | 444 |
| San Andres | 4,227 | -1,043 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,742 | 2,923 | Perforated |
| 4,370 | 4,527 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 365 | 11 | 250 S |
| 2.375 | 4,526 | — | — |
| 5.5 | 4,550 | 7.875 | 1,000 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 | Aug 15, 1988 | Aug 3, 1988 | Yes |
| 00 | Aug 10, 1988 | — | — |
| 00 | Jan 12, 1984 | Jun 16, 1982 | — |
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-003-33115 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-003-33115 → 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/00333115, documented in the API reference.