APRS Packet Errors for LTAC (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
20261020230004	EA1JAY-1>APRS,TCPIP,qAC,THIRD:;LTAC 202300z4007.68N/03259.70E_000/t039h93b10270 Ankara Esenboga Airport: LTAC 202220Z 00000KT CAVOK 04/03 Q1027 NOSIG
20261020231504	EA1JAY-1>APRS,TCPIP,qAC,SIXTH:;LTAC 202315z4007.68N/03259.70E_000/t039h93b10270 Ankara Esenboga Airport: LTAC 202220Z 00000KT CAVOK 04/03 Q1027 NOSIG
20261021013003	EA1JAY-1>APRS,TCPIP,qAC,THIRD:;LTAC 210130z4007.68N/03259.70E_000/t039h86b10270 Ankara Esenboga Airport: LTAC 210050Z 00000KT CAVOK 04/02 Q1027 NOSIG
20261021020004	EA1JAY-1>APRS,TCPIP,qAC,FOURTH:;LTAC 210200z4007.68N/03259.70E_000/t037h93b10270 Ankara Esenboga Airport: LTAC 210120Z 00000KT CAVOK 03/02 Q1027 NOSIG