WELL · 42-165-36983 · DISTRICT 8

Cook E. Estate A #4

Y

Gaines County · Stockyard (San Andres) field · Temp Abandoned  · Vertical

Cook E. Estate A #4 (API 42-165-36983) is a well in Gaines County operated by Ciervo Resources Asset Hldg LLC, completed December 1, 2008 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued October 6, 2008, permitted to 5,500 ft.

It was permitted by Texland Petroleum, L.P. and has since transferred to Ciervo Resources Asset Hldg LLC on the wellbore schedule.

Completion filings report one formation top, including San Andres.

No lease production has been reported under this well’s leases.

Operator of record

Ciervo Resources Asset Hldg LLC

Permitted by Texland Petroleum, L.P.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Jan 4, 2026 · (832) 563-3001

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCiervo Resources Asset Hldg LLC
Production reportsTexland Petroleum, L.P.through Jun 2014
Latest permitTexland Petroleum, L.P.Oct 6, 2008

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

5,500
total depth, ft
2
permits on file
Oct 6, 2008
last permit issued
Dec 1, 2008
completed
0
cumulative oil, bbl
81.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 1, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Cook, E. Estate "A" G-11-248468Stockyard (San Andres)Ciervo Resources Asset Hldg, LLC1081.9KDec 2008 – Jul 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. 1Texland Petroleum, L.P.Jan 2009 → Jun 2014

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
671935-98DrillTexland Petroleum, L.P.Feb 25, 2009Oct 6, 2008Nov 8, 20085,500
671935-99DrillTexland Petroleum, L.P.Sep 25, 2008Oct 6, 2008Nov 8, 20085,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-11-248468————

Formation tops

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

FormationMD ft
San AndresTOP SAN ANDRES4,556
San AndresMIDDLE SAN ANDRES4,632

Perforations

Perforated and open-hole intervals.

FromToType
4,5764,581Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62541012.25350 S
5.54,7617.8751,650 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
00Jul 29, 2009Apr 3, 2009Yes
00Jun 26, 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) 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/16536983, documented in the API reference.