WELL · 42-197-31450 · DISTRICT 9

Holcomb #1

Plugged

Hardeman County · Quanah (Chappel 8295) field  · Vertical

Holcomb #1 (API 42-197-31450) is a plugged well in Hardeman County, plugged November 14, 2014, last operated by Holmes Exploration LLC.

The RRC has issued one drilling permit, issued June 29, 1999, permitted to 9,000 ft.

It was permitted by Ratliff Operating Corp. and has since transferred to Holmes Exploration LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Barnett, Chester, Merimac, Chappel.

Its lease has reported 3.77K barrels of oil and 6.59K mcf of gas since September 1999, last reporting in June 2015.

Operator of record

Holmes Exploration LLC

Permitted by Ratliff Operating Corp.; the EWA schedule now lists a different operator.

Tulsa, OK · P-5 Y, filed Feb 5, 2016 · 341 permits on file · (918) 551-7180

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHolmes Exploration LLC
Production reportsGaedeke Oil & Gas Operating, LLCthrough Sep 2010
Latest permitRatliff Operating Corp.Jun 29, 1999

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

9,000
total depth, ft
1
permits on file
Jun 29, 1999
last permit issued
Feb 4, 2000
completed
3.77K
cumulative oil, bbl
6.59K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 1999 THROUGH Jun 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 4, 2000
Shut in
—
Plugged
Nov 14, 2014

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
Holcomb O-13-29737Quanah (Chappel 8295)Holmes Exploration, LLC13.77K6.59KSep 1999 – Jun 2015

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. 1Ratliff Operating Corp.Sep 1999 → Feb 2001
  2. 2Trio Consulting & Management,llcDec 2007 → Oct 2009
  3. 3Gaedeke Oil & Gas Operating, LLCNov 2009 → Sep 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
485501-99DrillRatliff Operating Corp.Jun 28, 1999Jun 29, 1999Aug 19, 19999,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-29737————

Formation tops

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

FormationMD ftSubsea
Barnett8,197-6,680
Chester8,219-6,702
Merimac8,406-6,889
Chappel8,520-7,003

Perforations

Perforated and open-hole intervals.

FromToType
8,5208,565Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62550812.25290 S
5.58,5557.875150 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
00Apr 13, 2000Mar 10, 2000Yes
00Mar 24, 2000——

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