APRS Packet Errors for KD4CCO-2 (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
20180425121325KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/280930z/;z-M9by,_ sT257/000g004t054r000P000p000h85b10140
20180425122325KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/281223z/;z-M9by,_ sT138/000g000t054r000P000p000h85b10140
20180425123355KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/281233z/;z-M9by,_ sT216/000g000t054r000P000p000h85b10150
20180425124355KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/281243z/;z-M9by,_ sT195/000g000t054r000P000p000h85b10150
20180425125355KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/281253z/;z-M9by,_ sT196/000g000t054r000P000p000h85b10150
20180425130355KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/281303z/;z-M9by,_ sT237/003g003t054r000P000p000h85b10150
20180425131355KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/281313z/;z-M9by,_ sT250/000g003t054r000P000p000h85b10150
20180425132355KD4CCO-2>APWW10,WIDE1-1,WIDE2-1,qAS,KD4CCO:/281323z/;z-M9by,_ sT215/000g000t054r000P000p000h85b10150