WELL · 42-337-33900 · DISTRICT 9

McCall Storey #1H

N

Montague County · Newark East (Barnett Shale) field  · Horizontal

Mccall Storey #1H (API 42-337-33900) is a horizontal well in Montague County operated by Eog Resources Inc., completed April 18, 2007.

The RRC has issued one drilling permit (amended once), issued February 8, 2007, permitted to 8,500 ft.

Completion filings report 5 formation tops, including Ranger, Palo Pinto, Brazos River, Bryson.

Its 2 leases have reported 6.58K barrels of oil and 565K mcf of gas since April 2007, last reporting in July 2026. The leases carry 4 wells, so these are lease totals, not this well alone.

Operator of record

EOG Resources Inc.

Based in
Midland, TX
P-5 status
Active (A)
P-5 last filed
Oct 2, 2025
Permits on file
16,348
Phone
(713) 651-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEOG Resources Inc.
Production reportsEOG Resources, Inc.through Aug 2025
Latest permitEOG Resources, Inc.Jan 16, 2008
8,500
total depth, ft
2
permits on file
Jan 16, 2008
last permit issued
Apr 18, 2007
completed
6.58K
cumulative oil, bbl
565K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 18, 2007
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 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
McCall Storey G-13-277643Newark, East (Barnett Shale)EOG Resources, Inc.10452KApr 2007 – Jul 2026
McCall Storey O-13-31015Newark, East (Barnett Shale)EOG Resources, Inc.36.58K113KApr 2007 – Dec 2015

Gas, mcf lease total

Last 12 months 1 · prior 12 512(-100%)

01K2K202420252026

Chain of custody

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

  1. 1EOG Resources, Inc.May 2008 → Aug 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
633033-98DrillEOG Resources, Inc.Jan 8, 2008Jan 16, 2008Mar 13, 20078,500
633033-99DrillEOG Resources, Inc.Feb 5, 2007Feb 8, 2007Mar 13, 20078,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-277643————
—— O-13-31015————

Formation tops

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

FormationMD ftSubsea
Ranger1,650-549
Palo Pinto2,820-1,719
Brazos River3,830-2,729
Bryson4,930-3,829
Barnett6,869-5,768
Barnett6,935-5,834
BarnettBARNETT SHALE7,113-6,012
BarnettBARNETT SHALE7,800-6,699

Perforations

Perforated and open-hole intervals.

FromToType
9,35110,444Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62588512.25485 S
77,1648.75585 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
00Aug 31, 2015Jun 30, 2014—
00Aug 16, 2010May 1, 2008Yes
00Jul 1, 2010——

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