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
20260425010004EA1JAY-1>APRS,TCPIP*,qAC,FOURTH:;LTAC *250100z4007.68N/03259.70E_000/t037h80b10160 Ankara Esenboga Airport: LTAC 250020Z 00000KT CAVOK 03/00 Q1016 NOSIG
20260425040004EA1JAY-1>APRS,TCPIP*,qAC,FIFTH:;LTAC *250400z4007.68N/03259.70E_000/t034h93b10170 Ankara Esenboga Airport: LTAC 250320Z 00000KT CAVOK 01/M00 Q1017 NOSIG
20260425041504EA1JAY-1>APRS,TCPIP*,qAC,NINTH:;LTAC *250415z4007.68N/03259.70E_000/t034h93b10170 Ankara Esenboga Airport: LTAC 250320Z 00000KT CAVOK 01/M00 Q1017 NOSIG