WELL · 42-603-30215 · DISTRICT 4

State Tract 840-S #3U

N

Matgrda IS-SB County  · Directional

State Tract 840-S #3U (API 42-603-30215) is a permitted well in Matgrda IS-SB County filed by Forest Oil Corp.; no completion report is on file yet.

The RRC has issued 6 drilling permits between 1981 and 2003, permitted to 12,000 ft.

Operator of record

Forest Oil Corp.

Houston, TX · P-5 Y, filed Sep 11, 2015 · 1,861 permits on file · (866) 520-0402

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsForest Oil Corporationthrough Oct 2001
Latest permitForest Oil Corp.Aug 8, 2003
12,000
total depth, ft
6
permits on file
Aug 8, 2003
last permit issued
—
completed
0
cumulative oil, bbl
1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2006

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 840-S G-4-121375Clear, South (Frio 8600)Forest Oil Corporation101KJan 1993 – Jan 2006
State Tract 840-S G-4-174016Clear, S. (Frio 9500)Forest Oil Corporation100Mar 1999 – Jan 2006

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. 1Forest Oil CorporationOct 2001 → Oct 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
534331-99RecompletionForest Oil Corp.Jul 18, 2003Aug 8, 2003—9,380
482655-99RecompletionForcenergy IncFeb 11, 1999Feb 25, 1999Jan 25, 199911,300
300543-99RecompletionCorpus Christi Oil & Gas Co.Mar 21, 1986Apr 1, 1986—11,300
211098-99RecompletionCorpus Christi Oil & Gas Co.Aug 31, 1983Sep 9, 1983—12,000
177756-99DrillCorpus Christi Oil & Gas Co.Nov 18, 1982Nov 18, 1982Jan 5, 198312,000
135998-99DrillCorpus Christi Oil & Gas Co.Oct 8, 1981Oct 8, 1981—12,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-121375————
—— G-4-174016————

Perforations

Perforated and open-hole intervals.

FromToType
8,6308,636Perforated
8,6308,639Perforated
9,4909,495Perforated
9,4909,516Perforated
9,5069,516Perforated
9,5909,642Perforated
9,8569,866Perforated
9,9029,906Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
30115——
30226——
163,129202,500 S
163,429202,500 S
10.757,96814.751,800 S
10.757,96914.751,800 S
2.3759,659——
7.6259,8569.5650 S
7.6259,8579.5650 S
2.8759,870——
2.3759,885——

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 17, 1999Aug 4, 1999—
00Sep 3, 1999——
00Jul 26, 1999May 14, 1999—
00Apr 24, 1987May 12, 1986Yes
00Jun 25, 1986——
00Jan 12, 1984Sep 6, 1983—
00Jan 12, 1984Mar 23, 1983—

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