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
20170430010238INEWTONK3>APRS,TCPXX*,qAX,CWOP-3:@300102z0000.00N/00000.00E_225/000g004t047r000p000P000h76b10108L000WeatherCatV241B14H166
20170430011310INEWTONK3>APRS,TCPXX*,qAX,CWOP-4:@300113z0000.00N/00000.00E_180/001g004t047r000p000P000h76b10107L000WeatherCatV241B14H166
20170430012342INEWTONK3>APRS,TCPXX*,qAX,CWOP-6:@300123z0000.00N/00000.00E_090/001g004t047r000p000P000h77b10108L000WeatherCatV241B14H166
20170430013409INEWTONK3>APRS,TCPXX*,qAX,CWOP-7:@300134z0000.00N/00000.00E_090/000g003t047r000p000P000h77b10109L000WeatherCatV241B14H166
20170430015418INEWTONK3>APRS,TCPXX*,qAX,CWOP-4:@300154z0000.00N/00000.00E_135/000g001t045r000p000P000h79b10105L000WeatherCatV241B14H166
20170430024508INEWTONK3>APRS,TCPXX*,qAX,CWOP-4:@300245z0000.00N/00000.00E_225/000g000t042r000p000P000h83b10102L000WeatherCatV241B14H166
20170430035414INEWTONK3>APRS,TCPXX*,qAX,CWOP-3:@300354z0000.00N/00000.00E_090/000g003t042r000p000P000h90b10096L000WeatherCatV241B14H166
20170430051442INEWTONK3>APRS,TCPXX*,qAX,CWOP-4:@300514z0000.00N/00000.00E_135/000g003t044r000p000P000h89b10091L042WeatherCatV241B14H166