APRS Packet Errors for IRLP-4069 (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
20130520163125W4SNA-13>APUN10,TCPIP*,qAC,T2QUEBEC:;IRLP-4069*201631z3622.65NC08021.86WW53.310MHz- PL100.0: Linked 9210 REF
20130520173127W4SNA-13>APUN10,TCPIP*,qAC,T2QUEBEC:;IRLP-4069*201731z3622.65NC08021.86WW53.310MHz- PL100.0: Linked 9210 REF
20130520183130W4SNA-13>APUN10,TCPIP*,qAC,T2VAN:;IRLP-4069*201831z3622.65NC08021.86WW53.310MHz- PL100.0: Linked 9210 REF
20130520193132W4SNA-13>APUN10,TCPIP*,qAC,T2QUEBEC:;IRLP-4069*201931z3622.65NC08021.86WW53.310MHz- PL100.0: Linked 9210 REF
20130520200100W4SNA-13>APUN10,TCPIP*,qAC,T2QUEBEC:;IRLP-4069*202000z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20130520210100W4SNA-13>APUN10,TCPIP*,qAC,T2SWEDEN2:;IRLP-4069*202100z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE
20130520220102W4SNA-13>APUN10,TCPIP*,qAC,T2LGA:;IRLP-4069*202201z3622.65NI08021.86WW53.310MHz- PL100.0: IDLE