APRS Packet Errors for W3SMD-1 (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
20190220075018W3SMD-1>APN383,qAR,NO3B-10:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20190220083905W3SMD-1>APN383,qAS,K3GJ-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20190220092753W3SMD-1>APN383,qAR,W4KEL-12:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20190220095246W3SMD-1>APN383,qAR,W4KEL-12:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20190220104129W3SMD-1>APN383,qAR,W4KEL-12:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20190220113017W3SMD-1>APN383,qAR,KK4ZWW-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20190220121906W3SMD-1>APN383,qAS,K3GJ-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20190220130753W3SMD-1>APN383,qAS,K3GJ-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO