APRS Packet Errors for M6CNA (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
20170622232004M6CNA>APRS,TCPXX*,qAX,CWOP-4:@222320z0000.00N/00000.00E_000/000g000t055r000p000P000h94b10166eCumulusFO
20170623035003M6CNA>APRS,TCPXX*,qAX,CWOP-5:@230350z0000.00N/00000.00E_000/000g000t055r000p000P000h91b10167eCumulusFO
20170623040003M6CNA>APRS,TCPXX*,qAX,CWOP-3:@230400z0000.00N/00000.00E_000/000g000t055r000p000P000h91b10166eCumulusFO
20170623041004M6CNA>APRS,TCPXX*,qAX,CWOP-3:@230410z0000.00N/00000.00E_000/000g000t055r000p000P000h90b10167eCumulusFO
20170623042003M6CNA>APRS,TCPXX*,qAX,CWOP-1:@230420z0000.00N/00000.00E_000/000g000t056r000p000P000h90b10165eCumulusFO
20170623043003M6CNA>APRS,TCPXX*,qAX,CWOP-3:@230430z0000.00N/00000.00E_000/000g000t056r000p000P000h90b10164eCumulusFO
20170623044003M6CNA>APRS,TCPXX*,qAX,CWOP-4:@230440z0000.00N/00000.00E_000/000g000t056r000p000P000h90b10165eCumulusFO
20170623045003M6CNA>APRS,TCPXX*,qAX,CWOP-5:@230450z0000.00N/00000.00E_000/000g000t056r000p000P000h90b10166eCumulusFO
20170623050003M6CNA>APRS,TCPXX*,qAX,CWOP-1:@230500z0000.00N/00000.00E_000/000g000t056r000p000P000h90b10165eCumulusFO
20170623051003M6CNA>APRS,TCPXX*,qAX,CWOP-1:@230510z0000.00N/00000.00E_000/000g000t056r000p000P000h90b10165eCumulusFO