TEXAS · WELLS · MONTAGUE COUNTY · ARMSTRONG LEASE · API 42-337-32897 · DISTRICT 7C

Armstrong #5

Y

Montague County · Montague County Regular field · Producing  · Vertical

Armstrong #5 (API 42-337-32897) is a well in Montague County operated by Mountain Creek Oil Company Inc., completed January 15, 1992 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 16, 1991, permitted to 3,310 ft.

Completion filings report 3 formation tops, including Hoosier Lime, Davenport Lime, Strawn.

Its lease has reported 7.59K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Mountain Creek Oil Company Inc.

Based in
Saint JO, TX
P-5 status
Active (A)
P-5 last filed
Sep 17, 2025
Permits on file
68
Phone
(940) 366-2370

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMountain Creek Oil Company Inc.
Production reportsMountain Creek Oil Company, Inc.through Apr 2026
Latest permitMountain Creek Oil Company, Inc.Dec 16, 1991
3,310
total depth, ft
1
permits on file
Dec 16, 1991
last permit issued
Jan 15, 1992
completed
7.59K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 15, 1992
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; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Armstrong O-13-18469Montague County RegularMountain Creek Oil Company, Inc.47.59K21Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 112 · prior 12 62(+81%)

051015202420252026

Chain of custody

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

  1. 1Mountain Creek Oil Company, Inc.Jan 1993 → Apr 2026
  2. 2Geurin Oil & GasOct 2002 → Oct 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
395131-99DrillMountain Creek Oil Company, Inc.Dec 16, 1991Dec 16, 1991Dec 27, 19913,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 15, 1992Armstrong O-13-18469Montague County RegularMountain Creek Oil Company Inc.Producing3,310

Formation tops

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

FormationMD ftSubsea
Hoosier Lime1,170-217
Davenport Lime1,990-1,037
StrawnSTRAWN SAND3,272-2,319

Perforations

Perforated and open-hole intervals.

FromToType
3,2223,228Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62540012.25250 S
4.53,3007.875100 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
00May 21, 1992Apr 28, 1992Yes
00May 5, 1992——

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