TEXAS · WELLS · GLASSCOCK COUNTY · CURRIE STATE V LEASE · API 42-173-36781 · DISTRICT 7B

Currie State V #2311

Plugged

Glasscock County · Garden City S. (Wolfcamp) field  · Vertical

Currie State V #2311 (API 42-173-36781) is a plugged well in Glasscock County, plugged April 15, 2020, last operated by Cog Operating LLC.

The RRC has issued one drilling permit (amended once), issued August 19, 2014, permitted to 9,400 ft.

Completion filings report 10 formation tops, including Santa Rosa, Seven Rivers, Queen, Yates.

Its lease has reported 18.3K barrels of oil and 101K mcf of gas since September 2015, last reporting in July 2020.

Operator of record

COG Operating LLC

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jun 2, 2026
Permits on file
4,568
Phone
(432) 683-7443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCOG Operating LLC
Production reportsCOG Operating LLCthrough Dec 2019
Latest permitCOG Operating LLCAug 19, 2014
9,400
total depth, ft
2
permits on file
Aug 19, 2014
last permit issued
Apr 22, 2016
completed
18.3K
cumulative oil, bbl
101K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2015 THROUGH Jul 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 22, 2016
Shut in
—
Plugged
Apr 15, 2020

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
Currie State V O-10-46917Garden City, S. (Wolfcamp)COG Operating LLC118.3K101KSep 2015 – Jul 2020

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. 1COG Operating LLCSep 2015 → Dec 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
792652-98DrillCOG Operating LLCOct 13, 2015Aug 19, 2014Jul 21, 20159,400
792652-99DrillCOG Operating LLCJul 28, 2014Aug 19, 2014Jul 21, 20159,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 22, 2016Currie State V O-10-46917Garden City S. (Wolfcamp)COG Operating LLCPlugged—

Formation tops

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

FormationMD ftSubsea
Santa Rosa1,0001,542
Seven Rivers1,3001,242
Queen1,5001,042
Yates2,050492
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO2,45488
Glorieta2,700-158
Grayburg2,850-308
Clear ForkCLEARFORK3,707-1,165
Spraberry4,621-2,079
Wichita-AlbanyWICHITA ALBANY7,400-4,858

Perforations

Perforated and open-hole intervals.

FromToType
6,6369,250Perforated
6,9009,250Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.52,199111,425 S
5.59,3767.8751,231 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
00May 5, 2016May 2, 2016Yes
00Oct 22, 2015Oct 19, 2015Yes

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