WELL · 42-497-34241 · DISTRICT 9

Cocanaugher #4

Plugged

Wise County · Boonsville (Bend Congl. Gas) field  · Vertical

Cocanaugher #4 (API 42-497-34241) is a plugged well in Wise County, plugged November 9, 2023, last operated by Richey Ray Management CO. Inc..

The RRC has issued one drilling permit, issued March 16, 1998, permitted to 7,000 ft.

It was permitted by Texas American Resources Company and has since transferred to Richey Ray Management CO. Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Park, Caddo, Bend.

Operator of record

Richey Ray Management Co. Inc.

Permitted by Texas American Resources Company; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Sep 4, 2025 · 136 permits on file · (800) 800-2908

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRichey Ray Management Co. Inc.
Production reportsRichey, Ray Management Co., Inc.through Sep 2006
Latest permitTexas American Resources CompanyMar 16, 1998

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

7,000
total depth, ft
1
permits on file
Mar 16, 1998
last permit issued
Jun 11, 1998
completed
0
cumulative oil, bbl
101K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 1998 THROUGH May 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jun 11, 1998
Shut in
—
Plugged
Nov 9, 2023

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Cocanaugher G-13-169444Boonsville (Bend Congl., Gas)Richey, Ray Management Co., Inc.10101KJun 1998 – May 2026

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. 1Texas American Resources CompanyJun 1998 → Dec 2001
  2. 2Goodrich Petroleum CompanyJan 2002 → Apr 2005
  3. 3Richey, Ray Management Co., Inc.May 2005 → Sep 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
474366-99DrillTexas American Resources CompanyMar 16, 1998Mar 16, 1998Mar 19, 19987,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-169444————

Formation tops

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

FormationMD ftSubsea
Park4,870-3,825
Caddo5,170-4,125
BendBEND X5,718-4,673

Perforations

Perforated and open-hole intervals.

FromToType
5,9705,979Perforated
6,0126,018Perforated
6,0786,083Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62575012.25405 S
4.56,1737.875260 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
00Sep 2, 1998Aug 17, 1998Yes
00Aug 27, 1998——

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