WELL · 42-125-30756 · DISTRICT 8
Lindsey #1
Dickens County · Vertical
Lindsey #1 (API 42-125-30756) is a plugged well in Dickens County, plugged September 10, 2001, last operated by J & J Trading.
The RRC has issued 2 drilling permits between 2001 and 2002, permitted to 7,400 ft.
Completion filings report one formation top, including T/Croton Lime.
Its lease has reported 7.25K barrels of oil since January 2003, last reporting in February 2012.
Operator of record
Abilene, TX · P-5 Y, filed Jan 7, 2005 · 60 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Henson Exploration, L.P.through Mar 2009 |
| Latest permit | J & J TradingDec 12, 2002 |
- 7,400
- total depth, ft
- 2
- permits on file
- Dec 12, 2002
- last permit issued
- —
- completed
- 7.25K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2003 THROUGH Feb 2012
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Sep 10, 2001
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Lindsey O-11-68546 | Spur, South (Croton Lime) | Henson Exploration, L.P. | 1 | 7.25K | 0 | Jan 2003 – Feb 2012 |
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.
- 1J & J TradingJan 2003 → Dec 2004
- 2Henson Exploration, L.P.Jan 2005 → Mar 2009
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 526196-99 | Reenter | J & J Trading | Dec 9, 2002 | Dec 12, 2002 | Dec 26, 2002 | 4,900 |
| 512339-99 | Drill | Woods Operating Co., Inc. | Aug 7, 2001 | Aug 7, 2001 | Aug 29, 2001 | 7,400 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-11-68546 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 2,225 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| T/Croton Lime | 4,650 | -2,425 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,652 | 4,660 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 353 | 17.5 | 335 S |
| 8.625 | 1,417 | 12.25 | 300 S |
| 4.5 | 4,852 | 7.875 | 225 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Apr 29, 2003 | Feb 12, 2003 | Yes |
| 00 | Apr 9, 2003 | — | — |
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.
- Wellbore filings for 42-125-30756 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-125-30756 → scanned completion filings
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/12530756, documented in the API reference.