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
20190115005218CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115023218CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115094220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115105220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115123220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115124220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115131220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115132220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115133220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115134220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115135220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115140220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115141220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115144221CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115145220CDS>BEACON,qAR,W5NGU-7:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115150220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115153220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115160220CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115163221CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115164222CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115165221CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115171221CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115173221CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115174221CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115175221CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115192221CDS>BEACON,qAR,W5NGU-7:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115201221CDS>BEACON,qAR,W5NGU-7:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115203221CDS>BEACON,qAR,W5NGU-7:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20190115223221CDS>BEACON,qAR,W5NGU-7:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net