APRS Packet Errors for W4TIY-4 (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
20170720190613W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170720200613W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170720203613W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170720210614W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170720213614W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170720223615W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170720230613W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170720233613W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170721000613W4TIY-4>BEACON,qAR,W4GVX-10:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh
20170721003613W4TIY-4>BEACON,qAR,N4NE-2:;146.895+*111111z3350.70N/8457.42WrT077 R45m Mg2ndTh