WELL · 42-323-32666 · DISTRICT 1

Comanche Ranch #1581H

Plugged

Maverick County · Comanche-Halsell (6500) field  · Horizontal

Comanche Ranch #1581H (API 42-323-32666) is a plugged horizontal well in Maverick County, plugged June 13, 2022, last operated by Cmr Energy L.P..

The RRC has issued 2 drilling permits between 2003 and 2004, permitted to 9,000 ft.

Completion filings report 11 formation tops, including Wilcox, Olmos, San Miguel, Anacacho.

Its lease has reported 5.3M barrels of oil since February 2002, last reporting in July 2026. The lease carries 81 wells, so these are lease totals, not this well alone.

Operator of record

CMR Energy L.P.

Houston, TX · P-5 Y, filed Jan 4, 2026 · 114 permits on file · (713) 580-7218

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCMR Energy L.P.
Production reportsCMR Energy, L.P.through Apr 2026
Latest permitCMR Energy, L.P.Aug 20, 2004
9,000
total depth, ft
2
permits on file
Aug 20, 2004
last permit issued
Oct 8, 2004
completed
5.3M
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2002 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 8, 2004
Shut in
—
Plugged
Jun 13, 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 lease this well is completed on; they carry 81 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Comanche Ranch O-1-14381Comanche-Halsell (6500)CMR Energy, L.P.815.3M0Feb 2002 – Jul 2026

Oil, barrels lease total

Last 12 months 45,071 · prior 12 53,079(-15%)

05K10K202420252026

Chain of custody

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

  1. 1Saxet Energy, Ltd.Feb 2002 → Mar 2004
  2. 2CMR Energy, L.P.Apr 2004 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
549897-99RecompletionCMR Energy, L.P.Aug 20, 2004Aug 20, 2004—8,000
530881-99DrillSaxet Energy, Ltd.Apr 17, 2003Apr 17, 2003Apr 25, 20039,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-14381————
—— O-1-14381————

Formation tops

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

FormationMD ftSubsea
Wilcox1,140-445
Olmos1,450-755
San Miguel1,980-1,285
Anacacho2,900-2,205
Austin Chalk3,090-2,395
Eagle FordEAGLEFORD4,000-3,305
Del Rio4,693-3,998
Georgetown4,934-4,239
McKnight5,530-4,835
Edwards5,820-5,125
Glen Rose6,090-5,395

Perforations

Perforated and open-hole intervals.

FromToType
6,2007,614Perforated
6,5906,665Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62553012.25235 S
76,5908.75480 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
00Aug 14, 2006Mar 17, 2006—
00May 19, 2005Dec 15, 2004Yes
00Feb 25, 2005Jun 6, 2003Yes
00Nov 21, 2003Jun 6, 2003Yes
00Nov 14, 2003——

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