WELL · 42-363-35700 · DISTRICT 7
M. C. Kay #3
Palo Pinto County · Ringo (Congl.) field · Vertical
M. C. Kay #3 (API 42-363-35700) is a plugged well in Palo Pinto County, plugged December 18, 2020, last operated by Crystal River Oil & Gas LLC.
The RRC has issued one drilling permit, issued November 5, 2007, permitted to 4,000 ft.
Completion filings report 2 formation tops, including Ringo (Congl.), Ringo (Conlermate).
Operator of record
Snowmass Vlg., CO · P-5 Y, filed Oct 4, 2025 · 6 permits on file · (970) 309-1535
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Crystal River Oil & Gas LLC |
| Production reports | Crystal River Oil & Gas LLCthrough Aug 2015 |
| Latest permit | Crystal River Oil & Gas LLCNov 5, 2007 |
- 4,000
- total depth, ft
- 1
- permits on file
- Nov 5, 2007
- last permit issued
- Apr 16, 2008
- completed
- 0
- cumulative oil, bbl
- 13.2K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Dec 2020
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Apr 16, 2008
- Shut in
- —
- Plugged
- Dec 18, 2020
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 |
|---|---|---|---|---|---|---|
| M. C. Kay G-8-253888 | Ringo (Congl.) | Crystal River Oil & Gas LLC | 1 | 0 | 13.2K | Apr 2008 – Dec 2020 |
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.
- 1Crystal River Oil & Gas LLCApr 2008 → Aug 2015
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 648568-99 | Drill | Crystal River Oil & Gas LLC | Oct 26, 2007 | Nov 5, 2007 | Mar 20, 2008 | 4,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-253888 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,070 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Ringo (Congl.) | 3,550 | -2,480 |
| Ringo (Conlermate) | 3,550 | -2,480 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,561 | 3,664 | Perforated |
| 3,590 | 3,594 | Perforated |
| 3,661 | 3,664 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 157 | 12.25 | 110 S |
| 4.5 | 3,750 | 7.875 | 225 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 | Oct 1, 2012 | Feb 6, 2012 | — |
| 00 | Jul 26, 2010 | Feb 4, 2009 | Yes |
| 00 | Jan 6, 2010 | — | — |
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-363-35700 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-363-35700 → 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/36335700, documented in the API reference.