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
20170324004921EW66880>APRS,TCPXX*,qAX,CWOP-1:@240049z0000.00N/00000.00E_356/000g000t050P000h42b10306ws31
20170324014913EW66880>APRS,TCPXX*,qAX,CWOP-5:@240149z0000.00N/00000.00E_349/000g000t046P000h49b10310ws31
20170324024928EW66880>APRS,TCPXX*,qAX,CWOP-5:@240249z0000.00N/00000.00E_349/000g000t044P000h55b10317ws31
20170324034920EW66880>APRS,TCPXX*,qAX,CWOP-6:@240349z0000.00N/00000.00E_356/000g000t044P000h61b10316ws31
20170324044915EW66880>APRS,TCPXX*,qAX,CWOP-4:@240449z0000.00N/00000.00E_297/000g001t044P000h62b10315ws31
20170324054905EW66880>APRS,TCPXX*,qAX,CWOP-2:@240549z0000.00N/00000.00E_284/000g002t044P000h67b10316ws31