APRS Packet Errors for LEMD (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
20260517060003	EA1JAY-1>APRS,TCPIP,qAC,THIRD:;LEMD 170600z4029.38N/00333.83W_000/t045h87b10150 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 170500Z 00000KT 9999 SCT078 07/05 Q1015 NOSIG
20260517061505	EA1JAY-1>APRS,TCPIP,qAC,SIXTH:;LEMD 170615z4029.38N/00333.83W_000/t046h81b10160 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 170530Z 00000KT 9999 SCT070 08/05 Q1016 NOSIG
20260517063014	EA1JAY-1>APRS,TCPIP,qAC,FIRST:;LEMD 170630z4029.38N/00333.83W_000/t046h81b10160 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 170530Z 00000KT 9999 SCT070 08/05 Q1016 NOSIG