WELL · 42-097-32989 · DISTRICT 9

Blakely -A- #2

Plugged

Cooke County · Cooke County Regular field  · Vertical

Blakely -A- #2 (API 42-097-32989) is a plugged well in Cooke County, plugged April 6, 2015, last operated by BP Petroleum Operations LLC.

The RRC has issued one drilling permit (amended once), issued July 20, 1989, permitted to 1,999 ft.

It was permitted by August Oil and has since transferred to BP Petroleum Operations LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Hosser, Davenport, Ellenburger.

Its lease has reported 4.02K barrels of oil and 157 mcf of gas since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

BP Petroleum Operations LLC

Permitted by August Oil; the EWA schedule now lists a different operator.

Nocona, TX · P-5 Y, filed Mar 4, 2026 · (940) 210-4794

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBP Petroleum Operations LLC
Production reportsC & O Productionthrough Aug 2016
Latest permitAugust OilJul 20, 1989

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

1,999
total depth, ft
2
permits on file
Jul 20, 1989
last permit issued
Aug 8, 1989
completed
4.02K
cumulative oil, bbl
157
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 8, 1989
Shut in
—
Plugged
Apr 6, 2015

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Blakely -A- O-13-27524Cooke County RegularBP Petroleum Operations, LLC24.02K157Jan 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. 1Triple G Well Service, Inc.Jan 1993 → Feb 1994
  2. 2August OilMar 1994 → Jun 1994
  3. 3Lynx Oil Co., Inc.Jul 1994 → Dec 1996
  4. 4W.B. OperatingMar 2001 → Jul 2001
  5. 5C & O ProductionAug 2001 → Aug 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
361762-98DrillAugust OilJul 20, 1989Jul 20, 1989—1,999
361762-99DrillAugust OilJul 20, 1989Jul 20, 1989—1,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-27524————

Formation tops

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

FormationMD ftSubsea
Hosser1,052-244
Davenport1,320-512
Ellenburger1,986-1,178

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,4008.625—

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
00Feb 22, 1990Nov 20, 1989Yes
00Feb 3, 1990——

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