APRS Packet Errors for WA6MHA-11 (last 24 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
20181209223339WA6MHA-11>APOTW1,W6SCE-10,KF6ILA-10,WIDE2*,qAO,WD6DRI-1:!320.50N/11828.9pV_002/009g012t067P001h36b10243V137OTW1
20181209223339WA6MHA-11>APOTW1,W6SCE-10,KF6ILA-10,WIDE2*,qAR,KF6SJ-10:!320.50N/11828.9pV_002/009g012t067P001h36b10243V137OTW1YJ
20181209225752WA6MHA-11>APOTW1,W6SCE-10,KF6ILA-10,WIDE2*,qAR,WA6IAJ-1:!3410.50N/Q1828.90W_324/002g007t066P001h35b10243V134OTW1
20181210092117WA6MHA-11>APOTW1,N6EX-1,KF6ILA-10,WIDE2*,qAR,N6JCM:!3410.50N/11828. 0W_315/001g002t04P(02h58b10225V126OTW1
20181210102138WA6MHA-11>APOTW1,W6SCE-10,KF6ILA-10,WIDE2*,qAR,KF6SJ-10:!3410.50N/11828.90W_238/0P2g002t046P002h58b10221V126OTW1=
20181210102138WA6MHA-11>APOTW1,W6SCE-10,KF6ILA-10,WIDE2*,qAO,WD6DRI-1:!3410.50N/11828.90W_238/0P2g002t046P002h58b10221V126OTW1