WELL · 42-321-02142 · DISTRICT 3

Stoddard-Lewis Unit #2

N

Matagorda County  · Vertical

Stoddard-Lewis Unit #2 (API 42-321-02142) is a former disposal or injection well in Matagorda County, last operated by Expro Engineering, Inc.; its UIC permit is no longer active.

The RRC has issued 2 drilling permits between 1993 and 1996, permitted to 10,310 ft.

Operator of record

Expro Engineering, Inc.

Based in
Fort Worth, TX
P-5 status
Active (A)
P-5 last filed
Jul 2, 2026
Permits on file
60
Phone
(817) 624-8425

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsExpro Engineering, Inc.through Nov 1996
Latest permitExpro Engineering, Inc.Aug 28, 1996
10,310
total depth, ft
2
permits on file
Aug 28, 1996
last permit issued
—
completed
0
cumulative oil, bbl
66.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Stoddard-Lewis Unit G-3-147005Duncan Slough (Frio Cons.)Atlas Operating LLC1066.1KMay 1993 – Jul 2026
Stoddard -A- G-3-6040Duncan Slough (Frio-6)Elliott Oil & Gas Company10722Jan 1993 – Nov 1993
Stoddard -A- O-3-6656Duncan Slough (Frio-5)Elliott Oil & Gas Company100Jan 1993 – Nov 1993

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. 1Elliott Oil & Gas CompanyJan 1993 → Feb 1993
  2. 2Expro Engineering, Inc.May 1993 → Nov 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
451946-99RecompletionExpro Engineering, Inc.Aug 27, 1996Aug 28, 1996—10,310
413593-99RecompletionElliott Oil & Gas CompanyJul 7, 1993Oct 1, 1993Apr 19, 199310,310

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-6040————
—— G-3-147005————
—— O-3-6656————

Perforations

Perforated and open-hole intervals.

FromToType
10,19410,206Perforated
10,95010,968Perforated
—10,620Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
71,666——
13.3752,000——
13.3752,001——
9.62510,099——
2.37510,593——

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 20, 1993Oct 14, 1993Yes
00Nov 3, 1993——
00Jan 12, 1984Jul 26, 1963—
00Jan 12, 1984——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
Dec 2007
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000095137W-14 DisposalNot activated1,5001,0903,700–3,850

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120062007

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