WELL · 42-485-45869 · DISTRICT 9

Goetze Bros. #4

Y

Wichita County · Wichita County Regular field · Shut IN  · Vertical

Goetze Bros. #4 (API 42-485-45869) is a well in Wichita County operated by Macha Enterprises Inc., completed July 16, 2015 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued June 16, 2015, permitted to 2,000 ft.

Completion filings report 9 formation tops, including Thomas Sand, Bluff Creek Sand, Canyon, Cisco.

Its lease has reported 1.27K barrels of oil since January 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

It holds an active disposal or injection permit.

Operator of record

Macha Enterprises Inc.

Wichita Falls, TX · P-5 Y, filed Jul 4, 2026 · 8 permits on file · (940) 631-9083

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMacha Enterprises Inc.
Production reportsMacha Enterprises, Inc.through Nov 2022
Latest permitMacha Enterprises, Inc.Jun 16, 2015
2,000
total depth, ft
1
permits on file
Jun 16, 2015
last permit issued
Jul 16, 2015
completed
1.27K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 16, 2015
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Goetze Bros. O-13-10968Wichita County RegularMacha Enterprises, Inc.21.27K0Jan 1993 – Jul 2026

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. 1McClure BrothersJan 1998 → Aug 1998
  2. 2Macha Enterprises, Inc.Apr 2011 → Nov 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
807384-99DrillMacha Enterprises, Inc.Jun 10, 2015Jun 16, 2015Jun 23, 20152,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-10968————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Thomas Sand1,450
Bluff Creek Sand—
CanyonCANYON SAND—
Cisco—
GunsightGUNSIGHT LIME—
GunsightGUNSIGHT SAND—
KMA—
Strawn—
Tannehill—
Vogstberger—

Perforations

Perforated and open-hole intervals.

FromToType
1,4531,457Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6256212.2550 S
5.51,5507.875230 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 2, 2016Dec 14, 2015Yes

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

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000125403H-1 InjectionActive3007261,452–1,476

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