APRS Packet Errors for AC4FL (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
20170920123330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201233z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920124830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201248z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920130330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201303z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920131830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201318z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920133330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201333z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920134830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201348z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920140330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201403z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920141830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201418z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920143330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201433z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920144830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201448z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920150330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201503z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920151830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201518z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920153330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201533z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920154830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201548z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920160330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201603z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920161830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201618z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920163330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201633z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920164830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201648z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920170330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201703z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920171830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201718z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920173330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201733z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920174830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201748z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920180330AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201803z2616.63N/-8149.20ErDVRPTR V2 N NAPLES
20170920181830AC4FL>APZCCS,TCPIP*,qAU,CCS002:;AC4FL-B *201818z2616.63N/-8149.20ErDVRPTR V2 N NAPLES