WELL · 42-367-32696 · DISTRICT 7

Lynch W. L. #1

Y

Parker County · Dicey (Conglomerate) field · Producing  · Vertical

Lynch W. L. #1 (API 42-367-32696) is a well in Parker County operated by Case Resources LLC, completed May 26, 1984 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 15, 1984, permitted to 5,800 ft.

It was permitted by Taylor, Ben J. and has since transferred to Case Resources LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Carr Sand, M. Caddo, Bend.

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

Operator of record

Case Resources LLC

Permitted by Taylor, Ben J.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed Sep 4, 2025 · (940) 567-1145

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCase Resources LLC
Production reportsCase Resources, LLCthrough Apr 2026
Latest permitTaylor, Ben J.Mar 15, 1984

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

5,800
total depth, ft
1
permits on file
Mar 15, 1984
last permit issued
May 26, 1984
completed
0
cumulative oil, bbl
344K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 26, 1984
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Lynch, W. L. G-8-110978Dicey (Conglomerate)Case Resources, LLC10344KJan 1993 – Jul 2026

Gas, mcf lease total

Last 12 months 6,955 · prior 12 24,447(-72%)

01K2K3K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Taylor, Ben J. Inc.Jan 1993 → Oct 2003
  2. 2Encana Oil & Gas(usa) Inc.Nov 2003 → Mar 2009
  3. 3Arrowhead Productions, LPApr 2009 → Oct 2020
  4. 4Case Resources, LLCMar 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
232496-99DrillTaylor, Ben J.Mar 14, 1984Mar 15, 1984—5,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-110978————

Formation tops

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

FormationMD ftSubsea
Carr Sand2,910-1,925
M. Caddo3,290-2,305
BendTOP OF BEND5,130-4,145

Perforations

Perforated and open-hole intervals.

FromToType
5,1685,177Perforated
5,5285,536Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62553712.25355 sx
4.55,7637.875190 sx
4.5—7.875200 sx

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
00Jun 29, 1984Jun 12, 1984—
00Jun 26, 1984Jun 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/36732696, documented in the API reference.