APRS Packet Errors for SP3YEE (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
20180522122149SP3YEE>APWW10,qAR,SP3WBX:;SP3VSS *221221z522
20180522133618SP3YEE>APWW10,qAR,SP3WBX:;438.700-P*221336z5240SR3XX FM-Link
20180522142951SP3YEE>APWW10,qAR,SP3WBX:;SP3YEE-1 *221429z5232.70N/01657
20180522144952SP3YEE>APWW10,qAR,SP3WBX:;SP3YEE-1 *221449z5232
20180522150649SP3YEE>APWW10,qAR,SP3WBX:;SP3VSS *221506z522
20180522152948SP3YEE>APWW10,qAR,SP3WBX:;SP3YEE-1 *221529z5232.70N/0165wt/pi dusk till dawn
20180522153950SP3YEE>APWW10,qAR,SP3WBX:;SP3YEE-1 *221539z5232.70N/01657