TEXAS · WELLS · MIDLAND COUNTY · PARKS FIELD UNIT 2 LEASE · API 42-329-37371 · DISTRICT 7B

Parks Field Unit 2 #1436

Plugged

Midland County · Parks (Consolidated) field  · Vertical

Parks Field Unit 2 #1436 (API 42-329-37371) is a plugged well in Midland County, plugged May 28, 2021, last operated by Cog Operating LLC.

The RRC has issued one drilling permit, issued June 2, 2011, permitted to 12,000 ft.

Completion filings report 5 formation tops, including Spraberry, Dean, Wolfcamp, Strawn.

Its lease has reported 17.1M barrels of oil and 43.6M mcf of gas since April 2009, last reporting volume in August 2026. The lease carries 142 wells, so these are lease totals, not this well alone.

Operator of record

COG Operating LLC

Based in
Midland, TX
P-5 status
Active (A)
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 Aug 2026
Latest permitCOG Operating LLCJun 2, 2011
12,000
total depth, ft
1
permits on file
Jun 2, 2011
last permit issued
Jul 26, 2011
completed
17.1M
cumulative oil, bbl
43.6M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · APR 2009 THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 26, 2011
Shut in
—
Plugged
May 28, 2021

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 142 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Parks Field Unit 2 O-10-39630Parks (Consolidated)COG Operating LLC14217.1M43.6MApr 2009 – Aug 2026

Gas, mcf lease total

Last 12 months 2,684,751 · prior 12 2,533,139(+6%)

0100K200K300K202420252026

Oil, barrels lease total

Last 12 months 373,636 · prior 12 421,490(-11%)

020K40K60K202420252026

Wells named Parks Field Unit 2

COG Operating LLC's other wells filed under this lease name in Midland County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

Operator on the lease's P-4

Each operator named on the P-4 filings for this well's lease (a gas well is its own lease), from the date its filing took effect. The P-4 is filed by lease, so a date before the well was drilled is the lease's.

OperatorFromTo
COG Operating LLCApr 1, 2009today

Reporting production

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

  1. 1COG Operating LLCApr 2009 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
717482-99DrillCOG Operating LLCJun 1, 2011Jun 2, 2011Jul 11, 201112,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 26, 2011Parks Field Unit 2 O-10-39630Parks (Consolidated)COG Operating LLCPlugged—

Formation tops

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

FormationMD ftSubsea
Spraberry7,800-4,989
Dean9,100-6,289
Wolfcamp9,205-6,394
WolfcampLOWER WOLFCAMP9,510-6,699
WolfcampBASE WOLFCAMP10,065-7,254
Strawn10,145-7,334
Bend10,470-7,659

Perforations

Perforated and open-hole intervals.

FromToType
7,85010,870Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62543312.25230 S
5.510,9807.875835 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
00Apr 30, 2013Mar 28, 2012Yes
00Jun 21, 2012Aug 30, 2011Yes

Well logs

1 log loaded from the RRC's log index, the latest received Jul 8, 2014. Neutron.

Click a log to get its files from the RRC (free account). It opens in a new tab on the RRC's log search for this well, which lists each file to view or download; the RRC has no address for a single file.

Logas describedFiles Intervalft, as filedDatereceivedSizeMB
NEUTRON POROSITYSpans Spraberry, Dean, Wolfcamp, Strawn, BendTIFF4,000 to 10,948Jul 8, 2014run Aug 15, 20116.69

"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.

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.

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