WELL · 42-329-40782 · DISTRICT 8

Buchanan Ranch SWD #1

WaterY

Midland County · Spraberry (Trend Area) field · Injection  · Vertical

Buchanan Ranch Swd #1 (API 42-329-40782) is a well in Midland County operated by Amrich Operating LLC, completed July 5, 2017 and listed as injection on the RRC schedule.

The RRC has issued one drilling permit, issued February 3, 2016, permitted to 6,000 ft.

Completion filings report 9 formation tops, including Yates, Queen, Grayburg, San Andres.

No lease production has been reported under this well’s leases.

It holds an active disposal or injection permit, with 2.69M barrels injected in the 12 months reported through January 2026.

Operator of record

Amrich Operating LLC

The Woodlands, TX · P-5 Y, filed Sep 4, 2025 · 4 permits on file · (830) 254-0520

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAmrich Operating LLC
Production reportsnone
Latest permitAmrich Operating, LLCFeb 3, 2016
6,000
total depth, ft
1
permits on file
Feb 3, 2016
last permit issued
Jul 5, 2017
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 5, 2017
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Buchanan Ranch SWD O-10-49523Spraberry (Trend Area)Amrich Operating, LLC100Jul 2017 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
813526-99DrillAmrich Operating, LLCJan 28, 2016Feb 3, 2016Jun 22, 20176,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-49523————

Formation tops

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

FormationMD ftSubsea
Yates2,468112
Queen3,440-860
Grayburg3,918-1,338
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO4,235-1,655
Glorieta5,330-2,750
Clear ForkCLEARFORK——
Santa Rosa——
Seven Rivers——
Spraberry——
SpraberrySPRABERRY UPPER-DEAN——

Perforations

Perforated and open-hole intervals.

FromToType
4,8756,000Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62533512.25180 S
74,8758.75420 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
00Mar 14, 2018Sep 5, 2017—

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

2.69M
bbl, last 12 reported months
18M
bbl, all reported
Jan 2026
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000113695W-14 DisposalActive20,0002,3004,600–6,000

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

Last 12 months 2,687,877 · prior 12 1,947,328(+38%)

0100K200K300K20252026

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