WELL · 42-321-31419 · DISTRICT 3

Hickl E. L. et AL #2

Plugged

Matagorda County · Mellon (10500) field  · Vertical

Hickl E. L. ET AL #2 (API 42-321-31419) is a plugged well in Matagorda County, plugged October 14, 2019, last operated by Sandel Operating Company.

The RRC has issued 2 drilling permits between 1984 and 1996, permitted to 11,000 ft.

It was permitted by Expro Engineering, Inc. and has since transferred to Sandel Operating Company on the wellbore schedule.

Completion filings report one formation top, including Mellon (10500).

Operator of record

Sandel Operating Company

Permitted by Expro Engineering, Inc.; the EWA schedule now lists a different operator.

Huntsville, TX · P-5 Active, filed Oct 17, 2025 · 11 permits on file · (936) 291-1002

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSandel Operating Company
Production reportsSandel Operating Companythrough Jul 2016
Latest permitExpro Engineering, Inc.Feb 13, 1996

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

11,000
total depth, ft
2
permits on file
Feb 13, 1996
last permit issued
Jul 5, 1996
completed
0
cumulative oil, bbl
143K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 2019

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 5, 1996
Shut in
—
Plugged
Oct 14, 2019

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
Hickl, E. L. et AL G-3-114679Mellon (10500)Sandel Operating Company10143KJan 1993 – Oct 2019

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. 1Expro Engineering, Inc.Jan 1993 → Dec 2008
  2. 2Sandel Operating CompanySep 2010 → Jul 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
443411-99RecompletionExpro Engineering, Inc.Jan 4, 1996Feb 13, 1996Jul 2, 199610,687
257071-99DrillPend Oreille Oil & Gas Co.Oct 31, 1984Nov 7, 1984Dec 4, 198411,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-114679————

Formation tops

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

FormationMD ftSubsea
Mellon (10500)10,562-10,508

Perforations

Perforated and open-hole intervals.

FromToType
10,56010,570Perforated
10,56210,570Perforated
10,57810,588Perforated
10,57810,594Perforated
10,60710,631Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,03012.25500 S
5.510,6718.75400 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
00Sep 24, 1996Aug 28, 1996Yes
00Feb 8, 1985Jan 28, 1985—
00Feb 6, 1985Jan 17, 1985—

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