WELL · 42-245-32135 · DISTRICT 3

Chessher #2

Plugged

Jefferson County · Fannett field  · Vertical

Chessher #2 (API 42-245-32135) is a plugged well in Jefferson County, plugged March 20, 2007, last operated by Ecoserv Environmental Svcs LLC.

The RRC has issued one drilling permit, issued July 29, 1996, permitted to 2,250 ft.

It was permitted by Newpark Environmental Services and has since transferred to Ecoserv Environmental Svcs LLC on the wellbore schedule.

Completion filings report one formation top, including Caprock.

Operator of record

Ecoserv Environmental Svcs LLC

Permitted by Newpark Environmental Services; the EWA schedule now lists a different operator.

Abbeville, LA · P-5 Y, filed Nov 4, 2025 · 3 permits on file · (337) 898-2104

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEcoserv Environmental Svcs LLC
Production reportsnone
Latest permitNewpark Environmental ServicesJul 29, 1996

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

2,250
total depth, ft
1
permits on file
Jul 29, 1996
last permit issued
Aug 29, 1996
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 1995 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 29, 1996
Shut in
—
Plugged
Mar 20, 2007

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; they carry 18 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Chessher O-3-22868FannettEcoserv Environmental Svcs, LLC1800Aug 1995 – Jul 2026

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
450913-99DrillNewpark Environmental ServicesJul 29, 1996Jul 29, 1996Aug 9, 19962,250

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-22868————

Formation tops

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

FormationMD ftSubsea
Caprock1,364-1,361

Perforations

Perforated and open-hole intervals.

FromToType
1,6701,988Open hole
1,9001,910Perforated
1,9201,930Perforated
1,9571,967Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,23017.51,585 S
9.6251,67012.25265 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
00Nov 13, 1996Sep 12, 1996—
00Oct 17, 1996——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
2.71M
bbl, all reported
Dec 2006
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000084544W-14 DisposalPlugged Apr 11, 200715,0005001,605–2,250

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 296,126(-100%)

050K100K20052006

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