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
20260219184503EA1JAY-1>APRS,TCPIP*,qAC,NINTH:;LTAC *191845z4007.68N/03259.70E_000/t034h64b10220 Ankara Esenboga Airport: LTAC 191750Z 00000KT CAVOK 01/M05 Q1022 NOSIG
20260220000004EA1JAY-1>APRS,TCPIP*,qAC,FOURTH:;LTAC *200000z4007.68N/03259.70E_000/t027h92b10230 Ankara Esenboga Airport: LTAC 192320Z 00000KT CAVOK M03/M04 Q1023 NOSIG
20260220001503EA1JAY-1>APRS,TCPIP*,qAC,FIRST:;LTAC *200015z4007.68N/03259.70E_000/t027h92b10230 Ankara Esenboga Airport: LTAC 192320Z 00000KT CAVOK M03/M04 Q1023 NOSIG
20260220010004EA1JAY-1>APRS,TCPIP*,qAC,SECOND:;LTAC *200100z4007.68N/03259.70E_000/t027h92b10230 Ankara Esenboga Airport: LTAC 200020Z 00000KT CAVOK M03/M04 Q1023 NOSIG
20260220011503EA1JAY-1>APRS,TCPIP*,qAC,SEVENTH:;LTAC *200115z4007.68N/03259.70E_000/t027h92b10230 Ankara Esenboga Airport: LTAC 200020Z 00000KT CAVOK M03/M04 Q1023 NOSIG
20260220053003EA1JAY-1>APRS,TCPIP*,qAC,FIRST:;LTAC *200530z4007.68N/03259.70E_000/t025h92b10240 Ankara Esenboga Airport: LTAC 200450Z 00000KT CAVOK M04/M05 Q1024 NOSIG
20260220054503EA1JAY-1>APRS,TCPIP*,qAC,FIRST:;LTAC *200545z4007.68N/03259.70E_000/t025h92b10240 Ankara Esenboga Airport: LTAC 200450Z 00000KT CAVOK M04/M05 Q1024 NOSIG