APRS Packet Errors for FW0498 (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
20180621031312FW0498>APRS,TCPXX*,qAX,CWOP-5:@210313z3922.74N/10450.100W_203/001g001t062r000P000h57b10238mUtWX
20180621041010FW0498>APRS,TCPXX*,qAX,CWOP-7:@210410z3922.74N/10450.100W_203/000g000t060r000P000h62b10243mUtWX
20180621051211FW0498>APRS,TCPXX*,qAX,CWOP-7:@210512z3922.74N/10450.100W_023/000g000t056r000P000h66b10243mUtWX
20180621051717FW0498>APRS,TCPXX*,qAX,CWOP-3:@210517z3922.74N/10450.100W_023/000g000t056r000P000h67b10243mUtWX
20180621054312FW0498>APRS,TCPXX*,qAX,CWOP-3:@210543z3922.74N/10450.100W_180/000g000t055r000P000h69b10245mUtWX
20180621063452FW0498>APRS,TCPXX*,qAX,CWOP-5:@210634z3922.74N/10450.100W_225/000g000t053r000P000h73b10241mUtWX
20180621065022FW0498>APRS,TCPXX*,qAX,CWOP-5:@210650z3922.74N/10450.100W_203/000g000t053r000P000h74b10241mUtWX
20180621074720FW0498>APRS,TCPXX*,qAX,CWOP-5:@210747z3922.74N/10450.100W_113/000g000t049r000P000h78b10237mUtWX
20180621075737FW0498>APRS,TCPXX*,qAX,CWOP-3:@210757z3922.74N/10450.100W_135/000g000t049r000P000h79b10236mUtWX
20180621081817FW0498>APRS,TCPXX*,qAX,CWOP-4:@210818z3922.74N/10450.100W_158/000g000t049r000P000h82b10233mUtWX
20180621082838FW0498>APRS,TCPXX*,qAX,CWOP-5:@210828z3922.74N/10450.100W_158/000g000t049r000P000h82b10233mUtWX