APRS Packet Errors for KD5WCQ (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
20190615214226KD5WCQ>APRS,TCPXX*,qAX,CWOP-2:@152142z0000.00N/00000.00E_269/009g000t089P152h08b08560ws20
20190615215225KD5WCQ>APRS,TCPXX*,qAX,CWOP-4:@152152z0000.00N/00000.00E_291/007g000t090P152h08b08567ws20
20190615220226KD5WCQ>APRS,TCPXX*,qAX,CWOP-3:@152202z0000.00N/00000.00E_269/006g000t090P152h08b08563ws20
20190615221226KD5WCQ>APRS,TCPXX*,qAX,CWOP-6:@152212z0000.00N/00000.00E_269/009g000t090P152h08b08563ws20
20190615222226KD5WCQ>APRS,TCPXX*,qAX,CWOP-6:@152222z0000.00N/00000.00E_291/013g000t091P152h08b08563ws20
20190615223226KD5WCQ>APRS,TCPXX*,qAX,CWOP-6:@152232z0000.00N/00000.00E_224/008g000t090P152h08b08556ws20
20190615224226KD5WCQ>APRS,TCPXX*,qAX,CWOP-3:@152242z0000.00N/00000.00E_269/005g000t091P152h08b08556ws20
20190615225226KD5WCQ>APRS,TCPXX*,qAX,CWOP-2:@152252z0000.00N/00000.00E_269/013g000t091P152h08b08556ws20
20190615230226KD5WCQ>APRS,TCPXX*,qAX,CWOP-3:@152302z0000.00N/00000.00E_269/006g000t090P152h08b08556ws20
20190615231225KD5WCQ>APRS,TCPXX*,qAX,CWOP-7:@152312z0000.00N/00000.00E_269/003g000t091P152h08b08556ws20