WELL · 42-461-37187 · DISTRICT 7

Powell 21 #9

Y

Upton County · Spraberry (Trend Area) field · Producing  · Vertical

Powell 21 #9 (API 42-461-37187) is a well in Upton County operated by Cog Operating LLC, completed June 11, 2011 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued January 24, 2011, permitted to 11,000 ft.

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

Its lease has reported 488K barrels of oil and 1.05M mcf of gas since October 2010, last reporting in July 2026. The lease carries 6 wells, so these are lease totals, not this well alone.

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 Apr 2026
Latest permitCOG Operating LLCJan 24, 2011
11,000
total depth, ft
2
permits on file
Jan 24, 2011
last permit issued
Jun 11, 2011
completed
488K
cumulative oil, bbl
1.05M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 11, 2011
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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; they carry 6 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Powell "21" O-9-17335Spraberry (Trend Area)COG Operating LLC6488K1.05MOct 2010 – Jul 2026

Oil, barrels lease total

Last 12 months 15,577 · prior 12 13,335(+17%)

01K2K3K202420252026

Gas, mcf lease total

Last 12 months 35,711 · prior 12 28,595(+25%)

02K4K6K202420252026

Chain of custody

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

  1. 1COG Operating LLCOct 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
708554-98DrillCOG Operating LLCFeb 15, 2011Jan 24, 2011Mar 27, 201111,000
708554-99DrillCOG Operating LLCJan 14, 2011Jan 24, 2011Mar 27, 201111,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-17335————

Formation tops

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

FormationMD ftSubsea
Spraberry7,670-4,842
Dean9,050-6,222
Wolfcamp9,180-6,352
L. Wolfcamp9,500-6,672
B. Wolfcamp10,500-7,672

Perforations

Perforated and open-hole intervals.

FromToType
7,86010,450Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62583512.25430 S
5.510,6857.875905 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
00Jun 29, 2012Jan 25, 2012Yes
00Jun 26, 2012Jul 29, 2011Yes

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) and the University Lands library. 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/46137187, documented in the API reference.