TEXAS · WELLS · OCHILTREE COUNTY · API 42-357-32560 · DISTRICT 08

Courson-Parnell 474 #3474

Shut in

Ochiltree County · Northrup (Cleveland) field · Temp Abandoned  · Vertical

Courson-Parnell 474 #3474 (API 42-357-32560) is a well in Ochiltree County operated by Presidio Petroleum LLC, completed July 24, 2006 and listed as temp abandoned on the RRC schedule, shut in September 1, 2024.

The RRC has issued 3 drilling permits between 2006 and 2007, permitted to 8,965 ft.

It was permitted by Apache Corporation and has since transferred to Presidio Petroleum LLC on the wellbore schedule.

Completion filings report 6 formation tops, including Lansing Kc Sand, Cleveland, Oswego, Atoka.

Its 2 leases have reported 711 barrels of oil and 290K mcf of gas since April 2006, last reporting volume in August 2024. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Presidio Petroleum LLC

Permitted by Apache Corporation; the EWA schedule now lists a different operator.

Based in
Canadian, TX
P-5 status
Active (A)
P-5 last filed
May 1, 2026
Permits on file
13
Phone
(806) 217-4483

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePresidio Petroleum LLC
Production reportsPresidio Petroleum LLCthrough Aug 2024
Latest permitApache CorporationOct 3, 2007

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

8,965
total depth, ft
3
permits on file
Oct 3, 2007
last permit issued
Jul 24, 2006
completed
711
cumulative oil, bbl
290K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2006 THROUGH Aug 2024

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 24, 2006
Shut in
Sep 1, 2024
Plugged
—

Operator's P-5 on the schedule: Active (A)

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Courson-Parnell 474 G-14-218472Northrup (Cleveland)Presidio Petroleum LLC1624272KJul 2006 – Aug 2024
Parnell 474 G-14-217265Dutcher (Atoka)Apache Corporation18717.9KApr 2006 – Jul 2006

Gas, mcf lease total

Last 12 months 0 · prior 12 1(-100%)

0200400202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Apache CorporationApr 2006 → Oct 2016
  2. 2Presidio Petroleum LLCSep 2021 → Aug 2024

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
646986-99RecompletionApache CorporationOct 1, 2007Oct 3, 2007—11,000
621845-99RecompletionApache CorporationJun 29, 2006Jun 30, 2006—11,000
613887-99DrillApache CorporationFeb 8, 2006Feb 9, 2006Mar 6, 200611,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 24, 2006Courson-Parnell 474 G-14-218472Northrup (Cleveland)Presidio Petroleum LLCTemp Abandoned · shut in Sep 1, 20248,965
Apr 6, 2006Parnell 474 G-14-217265Dutcher (Atoka)Apache CorporationNot on Schedule—

Formation tops

As filed on W-2/G-1. Subsea from 2,758 ft elevation.Download CSV →

FormationMD ftSubsea
Lansing KC Sand7,125-4,367
Cleveland7,165-4,407
Oswego7,475-4,717
AtokaATOKA PARNELL8,383-5,625
13 Finger8,421-5,663
Morrow8,508-5,750

Perforations

Perforated and open-hole intervals.

FromToType
7,1267,145Perforated
7,1677,180Perforated
7,1877,196Perforated
7,2047,212Perforated
8,3618,365Perforated
8,3828,390Perforated
8,4138,415Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,60711855 S
4.58,9597.875500 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jan 10, 2007Aug 9, 2006Yes
00Nov 7, 2006Jun 2, 2006Yes
00Aug 28, 2006——
00Jul 25, 2006——

Well logs

2 logs loaded from the RRC's log index, the latest received Mar 30, 2009. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Oswego, Atoka, 13 Finger, MorrowTIFF7,810 to 8,964Mar 30, 2009run Mar 24, 20061.48
RESISTIVITYSpans Lansing Kc Sand, Cleveland, OswegoTIFF1,600 to 8,301Mar 27, 2009run Mar 16, 20062.04

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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/35732560, documented in the API reference.