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
20181017110730KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N9CVA-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017111459KJ4NES-3>APTT4,K4UAN-3,WIDE1*,WIDE2-1,qAR,KK4ZDZ-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017113728KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017114220KJ4NES-3>APTT4,K4UAN-3,WIDE1*,WIDE2-1,qAR,KK4ZDZ-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017120738KJ4NES-3>APTT4,K4UAN-3,WIDE1*,WIDE2-1,qAR,N4UUJ-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017121241KJ4NES-3>APTT4,K4UAN-3,WIDE1,KA4MAP-3,WIDE2*,qAR,KK4ZDZ-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017123732KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017133726KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAO,N9CVA-10:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017140733KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,KJ4NES-4:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017143732KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017150727KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017153725KJ4NES-3>APTT4,K4UAN-3,WIDE1*,WIDE2-1,qAR,N5AAA-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi
20181017163718KJ4NES-3>APTT4,WIDE1-1,WIDE2-1,qAR,W1ARN-1:/BG, KY, 35W 357ft HAAT, 8dBi Yagi