APRS Packet Errors for WB4GMB (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
20170323154625WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231546z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323155125WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231551z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323155625WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231556z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323160125WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231601z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323160625WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231606z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323161125WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231611z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323161625WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231616z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323162125WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231621z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323162625WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231626z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400
20170323163125WB4GMB>APRS,TCPIP*,qAC,FIFTH:@231631z3326.57N/08444.21W_113/NaNg000t060r000p003P000h49b10299 VISR3748 400