WELL · 42-207-33042 · DISTRICT 7

Goetz #1

Y

Haskell County · Sojourner field · Shut IN  · Vertical

Goetz #1 (API 42-207-33042) is a well in Haskell County operated by S.B. Street Operating Inc., completed October 8, 2024 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued August 21, 2024, permitted to 6,000 ft.

Completion filings report 10 formation tops, including Canyon, Cisco, Coleman Junction, Cook Sand - Disposal.

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

Operator of record

S.B. Street Operating Inc.

Graham, TX · P-5 Y, filed Dec 4, 2025 · 274 permits on file · (325) 226-1585

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleS.B. Street Operating Inc.
Production reportsnone
Latest permitS.B. Street Operating, Inc.Aug 21, 2024
6,000
total depth, ft
1
permits on file
Aug 21, 2024
last permit issued
Oct 8, 2024
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2024 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 8, 2024
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

33.149939, -99.776418

OpenStreetMap → ·  Google Maps →

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

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
Goetz O-8-32801SojournerS.B. Street Operating, Inc.100Oct 2024 – Jul 2026

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
902054-99DrillS.B. Street Operating, Inc.Aug 14, 2024Aug 21, 2024Aug 28, 20246,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-32801————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON - DISPOSAL——
CiscoCISCO SAND - DISPOSAL——
Coleman Junction——
Cook Sand - Disposal——
GunsightGUNSIGHT LIME - DISPOSAL——
Home Creek Lime - Disposal——
King Sand - Disposal——
Swastika - Disposal——
TannehillTANNEHILL SAND - DISPOSAL——
Unidentified-County Regular - DI——

Perforations

Perforated and open-hole intervals.

FromToType
5,1595,168Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62510212.2585 S
5.55,5157.875200 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 20, 2025Mar 4, 2025Yes

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's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Cahill42-207-33030

0.3 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,650-92
Home Creek Lime - Disposal3,385-1,827
Sojourner Sand5,318-3,760
Tannehill—
Unidentified-County Regular - DI—
Gunsight—
King Sand - Disposal—
Swastika - Disposal—

10 TOPS · FIRST 8

Cahill42-207-33041

0.4 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,660-103
Home Creek Lime - Disposal3,385-1,828
Sojourner Sand5,323-3,766
Tannehill—
Swastika - Disposal—
King Sand - Disposal—
Gunsight—
Cisco—

10 TOPS · FIRST 8

Cahill42-207-33043

0.6 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,660-97
Home Creek Lime - Disposal3,385-1,822
Sojourner Sand5,325-3,762
Gunsight—
Unidentified-County Regular - DI—
Tannehill—
Swastika - Disposal—
King Sand - Disposal—

10 TOPS · FIRST 8

Cahill42-207-33039

0.6 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,660-98
Home Creek Lime - Disposal3,385-1,823
Canyon4,585-3,023
Gunsight—
Swastika - Disposal—
Tannehill—
Unidentified-County Regular - DI—
King Sand - Disposal—

10 TOPS · FIRST 8

Cahill42-207-33065

0.7 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,650-84
Home Creek Lime - Disposal3,385-1,819
Canyon4,585-3,019
Unidentified-County Regular - DI—
Cisco—
Cook Sand - Disposal—
Gunsight—
King Sand - Disposal—

10 TOPS · FIRST 8

Cahill42-207-33054

0.9 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,660-95
Home Creek Lime - Disposal3,385-1,820
Canyon4,585-3,020
Swastika - Disposal—
King Sand - Disposal—
Tannehill—
Gunsight—
Cook Sand - Disposal—

10 TOPS · FIRST 8

Middlebrook42-207-32881

2.2 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,650-84
Home Creek Lime - Disposal3,385-1,819
Sojourner5,208-3,642
Swastika - Disposal—
Tannehill—
Unidentified-County Regular - DI—
Cook Sand - Disposal—
King Sand - Disposal—

10 TOPS · FIRST 8

Middlebrook42-207-33011

2.5 KM · Wilcox Petroleum Operating LLC. · Section with this well →

Coleman Junction1,650-97
Home Creek Lime - Disposal3,385-1,832
Canyon4,585-3,032
Gunsight—
Cisco—
Unidentified-County Regular - DI—
Tannehill—
Swastika - Disposal—

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