WELL · 42-207-32965 · DISTRICT 8

BS-36.897 CR 448 #1901CP

N

Haskell County  · Vertical

BS-36.897 CR 448 #1901CP (API 42-207-32965) is a permitted well in Haskell County filed by Plains Pipeline L.P.; no completion report is on file yet.

The RRC has issued one drilling permit, issued September 13, 2019, permitted to 400 ft.

Operator of record

Plains Pipeline L.P.

Houston, TX · P-5 Y, filed Nov 4, 2025 · 70 permits on file · (713) 306-3298

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitPlains Pipeline L.P.Sep 13, 2019
400
total depth, ft
1
permits on file
Sep 13, 2019
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

33.079866, -99.905457

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Haskell County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
856928-99DrillPlains Pipeline L.P.Sep 9, 2019Sep 13, 2019—400

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Ramm Unit42-207-30836

5.4 KM · Crown Production Co., Inc. · Section with this well →

Tannehill2,410-831
King Sand - Disposal2,750-1,171
Gunsight2,840-1,261
Home Creek Lime - Disposal3,200-1,621
Cisco3,210-1,631
Canyon3,290-1,711
Cook Sand - Disposal—
Swastika - Disposal—

10 TOPS · FIRST 8

Whalen42-207-33001

6.2 KM · JQL Energy, LLC · Section with this well →

Coleman Junction1,710-106
Caddo5,455-3,851
Conglomerate5,680-4,076
Tannehill—
Swastika - Disposal—
King Sand - Disposal—
Gunsight—
Cook Sand - Disposal—

10 TOPS · FIRST 8

Wendeborn, F.W.42-207-32662

6.5 KM · JQL Energy, LLC · Section with this well →

Gunsight2,828-1,244
Swastika2,867-1,283

F.W. Wendeborn42-207-32982

6.5 KM · Crown Equipment Co. · Section with this well →

Coleman Junction1,400172
Tannehill2,300-728
Cook Sand - Disposal2,600-1,028
King Sand - Disposal2,750-1,178
Gunsight2,790-1,218
Swastika - Disposal2,930-1,358
Cisco3,060-1,488
Home Creek Lime - Disposal3,600-2,028

10 TOPS · FIRST 8

Wendeborn, F.W.42-207-32745

6.6 KM · Rister Oil&gas International LLC · Section with this well →

Swastika "A"2,868-1,284
Swastika "B"2,890-1,306
Swastika "C"2,900-1,316

Baba Looey42-207-33046

6.8 KM · Trio Consulting & Management,llc · Section with this well →

Coleman Junction1,730-112
Canyon4,370-2,752
Cisco—
Cook Sand - Disposal—
Gunsight—
Home Creek Lime - Disposal—
King Sand - Disposal—
Swastika - Disposal—

10 TOPS · FIRST 8

Cricket (Strawn) Unit42-207-32940

7.1 KM · Sojourner Drilling Corporation · Section with this well →

Coleman Junction1,892-333
Tannehill2,387-828
King Sand - Disposal2,889-1,330
Gunsight2,969-1,410
Swastika - Disposal3,039-1,480
Home Creek Lime - Disposal3,107-1,548
Cisco3,112-1,553
Jud Sand4,977-3,418

10 TOPS · FIRST 8

Kupatt42-207-33055

7.2 KM · Arnot Oil Company, LLC · Section with this well →

Coleman Junction1,800-146
Cisco—
Home Creek Lime - Disposal—
Gunsight—
Canyon—
Cook Sand - Disposal—
Unidentified-County Regular - DI—
Tannehill—

10 TOPS · FIRST 8

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