TEXAS · WELLS · MIDLAND COUNTY · BRADFORD "22A" LEASE · API 42-329-31034 · DISTRICT 7B

Bradford 22A #1

Shut in

Midland County · Bradford Ranch (Atoka) field · Shut In  · Vertical

Bradford 22a #1 (API 42-329-31034) is a well in Midland County operated by Diamondback E&P LLC, completed April 10, 1982 and listed as shut in on the RRC schedule, shut in October 1, 2019.

The RRC has issued one drilling permit, issued November 4, 1981, permitted to 11,500 ft.

It was permitted by Dorchester Exploration, Inc. and has since transferred to Diamondback E&P LLC on the wellbore schedule.

Its lease has reported 22.1K barrels of oil and 88.2K mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Diamondback E&P LLC

Permitted by Dorchester Exploration, Inc.; the EWA schedule now lists a different operator.

Based in
Midland, TX
P-5 status
Active – Extension (X)
P-5 last filed
May 4, 2026
Permits on file
5,243
Phone
(432) 221-7400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDiamondback E&P LLC
Production reportsEndeavor Energy Resources L.P.through Jun 2019
Latest permitDorchester Exploration, Inc.Nov 4, 1981

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

11,500
total depth, ft
1
permits on file
Nov 4, 1981
last permit issued
Apr 10, 1982
completed
22.1K
cumulative oil, bbl
88.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 10, 1982
Shut in
Oct 1, 2019
Plugged
—

Operator's P-5 on the schedule: Active (A)

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
Bradford "22A" O-10-27285Bradford Ranch (Atoka)Diamondback E&P LLC122.1K88.2KJan 1993 – Jul 2026

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. 1Permian Resources, Inc.Jan 1993 → Mar 2003
  2. 2Endeavor Energy Resources L.P.May 2003 → Jun 2019

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
139579-99DrillDorchester Exploration, Inc.Nov 4, 1981Nov 4, 1981—11,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 10, 1982Bradford 22A O-10-27285Bradford Ranch (Atoka)Diamondback E&P LLCShut In · shut in Oct 1, 201911,500

Perforations

Perforated and open-hole intervals.

FromToType
11,30811,320Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
1635020700 S
10.754,85014.753,250 S
7.6259,8009.5675 S
5.511,5006.5320 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 12, 1984Apr 22, 1982—

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