APRS Packet Errors for C4J-3 (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
20200216172901C4J-3>APWW10,TCPT,qAR,N3ENM-10:;PW HOSP 1z3846.0729.23 NOHOS
20200216175702C4J-3>APWW10,TCAWEST,qAR,N3ENM-10:;5 15z872N0704WSoeJckson
20200216191231C4J-3>A0,TCPqAC,TEST,qAR,N3ENM-10:;503R 61912z348N/0.53WdDumfrieiangle VFD