APRS Packet Errors for CTFD (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
20260208131658	K9WCR-10>APWW11,TCPIP,qAC,T2CAEAST:;CTFD 081316z4100.02N/08544.58WdCHESTER TWP FIRE
20260208141658	K9WCR-10>APWW11,TCPIP,qAC,T2CAEAST:;CTFD 081416z4100.02N/08544.58WdCHESTER TWP FIRE
20260208151658	K9WCR-10>APWW11,TCPIP,qAC,T2CAEAST:;CTFD 081516z4100.02N/08544.58WdCHESTER TWP FIRE
20260208161658	K9WCR-10>APWW11,TCPIP,qAC,T2CAEAST:;CTFD 081616z4100.02N/08544.58WdCHESTER TWP FIRE
20260208171659	K9WCR-10>APWW11,TCPIP,qAC,T2CAEAST:;CTFD 081716z4100.02N/08544.58WdCHESTER TWP FIRE
20260208181659	K9WCR-10>APWW11,TCPIP,qAC,T2CAEAST:;CTFD 081816z4100.02N/08544.58WdCHESTER TWP FIRE