WELL · 42-173-36566 · DISTRICT 8

Carter 8 #1

Shut in

Glasscock County · Jailhouse (Fusselman) field · Shut IN  · Vertical

Carter 8 #1 (API 42-173-36566) is a well in Glasscock County operated by Apache Corporation, completed July 9, 2014 and listed as shut in on the RRC schedule, shut in February 1, 2025.

The RRC has issued one drilling permit, issued May 27, 2014, permitted to 10,228 ft.

Completion filings report 10 formation tops, including Santa Rosa, Yates, Seven Rivers, Queen.

Its lease has reported 107K barrels of oil and 402K mcf of gas since July 2014, 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 Feb 2026
Latest permitApache CorporationMay 27, 2014
10,228
total depth, ft
1
permits on file
May 27, 2014
last permit issued
Jul 9, 2014
completed
107K
cumulative oil, bbl
402K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 9, 2014
Shut in
Feb 1, 2025
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
Carter 8 O-10-46038Jailhouse (Fusselman)Apache Corporation1107K402KJul 2014 – Jul 2026

Oil, barrels lease total

Last 12 months 3 · prior 12 124(-98%)

050100202420252026

Gas, mcf lease total

Last 12 months 0 · prior 12 131(-100%)

0100200202420252026

Chain of custody

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

  1. 1Apache CorporationJul 2014 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
785046-99DrillApache CorporationApr 18, 2014May 27, 2014Jun 1, 201410,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 9, 2014Carter 8 O-10-46038Jailhouse (Fusselman)Apache CorporationShut IN · shut in Feb 1, 202510,228

Formation tops

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

FormationMD ftSubsea
Santa Rosa8501,795
Yates1,740905
Seven Rivers1,880765
Queen2,070575
Grayburg2,500145
San AndresSAN ANDRES - HIGH FLOWS, H2S, CO2,730-85
Glorieta3,460-815
Clear ForkCLEARFORK3,630-985
Spraberry4,630-1,985
Wichita-AlbanyWICHITA ALBANY5,240-2,595

Perforations

Perforated and open-hole intervals.

FromToType
10,12510,140Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37542317.5420 S
8.6253,22011850 S
5.510,2287.875930 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
00Apr 28, 2015Mar 13, 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.

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