WELL · 42-459-31014 · DISTRICT 6

Smith W.F. GU #4

N

Upshur County · Gilmer(jurassic) field  · Vertical

Smith W.F. GU #4 (API 42-459-31014) is a well in Upshur County operated by Apache Corporation, completed August 22, 2000.

The RRC has issued 2 drilling permits between 2000 and 2008, permitted to 12,100 ft.

Completion filings report 7 formation tops, including B. Austin Chalk, B. Mass Anhydrite, B. Mass. Anhydrite, Pettit.

No lease production has been reported under this well’s leases.

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 Sep 2009
Latest permitApache CorporationJun 3, 2008
12,100
total depth, ft
2
permits on file
Jun 3, 2008
last permit issued
Aug 22, 2000
completed
0
cumulative oil, bbl
277K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 22, 2000
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Smith, W.F. Gas Unit G-6-243316Gilmer (Cotton Valley Sands)Diversified Production LLC1012.6KOct 2008 – Jul 2026
Smith, W.F. GU G-6-179010Gilmer(jurassic)Apache Corporation10264KAug 2000 – Apr 2009

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. 1Apache CorporationAug 2000 → Sep 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
661850-99RecompletionApache CorporationMay 13, 2008Jun 3, 2008Jun 17, 200812,100
495392-99DrillApache CorporationMay 23, 2000May 23, 2000Jul 1, 200012,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-179010————
—— G-6-243316————

Formation tops

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

FormationMD ftSubsea
B. Austin Chalk4,910-4,474
B. Mass Anhydrite7,400-6,964
B. Mass. Anhydrite7,400-6,964
Pettit7,943-7,507
Travis Peak8,092-7,656
BossierBOSSIER SHALE10,886-10,450
Haynesville11,738-11,302

Perforations

Perforated and open-hole intervals.

FromToType
11,08411,094Perforated
11,74211,752Perforated
11,76211,767Perforated
11,83611,845Perforated
11,85011,861Perforated
11,89211,916Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6254,22012.25890 S
5.512,1007.875400 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
00Jun 21, 2013Jun 10, 2013—
00Feb 2, 2009Dec 11, 2008Yes
00Dec 30, 2008——
00Nov 6, 2000Sep 13, 2000Yes
00Oct 16, 2000——

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