WELL · 42-485-44106 · DISTRICT 9
Mitchell Fee #34
Wichita County · K-M-A field · Producing · Vertical
Mitchell Fee #34 (API 42-485-44106) is a well in Wichita County operated by Quatro Oil And Gas Inc., completed June 29, 2006 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued May 16, 2006, permitted to 4,500 ft.
Completion filings report 3 formation tops, including Gunsight, Kma Lime, Kmasd..
Its lease has reported 826K barrels of oil and 93 mcf of gas since January 1993, last reporting in July 2026. The lease carries 33 wells, so these are lease totals, not this well alone.
Operator of record
Joshua, TX · P-5 Y, filed Aug 4, 2025 · 136 permits on file · (940) 767-4443
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Quatro Oil and Gas Inc. |
| Production reports | Quatro Oil and Gas, Inc.through Apr 2026 |
| Latest permit | Quatro Oil and Gas, Inc.May 16, 2006 |
- 4,500
- total depth, ft
- 1
- permits on file
- May 16, 2006
- last permit issued
- Jun 29, 2006
- completed
- 826K
- cumulative oil, bbl
- 93
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jun 29, 2006
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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; they carry 33 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Mitchell Fee O-13-11451 | K-M-A | Quatro Oil and Gas, Inc. | 33 | 826K | 93 | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 7,445 · prior 12 8,114(-8%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Mitchell Oil CompanyJan 1993 → Nov 2000
- 2Quatro Oil and Gas, Inc.Dec 2000 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 617893-99 | Drill | Quatro Oil and Gas, Inc. | Apr 19, 2006 | May 16, 2006 | Jun 16, 2006 | 4,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-11451 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,886 | 3,906 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 85 | 12.25 | 85 S |
| 4.5 | 4,009 | 7.875 | 350 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 | Apr 25, 2007 | Sep 20, 2006 | Yes |
| 00 | Dec 6, 2006 | — | — |
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-485-44106 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-485-44106 → 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/48544106, documented in the API reference.