WELL · 42-391-32754 · DISTRICT 2
O Connor M. V. Estate C #6
Refugio County · Train Wreck (6000 Sd.) field · Vertical
O Connor M. V. Estate C #6 (API 42-391-32754) is a plugged well in Refugio County, plugged September 19, 2017, last operated by Charro Operating L.L.C..
The RRC has issued one drilling permit, issued November 28, 2006, permitted to 6,600 ft.
Completion filings report 3 formation tops, including Catahoula, Frio, Vicksburg.
Operator of record
- Based in
- Englewood, CO
- P-5 status
- Active (A)
- P-5 last filed
- Apr 10, 2026
- Permits on file
- 326
- Phone
- (361) 319-3199
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 Jan 2016 |
| Latest permit | Charro Operating, L.L.C.Nov 28, 2006 |
- 6,600
- total depth, ft
- 1
- permits on file
- Nov 28, 2006
- last permit issued
- Nov 20, 2007
- completed
- 0
- cumulative oil, bbl
- 635K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2006 THROUGH Mar 2024
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 20, 2007
- Shut in
- —
- Plugged
- Sep 19, 2017
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-224771 | Train Wreck (6000 Sd.) | Charro Operating, L.L.C. | 1 | 0 | 635K | Dec 2006 – Mar 2024 |
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.Nov 2007 → Jan 2016
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 629543-99 | Drill | Charro Operating, L.L.C. | Nov 27, 2006 | Nov 28, 2006 | Dec 2, 2006 | 6,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-224771 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 64 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,015 | 6,021 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 1,326 | 12.25 | 500 S |
| 8.625 | 1,574 | 12.25 | 585 S |
| 4.5 | 2,830 | 7.875 | 175 S |
| 4.5 | 6,255 | 7.875 | 590 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 14, 2008 | Dec 18, 2007 | — |
| 00 | May 1, 2007 | Jan 26, 2007 | Yes |
| 00 | Feb 26, 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-391-32754 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-391-32754 → 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/39132754, documented in the API reference.