APRS Packet Errors for KJ4NES-3 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20170625132442KJ4NES-3>APTT4,K4UAN-3,WIDE1*,WIDE2-1,qAR,KG4OOZ-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625135438KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625142436KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625155428KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625162425KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625165424KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625172421KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625175418KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625182415KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20170625185412KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi