WELL · 42-227-03971 · DISTRICT 8

Cohiba #2

Plugged

Howard County  · Vertical

Cohiba #2 (API 42-227-03971) is a plugged well in Howard County, plugged July 2, 2004, last operated by Trilogy Operating, Inc..

The RRC has issued 2 drilling permits (amended twice) between 2004 and 2008, permitted to 9,568 ft.

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

Its lease has reported 19.9K barrels of oil and 47.1K mcf of gas since March 2008, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Trilogy Operating, Inc.

Midland, TX · P-5 Y, filed Nov 4, 2025 · 247 permits on file · (432) 556-7931

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsVital Energy, Inc.through Oct 2025
Latest permitTrilogy Operating, Inc.Aug 18, 2008
9,568
total depth, ft
4
permits on file
Aug 18, 2008
last permit issued
—
completed
19.9K
cumulative oil, bbl
47.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Jul 2, 2004

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cohiba O-10-38796Spraberry (Trend Area)Crescent Energy Operating, LLC219.9K47.1KMar 2008 – Jul 2026

Oil, barrels lease total

Last 12 months 28 · prior 12 0

0102030202420252026

Chain of custody

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

  1. 1Trilogy Operating, Inc.Mar 2008 → Oct 2014
  2. 2XOG Operating LLCNov 2014 → Apr 2016
  3. 3Platform Operating, LLCMay 2016 → Dec 2017
  4. 4Rrig Exploration, LLCJan 2018 → Mar 2018
  5. 5Sabalo Operating, LLCMay 2018 → Jan 2019
  6. 6Vital Energy, Inc.Oct 2025 → Oct 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
667978-97ReenterTrilogy Operating, Inc.Feb 4, 2009Aug 18, 2008Oct 20, 20089,568
667978-98ReenterTrilogy Operating, Inc.Aug 21, 2008Aug 18, 2008—9,568
667978-99ReenterTrilogy Operating, Inc.Jul 31, 2008Aug 18, 2008—6,000
547388-99ReenterBarrett Brothers Oil & Gas, Inc.Jun 24, 2004Jun 24, 2004Jun 29, 20046,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-38796————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Clear ForkCLEARFORK4,390
Spraberry5,510
Dean6,660
Wolfcamp6,922
Strawn7,942

Perforations

Perforated and open-hole intervals.

FromToType
5,2387,839Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.375295——
8.6252,845——
5.58,2107.875664 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 20, 2009Feb 4, 2009Yes
00Apr 24, 2009——

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