TEXAS · WELLS · REEVES COUNTY · CWEI-CHK 22-C9 LEASE · API 42-389-32824 · DISTRICT 7B

Cwei-CHK 22-C9 #1

Plugged

Reeves County · Wolfbone (Trend Area) field  · Vertical

Cwei-Chk 22-C9 #1 (API 42-389-32824) is a plugged well in Reeves County, plugged January 10, 2025, last operated by Noble Energy Inc.

The RRC has issued one drilling permit, issued April 29, 2011, permitted to 13,500 ft.

It was permitted by Williams, Clayton Energy, Inc. and has since transferred to Noble Energy Inc on the wellbore schedule.

Completion filings report 4 formation tops, including Delaware, Cherry Canyon, 3rd Bone Sand, Wolfcamp.

Its lease has reported 4.94K barrels of oil and 32.7K mcf of gas since October 2011, with no volume in the three years through August 2026.

Operator of record

Noble Energy Inc

Permitted by Williams, Clayton Energy, Inc.; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Aug 20, 2026
Permits on file
565
Phone
(866) 212-1212

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNoble Energy Inc
Production reportsNoble Energy Incthrough Oct 2020
Latest permitWilliams, Clayton Energy, Inc.Apr 29, 2011

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

13,500
total depth, ft
1
permits on file
Apr 29, 2011
last permit issued
Jun 6, 2017
completed
4.94K
cumulative oil, bbl
32.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · JUN 2017 THROUGH OCT 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 6, 2017
Shut in
—
Plugged
Jan 10, 2025

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cwei-CHK 22-C9 O-10-40985Wolfbone (Trend Area)Noble Energy Inc14.94K32.7KOct 2011 – Oct 2020

No volumes reported on these leases in the last three years.

Wells named Cwei-CHK 22-C9

Noble Energy Inc's other wells filed under this lease name in Reeves 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

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

  1. 1NBL Permian LLCJun 2017 → Jun 2018
  2. 2Noble Energy IncAug 2018 → Jan 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
715050-99DrillWilliams, Clayton Energy, Inc.Apr 26, 2011Apr 29, 2011Aug 12, 201113,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jun 6, 2017Cwei-CHK 22-C9 O-10-40985Wolfbone (Trend Area)Noble Energy IncPlugged—

Formation tops

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

FormationMD ftSubsea
Delaware4,020-1,241
Cherry Canyon4,976-2,197
3RD Bone Sand9,212-6,433
Wolfcamp1ST WOLFCAMP TOP9,467-6,688
Wolfcamp2ND WOLFCAMP SAND10,330-7,551

Perforations

Perforated and open-hole intervals.

FromToType
9,50410,020Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,41817.51,245 S
8.6252,17111420 S
8.6255,51211820 S
5.511,1627.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
00Oct 12, 2017Jun 27, 2017Yes
00Dec 19, 2011Dec 16, 2011Yes

Well logs

2 logs loaded from the RRC's log index, 1 of them with a digital LAS file, the latest received Apr 29, 2020. Density, Gamma ray, Neutron. 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
Gamma RaySpans Cherry Canyon, 3rd Bone Sand, WolfcampLAS + TIFF5,502 to 11,147Apr 29, 20201.39 + 4.10
NEUTRON/DENSITY POROSITYSpans Delaware, Cherry Canyon, 3rd Bone Sand, WolfcampTIFF200 to 11,150Oct 7, 2014run Sep 9, 20114.18

"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. The University Lands library has no per-well link: then paste it into its 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/38932824, documented in the API reference.