APRS Packet Errors for CQ0PAL-3 (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
20180925133925CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925140930CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925143925CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925150925CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925155425CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925162425CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925165425CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925173924CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925175426CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925183924CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925185424CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL
20180925190924CQ0PAL-3>BEACON,qAO,CQ0POD-3:;APRS MURTINHAIS IM58JL