APRS Packet Errors for kb8tuy (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
20171020045629kb8tuy>APRS,TCPIP*,qAC,CWOP-3:@200450z0000.00N/00000.00E_000/000g000t053r000p000P000h88b10116eCumulusFO
20171020055937kb8tuy>APRS,TCPIP*,qAC,CWOP-2:@200553z0000.00N/00000.00E_000/000g000t050r000p000P000h90b10117eCumulusFO
20171020070231kb8tuy>APRS,TCPIP*,qAC,CWOP-3:@200656z0000.00N/00000.00E_000/000g000t048r000p000P000h94b10119eCumulusFO
20171020072030kb8tuy>APRS,TCPIP*,qAC,CWOP-7:@200714z0000.00N/00000.00E_000/000g000t048r000p000P000h94b10119eCumulusFO
20171020091731kb8tuy>APRS,TCPIP*,qAC,CWOP-2:@200911z0000.00N/00000.00E_000/000g000t046r000p000P000h95b10126eCumulusFO
20171020100237kb8tuy>APRS,TCPIP*,qAC,CWOP-4:@200956z0000.00N/00000.00E_000/000g000t044r000p000P000h96b10132eCumulusFO
20171020102029kb8tuy>APRS,TCPIP*,qAC,CWOP-2:@201014z0000.00N/00000.00E_000/000g000t044r000p000P000h96b10134eCumulusFO
20171020102934kb8tuy>APRS,TCPIP*,qAC,CWOP-4:@201023z0000.00N/00000.00E_000/000g000t044r000p000P000h96b10134eCumulusFO
20171020104735kb8tuy>APRS,TCPIP*,qAC,CWOP-7:@201041z0000.00N/00000.00E_000/000g000t044r000p000P000h97b10136eCumulusFO