APRS Packet Errors for CDS (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
20171021100533CDS>BEACON,qAR,KD5GJE-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021101533CDS>BEACON,qAR,KD5GJE-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021102533CDS>BEACON,qAR,N5PSP-2:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021103533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021104533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021105533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021110533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021111534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021112533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021113534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021115533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021120533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021121534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021122533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021123534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021125533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021130534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021131534CDS>BEACON,qAR,NN5DX-9:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021132534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021133533CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021134534CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021135534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021141534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021142534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021143534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021145535CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021150534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021151534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021152534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021153534CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171021155534CDS>BEACON,qAR,NN5DX-9:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net