WELL · 42-363-35861 · DISTRICT 7

Caudill Heirs #3

Y

Palo Pinto County · P.K. Lake (Congl.) field · Producing  · Directional

Caudill Heirs #3 (API 42-363-35861) is a well in Palo Pinto County operated by Gannett Operating LLC, completed June 12, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued October 10, 2008, permitted to 4,900 ft.

It was permitted by Hill, R.M. Operating Inc. and has since transferred to Gannett Operating LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Palo Pinto, Caddo.

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

Operator of record

Gannett Operating LLC

Permitted by Hill, R.M. Operating Inc.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed May 4, 2026 · 21 permits on file · (940) 550-5351

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleGannett Operating LLC
Production reportsGannett Operating LLCthrough Apr 2026
Latest permitHill, R.M. Operating Inc.Apr 29, 2009

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

4,900
total depth, ft
2
permits on file
Apr 29, 2009
last permit issued
Jun 12, 2009
completed
0
cumulative oil, bbl
408K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jun 12, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Caudill Heirs G-8-252165P.K. Lake (Congl.)Gannett Operating LLC10408KJun 2009 – Jul 2026

Gas, mcf lease total

Last 12 months 888 · prior 12 809(+10%)

050100150202420252026

Chain of custody

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

  1. 1Hill, R.M. Operating Inc.Jun 2009 → Jul 2016
  2. 2Gannett Operating LLCAug 2016 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
672265-98DrillHill, R.M. Operating Inc.Apr 21, 2009Apr 29, 2009Apr 29, 20094,900
672265-99DrillUpham Oil & Gas CompanyOct 1, 2008Oct 10, 2008—4,245

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-252165————

Formation tops

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

FormationMD ftSubsea
Palo Pinto648448
Caddo3,490-2,394

Perforations

Perforated and open-hole intervals.

FromToType
4,0104,090Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62521113.5140 S
5.55,5258.75130 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
00Dec 29, 2009Sep 3, 2009Yes
00Oct 30, 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/36335861, documented in the API reference.