WELL · 42-441-34550 · DISTRICT 7

Buffalo Gap #1

Y

Taylor County · Lake Abilene (4000) field · Shut IN  · Vertical

Buffalo Gap #1 (API 42-441-34550) is a well in Taylor County operated by Sojourner Drilling Corporation, completed April 1, 2017 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued February 21, 2017, permitted to 4,700 ft.

It was permitted by North American Drilling Corp and has since transferred to Sojourner Drilling Corporation on the wellbore schedule.

Completion filings report 10 formation tops, including Coleman Junction, Cisco, Palo Pinto, Cook - Disposal.

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

Operator of record

Sojourner Drilling Corporation

Permitted by North American Drilling Corp; the EWA schedule now lists a different operator.

Abilene, TX · P-5 Y, filed Jul 4, 2026 · 872 permits on file · (325) 669-2068

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSojourner Drilling Corporation
Production reportsnone
Latest permitNorth American Drilling CorpFeb 21, 2017

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

4,700
total depth, ft
1
permits on file
Feb 21, 2017
last permit issued
Apr 1, 2017
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2017 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 1, 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
Buffalo Gap O-8-32153Lake Abilene (4000)Sojourner Drilling Corporation100Apr 2017 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
823159-99DrillNorth American Drilling CorpFeb 10, 2017Feb 21, 2017Mar 26, 20174,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-32153————

Formation tops

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

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION - CORROSIVE, SW1,470455
CiscoCISCO - DISPOSAL3,277-1,352
Palo PintoPALO PINTO LIME - DISPOSAL3,708-1,783
Cook - Disposal——
Flippen - Disposal——
Hope Lime - Disposal——
King Sand - Disposal——
Saddle CreekSADDLE CREEK - DISPOSAL——
Swastika - Disposal——
Unidentified-County Regular - DI——

Perforations

Perforated and open-hole intervals.

FromToType
3,8593,862Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62511712.25130 S
4.54,0287.875300 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
00Aug 29, 2017Aug 8, 2017Yes

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