TEXAS · WELLS · SHELBY COUNTY · HANSON, J.W. LEASE · API 42-419-30866 · DISTRICT 06
Hanson J.W. #6
Shelby County · Joaquin (Travis Peak) field · Temp Abandoned · Vertical
Hanson J.W. #6 (API 42-419-30866) is a well in Shelby County operated by Eqv Operating LLC, completed August 15, 2004 and listed as temp abandoned on the RRC schedule, shut in August 1, 2018.
The RRC has issued one drilling permit, issued July 2, 2003, permitted to 8,680 ft.
It was permitted by Kcs Resources, Inc. and has since transferred to Eqv Operating LLC on the wellbore schedule.
Completion filings report 4 formation tops, including Jeter, James Lime, Sligo, Travis Peak.
Its lease has reported 2.78K barrels of oil and 826K mcf of gas since August 2004, with no volume in the three years through April 2026.
Operator of record
Permitted by KCS Resources, Inc.; the EWA schedule now lists a different operator.
- Based in
- Oklahoma City, OK
- P-5 status
- Active (A)
- P-5 last filed
- Sep 24, 2025
- Phone
- (405) 648-4409
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Eqv Operating LLC |
| Production reports | Eqv Operating LLCthrough Jul 2018 |
| Latest permit | KCS Resources, Inc.Jul 2, 2003 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,680
- total depth, ft
- 1
- permits on file
- Jul 2, 2003
- last permit issued
- Aug 15, 2004
- completed
- 2.78K
- cumulative oil, bbl
- 826K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2004 THROUGH Jul 2018
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Aug 15, 2004
- Shut in
- Aug 1, 2018
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (X)
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 |
|---|---|---|---|---|---|---|
| Hanson, J.W. G-6-206326 | Joaquin (Travis Peak) | Eqv Operating LLC | 1 | 2.78K | 826K | Aug 2004 – Jul 2018 |
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.
- 1KCS Resources, Inc.Aug 2004 → Feb 2009
- 2KCS Resources, LLCMar 2009 → Apr 2010
- 3Classic Operating Co. LLCMay 2010 → Dec 2014
- 4Memorial Production Oper. LLCJan 2017 → May 2017
- 5Amplify Energy Operating LLCJun 2017 → Jul 2018
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 533802-99 | Drill | KCS Resources, Inc. | Jul 2, 2003 | Jul 2, 2003 | Jul 10, 2004 | 8,650 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Aug 15, 2004 | Hanson J.W. G-6-206326 | Joaquin (Travis Peak) | Eqv Operating LLC | Temp Abandoned · shut in Aug 1, 2018 | 8,680 |
Formation tops
As filed on W-2/G-1. Subsea from 224 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Jeter | 4,810 | -4,586 |
| James LimeJAMES LM | 5,304 | -5,080 |
| Sligo | 5,628 | -5,404 |
| Travis Peak | 6,240 | -6,016 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,342 | 8,521 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 850 | 17.5 | 665 S |
| 4.5 | 8,680 | 7.875 | 1,020 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | May 4, 2005 | Dec 7, 2004 | Yes |
| 00 | Feb 23, 2005 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received May 20, 2008. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| Combination: Resistivity/Neutron Density PorosityHIGH RESOLUTION INDUCTION DSN II SPECTRAL DENSITY MICROLOGSpans Jeter, James Lime, Sligo, Travis Peak | TIFF | 4,791 to 8,684 | May 20, 2008run Jul 28, 2004 | — |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-419-30866 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-419-30866 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/41930866, documented in the API reference.