APRS Packet Errors for IWELTON4 (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
20190425045458IWELTON4>APRS,TCPXX*,qAX,CWOP-3:@250454z0000.00N/00000.00E_180/000g000t049r000p000P000h87b09925L000WeatherCatV304B91H166
20190425050436IWELTON4>APRS,TCPXX*,qAX,CWOP-7:@250504z0000.00N/00000.00E_045/001g001t049r000p000P000h87b09922L006WeatherCatV304B91H166
20190425051441IWELTON4>APRS,TCPXX*,qAX,CWOP-3:@250514z0000.00N/00000.00E_067/000g000t049r000p000P000h86b09922L013WeatherCatV304B91H166
20190425052448IWELTON4>APRS,TCPXX*,qAX,CWOP-2:@250524z0000.00N/00000.00E_045/000g001t049r000p000P000h87b09922L035WeatherCatV304B91H166
20190425053444IWELTON4>APRS,TCPXX*,qAX,CWOP-3:@250534z0000.00N/00000.00E_135/000g003t049r000p000P000h87b09922L050WeatherCatV304B91H166
20190425054510IWELTON4>APRS,TCPXX*,qAX,CWOP-2:@250545z0000.00N/00000.00E_135/000g003t050r000p000P000h87b09922L042WeatherCatV304B91H166
20190425055516IWELTON4>APRS,TCPXX*,qAX,CWOP-5:@250555z0000.00N/00000.00E_000/001g003t050r000p000P000h87b09922L078WeatherCatV304B91H166
20190425060521IWELTON4>APRS,TCPXX*,qAX,CWOP-5:@250605z0000.00N/00000.00E_090/000g003t050r000p000P000h86b09922L105WeatherCatV304B91H166
20190425061542IWELTON4>APRS,TCPXX*,qAX,CWOP-2:@250615z0000.00N/00000.00E_180/000g003t051r000p000P000h85b09922L073WeatherCatV304B91H166