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
20190216075143K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@160751z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216082214K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@160822z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216085340K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@160853z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216090337K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@160903z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216093549K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@160935z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216111329K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@161113z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216114353K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@161143z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216121522K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@161215z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1
20190216124548K4HA>APBM1S,TCPIP*,qAS,N3FE-15:@161245z354200.00N/754200.00E-MMDVM MMDVM HS Hat 446.0750/446.0750 CC1