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
20171218070029CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218071028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218073028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218074028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218075028CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218080028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218082028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218083028CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218084028CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218085028CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218090028CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218091028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218092028CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218093030CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218094028CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218095029CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218100028CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218101028CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218102028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218103028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218104028CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218105029CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218110028CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218112029CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218113029CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218114029CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218115029CDS>BEACON,qAO,N5XTR-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218120029CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218121029CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218122029CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218123031CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20171218124030CDS>BEACON,qAR,KD5YCY-5:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net