WELL · 42-007-30718 · DISTRICT 4
Ocker Brothers #3
Aransas County · Ocker (A-4) field · Vertical
Ocker Brothers #3 (API 42-007-30718) is a plugged well in Aransas County, plugged February 10, 1994, last operated by Dinero Oil Corporation.
The RRC has issued 3 drilling permits between 1982 and 1991, permitted to 9,000 ft.
Operator of record
Corpus Chrsti, TX · P-5 Y, filed Dec 3, 1999 · 182 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Dinero Oil Corporation |
| Production reports | none |
| Latest permit | Dinero Oil CorporationFeb 7, 1991 |
- 9,000
- total depth, ft
- 3
- permits on file
- Feb 7, 1991
- last permit issued
- Jan 8, 1986
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 1994
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jan 8, 1986
- Shut in
- —
- Plugged
- Feb 10, 1994
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 2 leases this well is completed on; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Ocker Brothers G-4-138128 | Burgentine Lake, N. (Frio B-4) | Dinero Oil Corporation | 1 | 0 | 0 | Jan 1993 – Apr 1994 |
| — G-4-117299 | — | — | 0 | 0 | 0 | — |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 384134-99 | Recompletion | Dinero Oil Corporation | Feb 1, 1991 | Feb 7, 1991 | Feb 10, 1991 | 8,550 |
| 277186-99 | Recompletion | Callahan, Randall R | May 13, 1985 | Jun 10, 1985 | — | 8,550 |
| 166420-99 | Drill | Kelley & Kerr Drilling Ltd. | Jun 28, 1982 | Jun 28, 1982 | Jun 29, 1982 | 9,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-4-117299 | — | — | — | — |
| — | — G-4-138128 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,372 | 7,376 | Perforated |
| 7,372 | 7,386 | Perforated |
| 7,499 | 7,506 | Perforated |
| 7,500 | 7,504 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,027 | 12.25 | 475 S |
| 2.375 | 7,336 | — | — |
| 4.5 | 8,547 | 7.875 | 320 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 | Jul 1, 1991 | Apr 15, 1991 | Yes |
| 00 | May 21, 1991 | — | — |
| 00 | Apr 8, 1986 | Feb 20, 1986 | Yes |
| 00 | Sep 13, 1985 | Jul 16, 1985 | — |
| 00 | Aug 1, 1985 | — | — |
| 00 | Jan 12, 1984 | Aug 25, 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-007-30718 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-007-30718 → 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/00730718, documented in the API reference.