TEXAS · WELLS · BURLESON COUNTY · MINDY LEASE · API 42-051-32362 · DISTRICT 03
Mindy #2
Burleson County · Big -a- Taylor field · Vertical
Mindy #2 (API 42-051-32362) is a plugged well in Burleson County, plugged March 6, 2009, last operated by Anadarko E&P Company LP.
The RRC has issued 2 drilling permits between 1982 and 1987, permitted to 7,500 ft.
It was permitted by U. S. Operating, Inc. and has since transferred to Anadarko E&P Company LP on the wellbore schedule.
Operator of record
Permitted by U. S. Operating, Inc.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Sep 27, 2012
- Permits on file
- 2,635
- Phone
- (832) 636-3130
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Anadarko E&P Company LP |
| Production reports | none |
| Latest permit | U. S. Operating, Inc.Nov 30, 1987 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,500
- total depth, ft
- 2
- permits on file
- Nov 30, 1987
- last permit issued
- Jun 8, 1983
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2009
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 8, 1983
- Shut in
- —
- Plugged
- Mar 6, 2009
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 |
|---|---|---|---|---|---|---|
| Mindy G-3-106474 | Big -a- Taylor | Anadarko E&P Company LP | 1 | 0 | 0 | Jan 1993 – Mar 2009 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 339385-99 | Recompletion | U. S. Operating, Inc. | Nov 25, 1987 | Nov 30, 1987 | — | 7,200 |
| 176825-99 | Drill | U. S. Operating, Inc. | Nov 9, 1982 | Nov 9, 1982 | — | 7,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jun 8, 1983 | Mindy G-3-106474 | Big -a- Taylor | Anadarko E&P Company LP | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,074 | 7,082 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,149 | 12.25 | 650 S |
| 2.375 | 6,987 | — | — |
| 4.5 | 7,200 | 7.875 | 270 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 12, 1984 | Jul 28, 1983 | — |
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-051-32362 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-051-32362 → 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/05132362, documented in the API reference.