TEXAS · WELLS · CRANE COUNTY · API 42-103-01790 · DISTRICT 7B

Waddell TR A #322

Shut in

Crane County · Sand Hills (Tubb) field · Shut In  · Vertical

Fields on the latest permit · any of 2
Sand Hills (Judkins) · Sand Hills (Tubb)
Not one formation; the well must be completed in one of them, and no target formation is stated.

Waddell TR A #322 (API 42-103-01790) is a well in Crane County operated by Blackbeard Operating LLC, completed July 24, 2003 and listed as shut in on the RRC schedule, shut in September 1, 2024.

The RRC has issued one drilling permit (amended once), issued February 11, 2003, permitted to 6,040 ft.

It was permitted by Burlington Res O & G CO-Midland and has since transferred to Blackbeard Operating LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Judkins, Tubb, Witchita-Albany, Waddell.

Its 2 leases have reported 19.6M barrels of oil and 84.9M mcf of gas since the record begins in January 1993, last reporting volume in April 2026. The leases carry 607 wells, so these are lease totals, not this well alone.

Operator of record

Blackbeard Operating LLC

Permitted by Burlington Res O & G Co-Midland; the EWA schedule now lists a different operator.

Based in
Fort Worth, TX
P-5 status
Active (A)
P-5 last filed
Oct 2, 2025
Permits on file
2,267
Phone
(432) 242-0050

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBlackbeard Operating LLC
Production reportsBlackbeard Operating, LLCthrough Apr 2026
Latest permitBurlington Res O & G Co-MidlandFeb 11, 2003

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

6,040
total depth, ft
2
permits on file
Feb 11, 2003
last permit issued
Jul 24, 2003
completed
19.6M
cumulative oil, bbl
84.9M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · ON RECORD FROM JAN 1993, THE RECORD'S FIRST MONTH, THROUGH APR 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 24, 2003
Shut in
Sep 1, 2024
Plugged
—

Operator's P-5 on the schedule: Active – Extension (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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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 607 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Waddell TR A O-10-5294Sand Hills (Tubb)Blackbeard Operating, LLC56118.7M79.1Mby Jan 1993 – Apr 2026
Waddell TR A O-10-10932Running W (Waddell)Blackbeard Operating, LLC46884K5.76Mby Jan 1993 – Apr 2026

Oil, barrels lease total

Last 12 months 1,332,060 · prior 12 1,258,659(+6%)

050K100K150K202420252026

Gas, mcf lease total

Last 12 months 6,616,225 · prior 12 6,210,921(+7%)

0500K1M202420252026

Wells named Waddell TR A

Blackbeard Operating LLC's other wells filed under this lease name in Crane County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Southland Royalty Co.-MidlandJan 1993 → Feb 1996
  2. 2Meridian Oil Inc.-MidlandMar 1996 → Jul 1996
  3. 3Burlington Res O & G Co-MidlandAug 1996 → Mar 2020
  4. 4Blackbeard Operating, LLCApr 2020 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
528173-98RecompletionBurlington Res O & G Co-MidlandApr 11, 2003Feb 11, 2003Jan 20, 20036,040
528173-99RecompletionBurlington Res O & G Co-MidlandFeb 6, 2003Feb 11, 2003—6,040

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 24, 2003Waddell TR A O-10-5294Sand Hills (Tubb)Blackbeard Operating LLCShut In · shut in Sep 1, 20246,040
Feb 2, 1956Waddell TR A O-10-10932Running W (Waddell)Blackbeard Operating LLCNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Judkins2,682-164
Tubb4,400-1,882
Witchita-Albany4,857-2,339
WaddellWADDELL SAND5,965-3,447

Perforations

Perforated and open-hole intervals.

FromToType
4,4554,540Perforated
5,9656,025Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,16812.252,125 S
9.6252,168——
7.6253,1508.75576 S
7.6253,150——
25,954——
5.56,0406.75375 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Dec 8, 2003Aug 29, 2003—
00Nov 19, 2003——
00Jan 12, 1984Jun 17, 1960—

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it. The University Lands library has no per-well link: then paste it into its search.

Find logs withinmiles of this well:List →Map →

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