WELL · 42-603-30203 · DISTRICT 4

State Tract 818-S #1

N

Matgrda IS-SB County  · Vertical

State Tract 818-S #1 (API 42-603-30203) is a permitted well in Matgrda IS-SB County filed by PG&E Resources Offshore Company; no completion report is on file yet.

The RRC has issued 4 drilling permits between 1982 and 1993, permitted to 8,000 ft.

Its 2 leases have reported 82.2K barrels of oil and 34.3K mcf of gas since January 1993, last reporting in March 2008. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Pg&e Resources Offshore Company

Dallas, TX · P-5 Y, filed Oct 10, 1994 · 13 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsEnserch Exploration, Incthrough Nov 1996
Latest permitPg&e Resources Offshore CompanyMar 23, 1993
8,000
total depth, ft
4
permits on file
Mar 23, 1993
last permit issued
—
completed
82.2K
cumulative oil, bbl
34.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2008

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
State Tract 818-S O-4-12186Clear, N. (Miocene 6270)Forest Oil Corporation182.2K25.1KMar 1993 – Mar 2008
State Tract 818-S G-4-131202Clear, N. (Miocene 6830)Pg&e Resources Offshore Company109.28KJan 1993 – Jul 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. 1Pg&e Resources Offshore CompanyJan 1993 → Oct 1994
  2. 2Dalen Resources Oil & Gas Co.Nov 1994 → Dec 1995
  3. 3Enserch Exploration, IncJan 1996 → Nov 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
410083-99RecompletionPg&e Resources Offshore CompanyMar 22, 1993Mar 23, 1993Mar 9, 19937,175
360256-99RecompletionCorpus Christi Oil & Gas Co.Jun 9, 1989Jun 9, 1989—8,000
304397-99RecompletionCorpus Christi Oil & Gas Co.Jul 21, 1986Jul 22, 1986—8,000
165183-99DrillCorpus Christi Oil & Gas Co.Jun 30, 1982Jun 30, 1982Sep 1, 19828,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-131202————
—— O-4-12186————

Perforations

Perforated and open-hole intervals.

FromToType
6,2706,276Perforated
6,8366,838Perforated
6,8847,153Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
30211——
10.752,12214.751,400 S
2.8756,863——
2.3756,863——
2.8757,001——
2.3757,001——
7.6257,1759.875500 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
00May 25, 1993Apr 8, 1993Yes
00Apr 29, 1993——
00Aug 28, 1989Jun 14, 1989Yes
00Jul 22, 1989——
00Jan 12, 1984Oct 28, 1982—

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