WELL · 42-351-30836 · DISTRICT 3

BP Black Stone a-472 SWD #1

WaterN

Newton County · Magnolia Springs (Austin Chalk) field  · Horizontal

BP Black Stone A-472 Swd #1 (API 42-351-30836) is a disposal or injection well in Newton County operated by Anadarko E&P Company LP under an active UIC permit.

The RRC has issued 2 drilling permits in 2010, permitted to 16,000 ft.

Completion filings report 3 formation tops, including Frio, Wilcox, Navarro.

It holds an active disposal or injection permit, with 47.1K barrels injected in the 12 months reported through December 2025.

Operator of record

Anadarko E&P Company LP

Houston, TX · P-5 Y, filed Jul 4, 2025 · 2,635 permits on file · (832) 636-1111

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAnadarko E&P Company LP
Production reportsnone
Latest permitAnadarko E&P Company LPJul 9, 2010
16,000
total depth, ft
2
permits on file
Jul 9, 2010
last permit issued
—
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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
BP Black Stone a-472 Unit G-3-257521Magnolia Springs (Austin Chalk)Zarvona Energy LLC100Apr 2010 – Jul 2026
BP Black Stone a-472 SWD G-3-258899Magnolia Springs (Austin Chalk)Anadarko E&P Company LP100Aug 2010 – Aug 2010

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
698210-99RecompletionAnadarko E&P Company LPJun 28, 2010Jul 9, 2010—13,000
690145-99DrillAnadarko E&P Company LPJan 22, 2010Jan 27, 2010Mar 28, 201016,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-257521————
—— G-3-258899————

Formation tops

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

FormationMD ftSubsea
Frio4,290-4,020
Wilcox6,783-6,513
Navarro12,106-11,836

Perforations

Perforated and open-hole intervals.

FromToType
4,4125,339Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3753,11517.54,040 S
13.3753,21117.54,040 S
9.6256,87612.252,360 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
00Feb 22, 2011Nov 15, 2010—
00Feb 16, 2011——
00Sep 28, 2010Jul 12, 2010Yes

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

47.1K
bbl, last 12 reported months
6.21M
bbl, all reported
Dec 2025
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000101677W-14 DisposalActive20,0001,8503,700–5,800

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 47,055 · prior 12 16,787(+180%)

05K10K20242025

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