WELL · 42-173-33987 · DISTRICT 8

Rooster 17 #1

Y

Glasscock County · Spraberry (Trend Area) field · Producing  · Vertical

Rooster 17 #1 (API 42-173-33987) is a well in Glasscock County operated by Apache Corporation, completed May 15, 2011 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued January 20, 2011, permitted to 10,304 ft.

Completion filings report 3 formation tops, including Wolfcamp, Strawn, Atoka.

Its lease has reported 27.8K barrels of oil and 143K mcf of gas since May 2011, last reporting in July 2026.

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 CorporationJan 20, 2011
10,304
total depth, ft
2
permits on file
Jan 20, 2011
last permit issued
May 15, 2011
completed
27.8K
cumulative oil, bbl
143K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2011 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 15, 2011
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Rooster 17 O-10-41346Spraberry (Trend Area)Apache Corporation127.8K143KMay 2011 – Jul 2026

Gas, mcf lease total

Last 12 months 4,189 · prior 12 4,504(-7%)

0200400600202420252026

Oil, barrels lease total

Last 12 months 677 · prior 12 654(+4%)

050100202420252026

Chain of custody

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

  1. 1Apache CorporationJun 2011 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
708685-98DrillApache CorporationApr 8, 2011Jan 20, 2011Feb 27, 201110,450
708685-99DrillApache CorporationJan 18, 2011Jan 20, 2011—10,450

Completions

CompletedLeaseFieldOperatorStatusDepth
May 15, 2011Rooster 17 O-10-41346Spraberry (Trend Area)Apache CorporationProducing10,304

Formation tops

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

FormationMD ftSubsea
Wolfcamp6,312-3,663
Strawn9,400-6,751
Atoka9,693-7,044

Perforations

Perforated and open-hole intervals.

FromToType
7,1887,481Perforated
7,5107,725Perforated
7,7638,000Perforated
8,0878,363Perforated
8,4058,722Perforated
8,7669,058Perforated
9,0979,397Perforated
9,4289,608Perforated
9,6399,967Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37538017.5375 S
8.6253,27011800 S
5.510,3047.8751,125 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 29, 2012Jun 10, 2011Yes

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