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
20180717035718FW0498>APRS,TCPXX*,qAX,CWOP-3:@170357z3922.74N/10450.100W_023/000g000t063r000P007h87b10247mUtWX
20180717044348FW0498>APRS,TCPXX*,qAX,CWOP-7:@170443z3922.74N/10450.100W_203/000g000t064r000P007h86b10247mUtWX
20180717062713FW0498>APRS,TCPXX*,qAX,CWOP-5:@170627z3922.74N/10450.100W_045/000g000t063r000P000h85b10233mUtWX
20180717063738FW0498>APRS,TCPXX*,qAX,CWOP-5:@170637z3922.74N/10450.100W_158/000g000t062r000P000h86b10234mUtWX
20180717064248FW0498>APRS,TCPXX*,qAX,CWOP-7:@170642z3922.74N/10450.100W_225/001g001t064r000P000h80b10234mUtWX
20180717075511FW0498>APRS,TCPXX*,qAX,CWOP-4:@170755z3922.74N/10450.100W_045/000g000t061r000P000h80b10239mUtWX
20180717084708FW0498>APRS,TCPXX*,qAX,CWOP-3:@170847z3922.74N/10450.100W_293/002g002t063r000P000h80b10248mUtWX