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
20201022011645W3SMD-1>APN383,qAR,KA3OCS-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20201022020532W3SMD-1>APN383,qAR,KA3OCS-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20201022025419W3SMD-1>APN383,qAR,KA3OCS-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20201022025816W3SMD-1>APWW10,TCPIPAC,T2KENZ,qAS,N4JJS-1:)F.W.M/07653WhFtshing 1171ivingsh 20744 3
20201022034307W3SMD-1>APN383,qAR,KA3OCS-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO
20201022042644W3SMD-1>APWW10,TCPIP*,2KOBLNZ,qAR,N4JJS-1:;F_7DIST11111z3815.79N/07645.86Wd21660 tn Po Rd uood 20618 3017693600
20201022052045W3SMD-1>APN383,qAR,KA3OCS-1:;145.390-R111111z3833.72N/07642.54WrT196 R15m W3ZO