WELL · 42-235-35512 · DISTRICT 7

Scott Sugg 3332 #H 53M

Y

Irion County · Lin (Wolfcamp) field · Producing  · Horizontal

Scott Sugg 3332 #H 53M (API 42-235-35512) is a horizontal well in Irion County operated by Apache Corporation, completed March 3, 2014 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued June 27, 2013, permitted to 9,999 ft.

Completion filings report 5 formation tops, including San Andres, Clear Fork, Spraberry, Dean.

Its lease has reported 1.14M barrels of oil and 10.8M mcf of gas since February 2014, last reporting in July 2026. The lease carries 8 wells, so these are lease totals, not this well alone.

Operator of record

Apache Corporation

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Dec 3, 2025
Permits on file
9,756
Phone
(713) 954-5500

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleApache Corporation
Production reportsApache Corporationthrough Apr 2026
Latest permitApache CorporationJun 27, 2013
9,999
total depth, ft
2
permits on file
Jun 27, 2013
last permit issued
Mar 3, 2014
completed
1.14M
cumulative oil, bbl
10.8M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 3, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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 8 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Scott Sugg 3332 O-9-18524Lin (Wolfcamp)Apache Corporation81.14M10.8MFeb 2014 – Jul 2026

Gas, mcf lease total

Last 12 months 734,265 · prior 12 690,016(+6%)

050K100K202420252026

Oil, barrels lease total

Last 12 months 13,929 · prior 12 19,452(-28%)

01K2K3K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Apache CorporationFeb 2014 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
765288-98DrillApache CorporationJun 18, 2014Jun 27, 2013Nov 7, 20139,999
765288-99DrillApache CorporationJun 24, 2013Jun 27, 2013Nov 7, 20139,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-18524————

Formation tops

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

FormationMD ftSubsea
San Andres1,805815
Clear ForkCLEARFORK3,350-730
Spraberry5,210-2,590
Dean6,068-3,448
Wolfcamp6,203-3,583

Perforations

Perforated and open-hole intervals.

FromToType
7,78715,282Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37571117.5750 S
9.6256,33712.25500 S
5.515,3618.753,050 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
00Jul 29, 2014May 19, 2014Yes

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) and the University Lands library. 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/23535512, documented in the API reference.