APRS Packet Errors for W0AZR-2 (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
20180922092034W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,N0QVC-1:!4346.9400N/09303.15W#PHG5400
20180922093535W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,KD0TGF-1:!4346.9400N/09303.15W#PHG5400
20180922095035W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,N0QVC-1:!4346.9400N/09303.15W#PHG5400
20180922095040W0AZR-2>APTT4,N0QVC-1,WIDE1,N0AGI-1,WIDE2*,qAR,N0TOR-10:!4346.9400N/09303.15W#PHG5400Y
20180922103538W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,KD0TGF-1:!4346.9400N/09303.15W#PHG5400
20180922110538W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,N0QVC-1:!4346.9400N/09303.15W#PHG5400
20180922112042W0AZR-2>APTT4,W0MXW-3,WIDE1*,WIDE2-1,qAR,N0QVC-1:!4346.9400N/09303.15W#PHG5400
20180922115040W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,KD0TGF-1:!4346.9400N/09303.15W#PHG5400
20180922122041W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,N0QVC-1:!4346.9400N/09303.15W#PHG5400
20180922135047W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,KD0TGF-1:!4346.9400N/09303.15W#PHG5400
20180922140548W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,KD0TGF-1:!4346.9400N/09303.15W#PHG5400
20180922140736W0AZR-2>APTT4,W0MXW-3,WIDE1,N0AGI-1,WIDE2*,qAR,KC0FXY-2:!4346.9400N/09303.15W#PHG5400
20180922142050W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,KD0TGF-1:!4346.9400N/09303.15W#PHG5400
20180922150552W0AZR-2>APTT4,WIDE1-1,WIDE2-1,qAR,KD0TGF-1:!4346.9400N/09303.15W#PHG5400