WELL · 42-351-30663 · DISTRICT 3

Lindsey #1

Y

Newton County · Lueyville (Hackberry 2) field · Temp Abandoned  · Directional

Lindsey #1 (API 42-351-30663) is a well in Newton County operated by Olipdp II LLC, completed October 1, 1996 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued August 27, 1996, permitted to 8,800 ft.

It was permitted by Tri-C Resources, Inc. and has since transferred to Olipdp II LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Btm Of Massive Frio, Hackberry.

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

Operator of record

Olipdp II LLC

Permitted by Tri-C Resources, Inc.; the EWA schedule now lists a different operator.

Lafayette, LA · P-5 Y, filed Feb 4, 2026 · (936) 298-6840

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOlipdp II LLC
Production reportsPetrodome Operating, LLCthrough Oct 2020
Latest permitTri-C Resources, Inc.Aug 27, 1996

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

8,800
total depth, ft
1
permits on file
Aug 27, 1996
last permit issued
Oct 1, 1996
completed
0
cumulative oil, bbl
2.13M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 1996 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 1, 1996
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Lindsey G-3-162163Lueyville (Hackberry 2)Olipdp II, LLC102.13MOct 1996 – Jul 2026

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. 1Tri-C Resources, Inc.Oct 1996 → Feb 2000
  2. 2CNG Producing CompanyMar 2000 → May 2000
  3. 3Dominion Expl. & Prod., Inc.Jun 2000 → Sep 2000
  4. 4Five-Jab, Inc.May 2018 → Dec 2018
  5. 5Petrodome Operating, LLCJan 2019 → Oct 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
451964-99DrillTri-C Resources, Inc.Aug 27, 1996Aug 27, 1996Sep 7, 19968,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-162163————

Formation tops

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

FormationMD ftSubsea
BTM of Massive Frio7,200-7,171
Hackberry8,150-8,121

Perforations

Perforated and open-hole intervals.

FromToType
8,1988,214Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,28912.251,355 S
4.58,4378.75770 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
00Apr 3, 1997Oct 17, 1996Yes
00Mar 31, 1997——

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