WELL · 42-399-33450 · DISTRICT 7
Brookshier #1
Runnels County · Vertical
Brookshier #1 (API 42-399-33450) is a plugged well in Runnels County, plugged February 17, 1985, last operated by Olympian Resources, Inc..
The RRC has issued 2 drilling permits between 1985 and 1988, permitted to 2,250 ft.
Completion filings report 3 formation tops, including Coleman Junction, Breckenridge, Serratt.
Its lease has reported 560 barrels of oil since January 1993, last reporting in August 2003.
Operator of record
Austin, TX · P-5 Y, filed Aug 3, 1992 · 2 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | McIver, Terry L.through Nov 1996 |
| Latest permit | Olympian Resources, Inc.May 18, 1988 |
- 2,250
- total depth, ft
- 2
- permits on file
- May 18, 1988
- last permit issued
- —
- completed
- 560
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Feb 17, 1985
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 |
|---|---|---|---|---|---|---|
| Brookshire O-9-12552 | Winick (Serratt) | McIver, Terry L. | 1 | 560 | 0 | Jan 1993 – Aug 2003 |
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.
- 1McIver, Terry L.Mar 1996 → Nov 1996
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 346709-99 | Reenter | Olympian Resources, Inc. | May 18, 1988 | May 18, 1988 | — | 2,250 |
| 264519-99 | Drill | JLC Energy Investment Corp. | Jan 10, 1985 | Jan 17, 1985 | — | 2,200 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-9-12552 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,805 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Coleman Junction | 896 | 909 |
| Breckenridge | 2,069 | -264 |
| Serratt | 2,165 | -360 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,165 | 2,167 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 150 | 12.25 | 100 S |
| 4.5 | 2,222 | 7.875 | 480 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 7, 1988 | Oct 12, 1988 | Yes |
| 00 | Nov 4, 1988 | — | — |
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-399-33450 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-399-33450 → 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/39933450, documented in the API reference.