WELL · 42-363-33342 · DISTRICT 7

Caudill #1

Plugged

Palo Pinto County · Palo Pinto Co. Reg. (Gas) field  · Vertical

Caudill #1 (API 42-363-33342) is a plugged well in Palo Pinto County, plugged November 15, 2000, last operated by Bandera Petroleum Inc..

The RRC has issued 2 drilling permits between 1984 and 2000, permitted to 5,000 ft.

Completion filings report 6 formation tops, including Strawn, Top Preg Shale, Atoka, Conglomerate.

Its 2 leases have reported 1.36K barrels of oil and 17.4K mcf of gas since January 1993, last reporting in January 2001. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Bandera Petroleum Inc.

Abilene, TX · P-5 Y, filed Apr 5, 2019 · 71 permits on file · (918) 520-4859

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBandera Petroleum Inc.
Production reportsBandera Petroleum, Inc.through Nov 2000
Latest permitBandera Petroleum, Inc.Aug 2, 2000
5,000
total depth, ft
2
permits on file
Aug 2, 2000
last permit issued
Aug 12, 2000
completed
1.36K
cumulative oil, bbl
17.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2001

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 12, 2000
Shut in
—
Plugged
Nov 15, 2000

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Caudill G-8-178809Palo Pinto Co. Reg. (Gas)Bandera Petroleum, Inc.10414Aug 2000 – Jan 2001
Caudill O-8-21827Palo Pinto County RegularBandera Petroleum, Inc.11.36K16.9KJan 1993 – Jan 2001

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. 1Bandera Petroleum, Inc.Jan 1993 → Nov 2000

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
497714-99RecompletionBandera Petroleum, Inc.Jul 27, 2000Aug 2, 2000Jul 27, 20001,570
242220-99DrillWilliams Petroleum CompanyJun 15, 1984Jun 15, 1984—5,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-178809————
—— O-8-21827————

Formation tops

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

FormationMD ftSubsea
Strawn1,480-427
Top Preg Shale3,724-2,671
Atoka3,904-2,851
Conglomerate4,120-3,067
Marble Falls4,248-3,195
EllenburgerELLENBERGER4,746-3,693

Perforations

Perforated and open-hole intervals.

FromToType
1,4801,484Perforated
1,4861,490Perforated
4,1204,126Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62527912.25210 S
4.51,5717.875300 S
4.54,3007.875275 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
00Nov 8, 2000Sep 6, 2000Yes
00Oct 10, 2000——
00Dec 10, 1984Oct 1, 1984—
00Dec 1, 1984——

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