APRS Packet Errors for dw6699 (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
20170622231522dw6699>APRS,TCPXX*,qAX,CWOP-5:@222315z3239.86N/09810.100W_142/003g000t093P000h49b09934ws31
20170622232533dw6699>APRS,TCPXX*,qAX,CWOP-5:@222325z3239.86N/09810.100W_140/001g000t093P000h49b09934ws31
20170623043537dw6699>APRS,TCPXX*,qAX,CWOP-3:@230435z3239.86N/09810.100W_141/001g000t080P000h74b09957ws31
20170623044528dw6699>APRS,TCPXX*,qAX,CWOP-3:@230445z3239.86N/09810.100W_141/000g000t080P000h75b09960ws31
20170623045532dw6699>APRS,TCPXX*,qAX,CWOP-3:@230455z3239.86N/09810.100W_141/000g000t080P000h75b09963ws31
20170623050528dw6699>APRS,TCPXX*,qAX,CWOP-3:@230505z3239.86N/09810.100W_141/000g000t080P000h76b09964ws31