WELL · 42-461-39180 · DISTRICT 7

CC #3731HU

Y

Upton County · Spraberry (Trend Area) field · Shut IN  · Horizontal

CC #3731HU (API 42-461-39180) is a horizontal well in Upton County operated by Apache Corporation, completed July 13, 2014 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued December 31, 2013, permitted to 9,500 ft.

Completion filings report 10 formation tops, including Yates, Grayburg, San Andres, Clear Fork.

Its lease has reported 4.97M barrels of oil and 15.3M mcf of gas since October 2009, last reporting in July 2026. The lease carries 52 wells, so these are lease totals, not this well alone.

Operator of record

Apache Corporation

Houston, TX · P-5 Y, filed Oct 4, 2025 · 9,754 permits on file · (713) 296-6400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleApache Corporation
Production reportsApache Corporationthrough Apr 2026
Latest permitApache CorporationDec 31, 2013
9,500
total depth, ft
1
permits on file
Dec 31, 2013
last permit issued
Jul 13, 2014
completed
4.97M
cumulative oil, bbl
15.3M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 13, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
CC O-9-17037Spraberry (Trend Area)Apache Corporation524.97M15.3MOct 2009 – Jul 2026

Gas, mcf lease total

Last 12 months 759,239 · prior 12 851,159(-11%)

050K100K202420252026

Oil, barrels lease total

Last 12 months 99,000 · prior 12 109,803(-10%)

05K10K15K202420252026

Chain of custody

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

  1. 1Mariner Energy, Inc.Nov 2009 → Nov 2010
  2. 2Apache CorporationDec 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
774096-99DrillApache CorporationNov 19, 2013Dec 31, 2013Feb 13, 20149,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-17037————

Formation tops

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

FormationMD ftSubsea
Yates2,670127
Grayburg3,970-1,173
San AndresSAN ANDRES - SALTWATER FLOW4,050-1,253
Clear ForkCLEARFORK6,683-3,886
Spraberry7,545-4,748
Wolfcamp9,081-6,284
Devonian——
Ellenburger——
Fusselman——
Strawn——

Perforations

Perforated and open-hole intervals.

FromToType
9,69014,453Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37542317.5455 S
9.6258,59612.251,165 S
5.514,5758.51,830 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
00Dec 15, 2014Nov 14, 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/46139180, documented in the API reference.