WELL · 42-391-32862 · DISTRICT 2
O Connor M.V. Estate C #7
Refugio County · Train Wreck (5500) field · Vertical
O Connor M.V. Estate C #7 (API 42-391-32862) is a plugged well in Refugio County, plugged October 4, 2010, last operated by Charro Operating L.L.C..
The RRC has issued one drilling permit, issued August 28, 2008, permitted to 7,000 ft.
Completion filings report 3 formation tops, including Miocene (undifferentiated), Frio, Vicksburg.
Operator of record
Englewood, CO · P-5 Y, filed Feb 4, 2026 · 326 permits on file · (303) 799-9828
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Charro Operating L.L.C. |
| Production reports | Charro Operating, L.L.C.through Jul 2010 |
| Latest permit | Charro Operating, L.L.C.Aug 28, 2008 |
- 7,000
- total depth, ft
- 1
- permits on file
- Aug 28, 2008
- last permit issued
- Sep 23, 2008
- completed
- 0
- cumulative oil, bbl
- 106K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2008 THROUGH Jan 2011
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Sep 23, 2008
- Shut in
- —
- Plugged
- Oct 4, 2010
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 |
|---|---|---|---|---|---|---|
| O'Connor, M.V. Estate "C" G-2-242790 | Train Wreck (5500) | Charro Operating, L.L.C. | 1 | 0 | 106K | Sep 2008 – Jan 2011 |
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.
- 1Charro Operating, L.L.C.Oct 2008 → Jul 2010
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 669264-99 | Drill | Charro Operating, L.L.C. | Aug 18, 2008 | Aug 28, 2008 | Aug 29, 2008 | 7,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-242790 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 72 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Miocene (undifferentiated)MIOCENE | 2,430 | -2,358 |
| Frio | 3,750 | -3,678 |
| Vicksburg | 6,265 | -6,193 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,360 | 5,368 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,330 | 12.25 | 760 S |
| 4.5 | 6,437 | 7.875 | 345 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 21, 2009 | Dec 1, 2008 | Yes |
| 00 | Dec 9, 2008 | — | — |
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-391-32862 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-391-32862 → 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/39132862, documented in the API reference.