WELL · 42-009-42361 · DISTRICT 9
Medders South #1
Archer County · Coleman Ranch (Caddo) field · Vertical
Medders South #1 (API 42-009-42361) is a plugged well in Archer County, plugged July 7, 2017, last operated by Cholla Petroleum Inc..
The RRC has issued one drilling permit, issued August 11, 2011, permitted to 5,999 ft.
Completion filings report 3 formation tops, including Gunsight, M Sand, Caddo.
Its lease has reported 5.4K barrels of oil and 40.4K mcf of gas since September 2011, last reporting in September 2017.
Operator of record
- Based in
- Dallas, TX
- P-5 status
- Active (A)
- P-5 last filed
- Mar 23, 2026
- Permits on file
- 1,085
- Phone
- (214) 692-7052
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Cholla Petroleum Inc. |
| Production reports | Cholla Petroleum, Inc.through Jul 2017 |
| Latest permit | Cholla Petroleum, Inc.Aug 11, 2011 |
- 5,999
- total depth, ft
- 1
- permits on file
- Aug 11, 2011
- last permit issued
- Sep 7, 2011
- completed
- 5.4K
- cumulative oil, bbl
- 40.4K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2011 THROUGH Sep 2017
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Sep 7, 2011
- Shut in
- —
- Plugged
- Jul 7, 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 |
|---|---|---|---|---|---|---|
| Medders South O-13-32007 | Coleman Ranch (Caddo) | Cholla Petroleum, Inc. | 1 | 5.4K | 40.4K | Sep 2011 – Sep 2017 |
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.
- 1Cholla Petroleum, Inc.Sep 2011 → Mar 2017
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 721932-99 | Drill | Cholla Petroleum, Inc. | Aug 9, 2011 | Aug 11, 2011 | Aug 16, 2011 | 5,999 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Sep 7, 2011 | Medders South O-13-32007 | Coleman Ranch (Caddo) | Cholla Petroleum Inc. | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 939 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,084 | 5,094 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 118 | 12.25 | 100 S |
| 4.5 | 5,112 | 7.875 | 280 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 30, 2012 | Sep 13, 2011 | Yes |
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-42361 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-009-42361 → 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/00942361, documented in the API reference.