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
20260506234504EA1JAY-1>APRS,TCPIP*,qAC,EIGHTH:;LTAC *062345z4007.68N/03259.70E_000/t041h80b10180 Ankara Esenboga Airport: LTAC 062250Z 00000KT CAVOK 05/02 Q1018 NOSIG
20260507010004EA1JAY-1>APRS,TCPIP*,qAC,SECOND:;LTAC *070100z4007.68N/03259.70E_000/t037h86b10190 Ankara Esenboga Airport: LTAC 070020Z 00000KT CAVOK 03/01 Q1019 NOSIG
20260507013005EA1JAY-1>APRS,TCPIP*,qAC,EIGHTH:;LTAC *070130z4007.68N/03259.70E_000/t036h86b10190 Ankara Esenboga Airport: LTAC 070050Z 00000KT CAVOK 02/00 Q1019 NOSIG