APRS Packet Errors for EA5AWB (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
20190918153242EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@181732z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918160236EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@181802z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918163318EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@181833z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918170346EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@181903z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918173313EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@181933z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918180322EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@182003z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918183315EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@182033z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918190404EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@182104z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918193408EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@182134z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1
20190918200347EA5AWB>APRS,TCPIP*,qAS,BM2142POS:@182203z4143.100N/05023.99WrMMDVM Unknown 224.9400/222.3400 CC1