WELL · 42-177-31494 · DISTRICT 1

Eckols #1

Plugged

Gonzales County · Christian (6800) field  · Vertical

Eckols #1 (API 42-177-31494) is a plugged well in Gonzales County, plugged February 1, 1997, last operated by Regal Petroleum Services.

The RRC has issued one drilling permit, issued November 7, 1983, permitted to 7,000 ft.

It was permitted by Catlett, E. G. and has since transferred to Regal Petroleum Services on the wellbore schedule.

Completion filings report 4 formation tops, including Anacacho, Austin Chalk, Eagle Ford, Buda.

Its lease has reported 1.43K barrels of oil and 11 mcf of gas since January 1993, last reporting in March 1997.

Operator of record

Regal Petroleum Services

Permitted by Catlett, E. G.; the EWA schedule now lists a different operator.

Euless, TX · P-5 Y, filed Apr 4, 2003 · 37 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRegal Petroleum Services
Production reportsRegal Petroleum Servicesthrough Oct 1995
Latest permitCatlett, E. G.Nov 7, 1983

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

7,000
total depth, ft
1
permits on file
Nov 7, 1983
last permit issued
Jan 23, 1984
completed
1.43K
cumulative oil, bbl
11
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 1997

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 23, 1984
Shut in
—
Plugged
Feb 1, 1997

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
Eckols O-1-9431Christian (6800)Regal Petroleum Services11.43K11Jan 1993 – Mar 1997

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. 1Austral Oil Company IncorporatedApr 1993 → Jul 1993
  2. 2Evantech Energy Corp.Aug 1993 → Jan 1995
  3. 3Regal Petroleum ServicesOct 1995 → Oct 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
220098-99DrillCatlett, E. G.Nov 7, 1983Nov 7, 1983Dec 8, 19837,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-9431————

Formation tops

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

FormationMD ftSubsea
Anacacho6,082-5,703
Austin ChalkAUSTIN6,204-5,825
Eagle FordEAGLEFORD6,544-6,165
Buda6,610-6,231

Perforations

Perforated and open-hole intervals.

FromToType
6,6406,650Perforated
6,6546,668Perforated
6,6706,674Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62580010.75405 S
4.56,7207.8751,234 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 18, 1984Feb 17, 1984—
00Apr 11, 1984Feb 17, 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.

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