WELL · 42-285-33342 · DISTRICT 2
Big Brushy Unit #1
Lavaca County · Vertical
Big Brushy Unit #1 (API 42-285-33342) is a permitted well in Lavaca County filed by B D Production CO., Inc.; no completion report is on file yet.
The RRC has issued 2 drilling permits between 2006 and 2010, permitted to 6,000 ft.
Completion filings report 3 formation tops, including Miocene (undifferentiated), Vicksburg, Yegua.
Operator of record
Corpus Christ, TX · P-5 Y, filed Nov 4, 2025 · 126 permits on file · (361) 813-5177
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | B D Production Co., Inc.through Apr 2011 |
| Latest permit | B D Production Co., Inc.Jul 14, 2010 |
- 6,000
- total depth, ft
- 2
- permits on file
- Jul 14, 2010
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 148K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2007 THROUGH Feb 2013
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 |
|---|---|---|---|---|---|---|
| Big Brushy Unit G-2-226302 | Hope (Miocene 2780) | B D Production Co., Inc. | 1 | 0 | 148K | Jan 2007 – Feb 2013 |
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.
- 1B D Production Co., Inc.Jan 2007 → Apr 2011
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 698514-99 | Recompletion | B D Production Co., Inc. | Jul 2, 2010 | Jul 14, 2010 | — | 5,550 |
| 627177-99 | Drill | B D Production Co., Inc. | Oct 6, 2006 | Oct 9, 2006 | Nov 6, 2006 | 6,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-226302 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 153 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Miocene (undifferentiated)MIOCENE | 3,300 | -3,147 |
| Vicksburg | 3,400 | -3,247 |
| Yegua | 4,850 | -4,697 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,876 | 2,878 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,021 | 12.25 | 440 S |
| 4.5 | 3,601 | 7.875 | 955 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 | May 21, 2007 | Mar 28, 2007 | Yes |
| 00 | Apr 30, 2007 | — | — |
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-285-33342 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-285-33342 → 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/28533342, documented in the API reference.