WELL · 42-003-41207 · DISTRICT 8

Carbright 23 #2

Plugged

Andrews County · Wemac (Wolfcamp) field  · Vertical

Carbright 23 #2 (API 42-003-41207) is a plugged well in Andrews County, plugged December 15, 2022, last operated by Discovery Operating Inc..

The RRC has issued 2 drilling permits between 2009 and 2011, permitted to 10,000 ft.

Completion filings report 3 formation tops, including Clear Fork, Spraberry, Wolfcamp.

Its 2 leases have reported 36.4K barrels of oil and 57.3K mcf of gas since March 2010, last reporting in March 2023. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Discovery Operating Inc.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Mar 31, 2026
Permits on file
712
Phone
(432) 683-5203

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiscovery Operating Inc.
Production reportsDiscovery Operating, Inc.through Dec 2021
Latest permitDiscovery Operating, Inc.Apr 18, 2011
10,000
total depth, ft
2
permits on file
Apr 18, 2011
last permit issued
Mar 11, 2010
completed
36.4K
cumulative oil, bbl
57.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2010 THROUGH Mar 2023

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 11, 2010
Shut in
—
Plugged
Dec 15, 2022

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Carbright 23 O-10-41472Spraberry (Trend Area)Discovery Operating, Inc.233.2K55.2KApr 2011 – Mar 2023
Carbright 23 O-10-40163Wemac (Wolfcamp)Discovery Operating, Inc.13.17K2.1KMar 2010 – Jul 2012

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. 1Discovery Operating, Inc.Mar 2010 → Nov 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
713695-99RecompletionDiscovery Operating, Inc.Apr 6, 2011Apr 18, 2011Apr 20, 20119,215
685824-99DrillDiscovery Operating, Inc.Oct 6, 2009Oct 8, 2009Nov 10, 200910,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-40163————
—— O-10-41472————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK6,950-3,823
Spraberry7,514-4,387
Wolfcamp8,572-5,445

Perforations

Perforated and open-hole intervals.

FromToType
7,3568,427Perforated
8,8539,076Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
12.7532617.5380 S
8.6254,77011865 S
4.59,2147.8751,035 S
4.5—7.875465 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 18, 2012Mar 14, 2012—
00Sep 30, 2010Apr 13, 2010Yes
00Sep 21, 2010——

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