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
20241128053003EA1JAY-1>APRS,TCPIP*,qAC,THIRD:;LTAC *280530z4007.68N/03259.70E_000/t034h80b10250 Ankara Esenboga Airport: LTAC 280420Z 00000KT 9999 BKN016 01/M02 Q1025 NOSIG
20241128071502EA1JAY-1>APRS,TCPIP*,qAC,THIRD:;LTAC *280715z4007.68N/03259.70E_000/t036h74b10260 Ankara Esenboga Airport: LTAC 280620Z 00000KT 7000 BKN015 02/M02 Q1026 NOSIG
20241128073002EA1JAY-1>APRS,TCPIP*,qAC,THIRD:;LTAC *280730z4007.68N/03259.70E_000/t036h74b10260 Ankara Esenboga Airport: LTAC 280620Z 00000KT 7000 BKN015 02/M02 Q1026 NOSIG