WELL · 42-151-32332 · DISTRICT 7

Waddell Bettie #1 B

Plugged

Fisher County · Sandy Hill (Strawn Sand) field  · Vertical

Waddell Bettie #1 B (API 42-151-32332) is a plugged well in Fisher County, plugged May 25, 2006, last operated by Central Texas Operating Inc..

The RRC has issued one drilling permit, issued October 2, 1992, permitted to 5,800 ft.

It was permitted by Rincon Production CO., Inc. and has since transferred to Central Texas Operating Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Coleman Junction, Strawn.

Its lease has reported 24.6K barrels of oil and 76.6K mcf of gas since January 1993, last reporting in July 2006.

Operator of record

Central Texas Operating Inc.

Permitted by Rincon Production Co., Inc.; the EWA schedule now lists a different operator.

Breckenridge, TX · P-5 Y, filed Dec 4, 2025 · (254) 559-0875

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCentral Texas Operating Inc.
Production reportsCentral Texas Operating, Inc.through May 2005
Latest permitRincon Production Co., Inc.Oct 2, 1992

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

5,800
total depth, ft
1
permits on file
Oct 2, 1992
last permit issued
Nov 13, 1992
completed
24.6K
cumulative oil, bbl
76.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2006

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Nov 13, 1992
Shut in
—
Plugged
May 25, 2006

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
Waddell, Bettie O-8-26719Sandy Hill (Strawn Sand)Central Texas Operating, Inc.124.6K76.6KJan 1993 – Jul 2006

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. 1Rincon Production Co., Inc.Jan 1993 → Mar 1997
  2. 2Central Texas Operating, Inc.Apr 1997 → May 2005

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
403568-99DrillRincon Production Co., Inc.Sep 17, 1992Oct 2, 1992Oct 5, 19925,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-26719————

Formation tops

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

FormationMD ftSubsea
Coleman Junction2,132-194
StrawnSTRAWN REEF5,366-3,428
StrawnSTRAWN SAND5,565-3,627

Perforations

Perforated and open-hole intervals.

FromToType
5,5745,592Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62517212.25120 S
4.55,6497.875200 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
00Jan 14, 1993Nov 17, 1992Yes
00Dec 2, 1992——

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