WELL · 42-009-38914 · DISTRICT 9
Cowan-McKinney #1
Archer County · Vertical
Cowan-Mckinney #1 (API 42-009-38914) is a plugged well in Archer County, plugged May 27, 1985, last operated by Crutcher, David F. Inc..
The RRC has issued 2 drilling permits between 1985 and 1990, permitted to 5,000 ft.
Completion filings report one formation top, including Gunsite.
Its lease has reported 14K barrels of oil and 78 mcf of gas since January 1993, last reporting in March 2012. The lease carries 3 wells, so these are lease totals, not this well alone.
Operator of record
Wichita Falls, TX · P-5 Y, filed Jul 8, 1992 · 45 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Willowbend Investments, Inc.through Apr 2011 |
| Latest permit | Crutcher, David F. Inc.Jan 31, 1990 |
- 5,000
- total depth, ft
- 2
- permits on file
- Jan 31, 1990
- last permit issued
- —
- completed
- 14K
- cumulative oil, bbl
- 78
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- May 27, 1985
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 3 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Cowan-McKinney O-13-27686 | Archer County Regular | Willowbend Investments, Inc. | 3 | 14K | 78 | Jan 1993 – Mar 2012 |
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.
- 1Shelley, Richard WJan 1993 → Aug 1993
- 2Meyers Oil & GasSep 1993 → May 1997
- 3Willowbend Investments, Inc.Dec 1999 → Apr 2011
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 368589-99 | Reenter | Crutcher, David F. Inc. | Jan 12, 1990 | Jan 31, 1990 | — | 1,650 |
| 274779-99 | Drill | Henry Energy Corporation | May 9, 1985 | May 8, 1985 | May 14, 1985 | 5,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-27686 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,524 | 1,526 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 136 | 12.25 | 100 S |
| 4.5 | 1,568 | 6.75 | 135 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 | May 9, 1990 | Mar 27, 1990 | Yes |
| 00 | May 5, 1990 | — | — |
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-009-38914 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-009-38914 → 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/00938914, documented in the API reference.