APRS Packet Errors for CDS (last 24 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
20180921130409CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922035411CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922051412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922062412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922063412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922064413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922065412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922072412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922073412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922074412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922081412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922084412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922085412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922093413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922094413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922095412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922100412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922101412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922102412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922103412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922104412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922105412CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922110413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922111413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922112413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922113416CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922114413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922121413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922122413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180922123413CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net