WELL · 42-417-36099 · DISTRICT 7

Davis Estate #2

Plugged

Shackelford County · A.t.& H. (Palo Pinto Sd.) field  · Vertical

Davis Estate #2 (API 42-417-36099) is a plugged well in Shackelford County, plugged July 27, 2011, last operated by Couch Oil & Gas Inc..

The RRC has issued one drilling permit, issued December 20, 1984, permitted to 3,999 ft.

It was permitted by Operator Name Not On File and has since transferred to Couch Oil & Gas Inc. on the wellbore schedule.

Completion filings report one formation top, including Palo Pinto.

Its lease has reported 4.25K barrels of oil and 49.9K mcf of gas since January 1993, last reporting in February 2012.

Operator of record

Couch Oil & Gas Inc.

Permitted by Operator Name Not on File; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed May 29, 2025 · 38 permits on file · (972) 444-0014

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCouch Oil & Gas Inc.
Production reportsCrownquest Operating, LLCthrough Jun 2000
Latest permitOperator Name Not on FileDec 20, 1984

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

3,999
total depth, ft
1
permits on file
Dec 20, 1984
last permit issued
Jul 13, 1985
completed
4.25K
cumulative oil, bbl
49.9K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2012

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 13, 1985
Shut in
—
Plugged
Jul 27, 2011

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
Davis Estate O-8-22958A.t.& H. (Palo Pinto Sd.)Couch Oil & Gas, Inc.14.25K49.9KJan 1993 – Feb 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. 1Sheets Exploration Co., Inc.Jan 1993 → Sep 1994
  2. 2Tracker MineralOct 1994 → Jun 1996
  3. 3Continual Oil & Gas, Inc.Jul 1996 → Feb 1998
  4. 4BC Operating, Inc.Mar 1998 → Dec 1999
  5. 5Crownquest Operating, LLCJan 2000 → Jun 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
261757-99DrillOperator Name Not on FileMay 17, 1985Dec 20, 1984—3,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-22958————

Formation tops

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

FormationMD ftSubsea
Palo Pinto3,158-1,279

Perforations

Perforated and open-hole intervals.

FromToType
3,1583,161Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62510612.25105 S
4.53,4986.75175 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
00Oct 14, 1985Jul 30, 1985—
00Oct 4, 1985——

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