APRS Packet Errors for INEWTONK3 (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
20170922115855INEWTONK3>APRS,TCPXX*,qAX,CWOP-6:@221157z0000.00N/00000.00E_180/003g008t066r000p000P000h51b10190WeatherCatV241B14H166
20170922120804INEWTONK3>APRS,TCPXX*,qAX,CWOP-1:@221207z0000.00N/00000.00E_180/003g009t066r000p000P000h49b10190WeatherCatV241B14H166
20170922133728INEWTONK3>APRS,TCPXX*,qAX,CWOP-4:@221337z0000.00N/00000.00E_135/005g008t065r000p000P000h52b10187WeatherCatV241B14H166
20170922144648INEWTONK3>APRS,TCPXX*,qAX,CWOP-5:@221446z0000.00N/00000.00E_315/000g005t061r000p000P000h61b10186WeatherCatV241B14H166