TEXAS · WELLS · HOWARD COUNTY · BUCHANAN 42 LEASE · API 42-227-37430 · DISTRICT 7B

Buchanan 42 #1

Plugged

Howard County · Spraberry (Trend Area) field  · Vertical

Buchanan 42 #1 (API 42-227-37430) is a plugged well in Howard County, plugged February 10, 2022, last operated by Bayswater Operating Company LLC.

The RRC has issued one drilling permit, issued April 8, 2013, permitted to 9,600 ft.

It was permitted by Apache Corporation and has since transferred to Bayswater Operating Company LLC on the wellbore schedule.

Completion filings report 7 formation tops, including Clear Fork, Spraberry, Dean, Wolfcamp.

Its lease has reported 10.3K barrels of oil and 37.6K mcf of gas since June 2013, with no volume in the three years through April 2026.

Operator of record

Bayswater Operating Company LLC

Permitted by Apache Corporation; the EWA schedule now lists a different operator.

Based in
Denver, CO
P-5 status
Active (A)
P-5 last filed
Sep 8, 2025
Permits on file
279
Phone
(303) 893-2503

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBayswater Operating Company LLC
Production reportsBayswater Operating Company LLCthrough Mar 2021
Latest permitApache CorporationApr 8, 2013

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

9,600
total depth, ft
1
permits on file
Apr 8, 2013
last permit issued
Oct 20, 2015
completed
10.3K
cumulative oil, bbl
37.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2013 THROUGH Mar 2021

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 20, 2015
Shut in
—
Plugged
Feb 10, 2022

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 42 O-10-44858Spraberry (Trend Area)Bayswater Operating Company LLC110.3K37.6KJun 2013 – Mar 2021

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. 1Apache CorporationSep 2013 → Nov 2019
  2. 2Bayswater Operating Company LLCDec 2019 → Mar 2021

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
760130-99DrillApache CorporationApr 5, 2013Apr 8, 2013May 1, 20139,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Oct 20, 2015Buchanan 42 O-10-44858Spraberry (Trend Area)Bayswater Operating Company LLCPlugged—

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK3,943-1,392
SpraberrySPRABERRY (UPPER)5,263-2,712
SpraberrySPRABERRY (LOWER)5,797-3,246
Dean6,443-3,892
Wolfcamp6,582-4,031
Strawn8,570-6,019
Atoka8,621-6,070
MississippianMISSISSIPPIAN LIME8,932-6,381

Perforations

Perforated and open-hole intervals.

FromToType
6,2726,864Perforated
6,2729,142Perforated
8,5908,610Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37543517.5435 S
8.6253,18811850 S
5.59,3857.875790 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 22, 2017Sep 12, 2017—
00Jul 31, 2014Apr 14, 2014Yes

Well logs

3 logs loaded from the RRC's log index, the latest received Jun 15, 2016. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans Clear Fork, Spraberry, Dean, Wolfcamp, Strawn, Atoka, MississippianTIFF100 to 9,364Jun 15, 2016run May 9, 20139.41
RESISTIVITYSpans Clear Fork, Spraberry, Dean, Wolfcamp, Strawn, Atoka, Mississippian2 TIFF3,170 to 9,364Jun 15, 2016run May 9, 20136.40 + 7.18
RESISTIVITYSpans Clear Fork, Spraberry, Dean, Wolfcamp, Strawn, Atoka, MississippianTIFF3,187 to 9,364Jun 15, 2016run May 9, 20133.28

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000114913H-1 InjectionPlugged Apr 24, 202310,0001,4752,950–8,970

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