APRS Packet Errors for LTAC (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
20251014061508	EA1JAY-1>APRS,TCPIP,qAC,FIFTH:;LTAC 140615z4007.68N/03259.70E_000/t043h75b10210 Ankara Esenboga Airport: LTAC 140520Z 00000KT CAVOK 06/02 Q1021 NOSIG
20251014063003	EA1JAY-1>APRS,TCPIP,qAC,SECOND:;LTAC 140630z4007.68N/03259.70E_000/t043h75b10210 Ankara Esenboga Airport: LTAC 140520Z 00000KT CAVOK 06/02 Q1021 NOSIG
20251014074503	EA1JAY-1>APRS,TCPIP,qAC,FIFTH:;LTAC 140745z4007.68N/03259.70E_000/t048h66b10210 Ankara Esenboga Airport: LTAC 140650Z 00000KT 9999 FEW040 SCT100 09/03 Q1021 NOSIG
20251014080003	EA1JAY-1>APRS,TCPIP,qAC,THIRD:;LTAC 140800z4007.68N/03259.70E_000/t048h66b10210 Ankara Esenboga Airport: LTAC 140650Z 00000KT 9999 FEW040 SCT100 09/03 Q1021 NOSIG