WELL · 42-321-31877 · DISTRICT 3

State Tract 295 #1

N

Matagorda County · Oyster Lake W. (3750) field  · Vertical

State Tract 295 #1 (API 42-321-31877) is a well in Matagorda County operated by Main Energy Inc., completed June 15, 2001.

The RRC has issued 2 drilling permits (amended once) between 2001 and 2002, permitted to 4,417 ft.

Completion filings report one formation top, including Miocene (undifferentiated).

No lease production has been reported under this well’s leases.

Operator of record

Main Energy Inc.

Houston, TX · P-5 Y, filed Apr 2, 2010 · 32 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMain Energy Inc.
Production reportsMain Energy, Inc.through Jan 2009
Latest permitMain Energy, Inc.Nov 18, 2002
4,417
total depth, ft
3
permits on file
Nov 18, 2002
last permit issued
Jun 15, 2001
completed
0
cumulative oil, bbl
417K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State Tract 295 G-3-196814Oyster Lake, W. (1300)Coastland Operations, LLC10164KMay 2003 – Jul 2026
State Tract 295 G-3-196816Oyster Lake, W. (1400)Coastland Operations, LLC10166KMay 2003 – Jul 2026
State Tract 295 G-3-187423Oyster Lake, W. (3750)Main Energy, Inc.1042.8KJun 2001 – May 2003
State Tract 295 G-3-187424Oyster Lake, W. (1800)Main Energy, Inc.1045.5KJun 2001 – May 2003

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. 1Main Energy, Inc.Jul 2001 → Jan 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
525431-99RecompletionMain Energy, Inc.Nov 12, 2002Nov 18, 2002May 13, 20034,417
507618-98DrillMain Energy, Inc.Feb 12, 2002Apr 11, 2001—4,417
507618-99DrillMain Energy, Inc.Apr 10, 2001Apr 11, 2001Apr 24, 20014,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-187423————
—— G-3-187424————
—— G-3-196814————
—— G-3-196816————

Formation tops

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

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE1,300-1,264

Perforations

Perforated and open-hole intervals.

FromToType
1,3281,333Perforated
1,3431,349Perforated
1,4701,476Perforated
1,6641,668Perforated
3,6983,708Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
14142——
9.62597612.25340 S
73,8868.5540 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
00Oct 10, 2003Jul 9, 2003Yes
00Oct 1, 2003——
00Apr 10, 2002Oct 31, 2001Yes
00Mar 12, 2002——

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