APRS Packet Errors for K4HA (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
20190421161044K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@211610z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421165025K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@211650z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421172259K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@211722z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421182346K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@211823z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421192412K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@211924z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421200846K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@212008z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421202752K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@212027z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421210941K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@212109z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421212850K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@212128z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190421215720K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@212157z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1