TEXAS · WELLS · LOVING COUNTY · API 42-301-32989 · DISTRICT 7B

CBR 22 #11H

Shut in

Loving County · Phantom (Wolfcamp) field · Temp Abandoned  · Horizontal

Cbr 22 #11H (API 42-301-32989) is a horizontal well in Loving County operated by Wpx Energy Permian LLC, completed March 16, 2017 and listed as temp abandoned on the RRC schedule, shut in October 1, 2025.

The RRC has issued one drilling permit, issued September 2, 2016, permitted to 10,976 ft.

It was permitted by Rki Exploration & Production LLC and has since transferred to Wpx Energy Permian LLC on the wellbore schedule.

Completion filings report 10 formation tops, including Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring.

Its 2 leases have reported 252K barrels of oil and 1.2M mcf of gas since January 2015, last reporting volume in September 2025. The leases carry 11 wells, so these are lease totals, not this well alone.

Operator of record

WPX Energy Permian LLC

Permitted by RKI Exploration & Production LLC; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
956
Phone
(405) 235-3611

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWPX Energy Permian LLC
Production reportsWPX Energy Permian, LLCthrough Sep 2025
Latest permitRKI Exploration & Production LLCSep 2, 2016

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

10,976
total depth, ft
1
permits on file
Sep 2, 2016
last permit issued
Mar 16, 2017
completed
252K
cumulative oil, bbl
1.2M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2017 THROUGH Sep 2025

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 16, 2017
Shut in
Oct 1, 2025
Plugged
—

Operator's P-5 on the schedule: Active (A)

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 2 leases this well is completed on; they carry 11 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
CBR 22 G-10-285849Phantom (Wolfcamp)WPX Energy Permian, LLC1252K1.2MMar 2017 – Sep 2025
CBR 22 O-10-46406Phantom (Wolfcamp)WPX Energy Permian, LLC1000Jan 2015 – —

Gas, mcf lease total

Last 12 months 18,297 · prior 12 43,016(-57%)

05K10K15K202420252026

Chain of custody

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

  1. 1WPX Energy Permian, LLCMar 2017 → Sep 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
818063-99DrillRKI Exploration & Production LLCAug 26, 2016Sep 2, 2016Dec 3, 201616,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 16, 2017CBR 22 G-10-285849Phantom (Wolfcamp)WPX Energy Permian LLCTemp Abandoned · shut in Oct 1, 202510,976
Mar 16, 2017CBR 22 O-10-46406Phantom (Wolfcamp)WPX Energy Permian LLCNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Bell Canyon3,427-499
Cherry Canyon4,388-1,460
Brushy Canyon5,676-2,748
Bone SpringBONE SPRINGS7,329-4,401
Wolfcamp10,451-7,523
AtokaATOKA - HIGH PRESSURE——
Delaware——
Pennsylvanian——
Red Bluff——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
10,82615,610Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37592117.5730 S
9.6253,47112.25930 S
711,3098.751,120 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
00Feb 28, 2019Dec 17, 2018Yes
00Jul 6, 2017May 1, 2017Yes

Well logs

2 logs loaded from the RRC's log index, 2 of them with a digital LAS file, the latest received Nov 19, 2019. Gamma ray, While drilling (MWD). 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 Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring, WolfcampLAS + TIFF2,645 to 14,647Nov 19, 20190.39 + 21.9
Measure While Drilling (MWD)Spans Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring, WolfcampLAS + TIFF2,600 to 15,754Apr 30, 20190.39 + 6.54

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