APRS Packet Errors for mendele (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
20180620112516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620115516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620122517mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620125517mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620132516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620135516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620142516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620145516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620152516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620155516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620162516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM
20180620165516mendele>APZ7,TCPIP*,qAS,RO7T:=4357.56N14540.89E^ aeroport Mendeleevo - UHSM