WELL · 42-285-00395 · DISTRICT 2

Iaves I. S. #1

Plugged

Lavaca County · Speaks SW. (Wilcox -A-) field  · Vertical

Iaves I. S. #1 (API 42-285-00395) is a plugged well in Lavaca County, plugged October 9, 2002, last operated by North Central Oil Corp..

The RRC has issued one drilling permit, issued October 8, 1990, permitted to 9,413 ft.

It was permitted by Coastal Plains Energy, Inc. and has since transferred to North Central Oil Corp. on the wellbore schedule.

Completion filings report 4 formation tops, including Miocene (undifferentiated), Frio, Yegua, Wilcox.

Its lease has reported 4.18K barrels of oil and 191K mcf of gas since January 1993, last reporting in November 2002.

Operator of record

North Central Oil Corp.

Permitted by Coastal Plains Energy, Inc.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed May 4, 2007 · 558 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNorth Central Oil Corp.
Production reportsCoastal Plains Energy, Inc.through Nov 1999
Latest permitCoastal Plains Energy, Inc.Oct 8, 1990

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

9,413
total depth, ft
1
permits on file
Oct 8, 1990
last permit issued
May 1, 1958
completed
4.18K
cumulative oil, bbl
191K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 1, 1958
Shut in
—
Plugged
Oct 9, 2002

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
Eaves O-2-7696Speaks, SW. (Wilcox -A-)Coastal Plains Energy, Inc.14.18K191KJan 1993 – Nov 2002

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. 1Coastal Plains Energy, Inc.Jan 1993 → Oct 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
379091-99ReenterCoastal Plains Energy, Inc.Oct 8, 1990Oct 8, 1990Oct 8, 19909,413

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-7696————

Formation tops

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

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE1,000-839
Frio1,850-1,689
Yegua3,050-2,889
Wilcox8,380-8,219

Perforations

Perforated and open-hole intervals.

FromToType
8,4688,551Perforated
8,5188,532Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,06215375 S
5.58,6527.875520 S
5.5—7.875205 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 19, 2000Feb 9, 2000—
00Jun 5, 1991May 1, 1991Yes
00May 13, 1991——
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.

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