WELL · 42-393-31872 · DISTRICT 10

Courson Ranch 136 #12

Y

Roberts County · Wildcat field · Temp Abandoned  · Vertical

Courson Ranch 136 #12 (API 42-393-31872) is a well in Roberts County operated by Complete Oil & Gas Services LLC, completed September 27, 2006 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued August 21, 2006, permitted to 5,900 ft.

It was permitted by Latigo Petroleum Texas, LP and has since transferred to Complete Oil & Gas Services LLC on the wellbore schedule.

Completion filings report 6 formation tops, including Krider, Winfield, Council Grove, Shawnee.

No lease production has been reported under this well’s leases.

Operator of record

Complete Oil & Gas Services LLC

Permitted by Latigo Petroleum Texas, LP; the EWA schedule now lists a different operator.

Perkins, OK · P-5 Y, filed Jul 4, 2026 · (405) 788-0433

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleComplete Oil & Gas Services LLC
Production reportsLatigo Petroleum Texas, LPthrough Feb 2007
Latest permitLatigo Petroleum Texas, LPAug 21, 2006

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

5,900
total depth, ft
1
permits on file
Aug 21, 2006
last permit issued
Sep 27, 2006
completed
0
cumulative oil, bbl
171
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 27, 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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Courson Ranch 136 G-14-227414WildcatComplete Oil & Gas Services, LLC10171Sep 2006 – Jul 2026

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.

  1. 1Latigo Petroleum Texas, LPJan 2007 → Feb 2007

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
624678-99DrillLatigo Petroleum Texas, LPAug 21, 2006Aug 21, 2006Sep 15, 20065,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-227414————

Formation tops

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

FormationMD ftSubsea
Krider3,252-620
Winfield3,483-851
Council Grove3,987-1,355
Shawnee4,741-2,109
Douglas5,354-2,722
Tonkawa5,690-3,058

Perforations

Perforated and open-hole intervals.

FromToType
5,7405,750Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,64212.25925 S
4.55,9097.875740 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 6, 2007Mar 19, 2007Yes
00Jun 26, 2007——

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.

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