APRS Packet Errors for EW66880 (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
20170322164916EW66880>APRS,TCPXX*,qAX,CWOP-3:@221649z0000.00N/00000.00E_049/014g018t063P000h42b10202ws31
20170322174852EW66880>APRS,TCPXX*,qAX,CWOP-6:@221748z0000.00N/00000.00E_060/006g016t063P000h35b10206ws31
20170322184918EW66880>APRS,TCPXX*,qAX,CWOP-4:@221849z0000.00N/00000.00E_342/004g013t063P000h35b10207ws31
20170322194911EW66880>APRS,TCPXX*,qAX,CWOP-5:@221949z0000.00N/00000.00E_047/006g013t062P000h26b10213ws31
20170322204908EW66880>APRS,TCPXX*,qAX,CWOP-4:@222049z0000.00N/00000.00E_031/005g008t062P000h28b10214ws31
20170322214915EW66880>APRS,TCPXX*,qAX,CWOP-4:@222149z0000.00N/00000.00E_017/001g007t061P000h26b10216ws31