WELL · 42-353-32184 · DISTRICT 7

Armstrong #1

Plugged

Nolan County · Nolan County Regular field  · Vertical

Armstrong #1 (API 42-353-32184) is a plugged well in Nolan County, plugged February 13, 2020, last operated by Clear Water Inc..

The RRC has issued one drilling permit (amended once), issued November 27, 1991, permitted to 4,300 ft.

It was permitted by ST. Clair Energy Corporation and has since transferred to Clear Water Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Coleman Junction, Cisco.

Its lease has reported 61.3K barrels of oil and 56 mcf of gas since January 1993, last reporting in March 2021.

Operator of record

Clear Water Inc.

Permitted by St. Clair Energy Corporation; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Jan 4, 2026 · 57 permits on file · (432) 528-6751

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleClear Water Inc.
Production reportsClear Water Inc.through Aug 2017
Latest permitSt. Clair Energy CorporationNov 27, 1991

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

4,300
total depth, ft
2
permits on file
Nov 27, 1991
last permit issued
Dec 16, 1991
completed
61.3K
cumulative oil, bbl
56
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2021

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 16, 1991
Shut in
—
Plugged
Feb 13, 2020

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
Armstrong O-8-26446Nolan County RegularClear Water Inc.161.3K56Jan 1993 – Mar 2021

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. 1St. Clair Energy CorporationJan 1993 → Apr 2003
  2. 2Manhattan Petroleum, Inc.May 2003 → Jul 2003
  3. 3Clear Water Inc.Aug 2003 → Aug 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
394406-98DrillSt. Clair Energy CorporationFeb 13, 1992Nov 27, 1991Dec 2, 19914,100
394406-99DrillSt. Clair Energy CorporationNov 25, 1991Nov 27, 1991—4,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-26446————

Formation tops

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

FormationMD ftSubsea
Coleman Junction3,155-994
CiscoCISCO LIME3,890-1,729

Perforations

Perforated and open-hole intervals.

FromToType
4,0314,033Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62529112.25250 S
5.54,0377.875350 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 13, 1992Jan 6, 1992Yes
00Feb 21, 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/35332184, documented in the API reference.