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
20171020012528CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020013528CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020014528CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020015528CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020020528CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020021528CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020022529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020023529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020024529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020025529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020030529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020032528CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020033529CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020034529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020040529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020041529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020042529CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020043529CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020044529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020045529CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020050529CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020051529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020052529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020053529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020055529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020060529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020061529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020062529CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020063529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020064530CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020065529CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171020070529CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net