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
20250917001503	EA1JAY-1>APRS,TCPIP,qAC,THIRD:;LEMD 170015z4029.38N/00333.83W_000/t072h28b10230 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 162330Z 00000KT CAVOK 22/03 Q1023 NOSIG
20250917003004	EA1JAY-1>APRS,TCPIP,qAC,SIXTH:;LEMD 170030z4029.38N/00333.83W_000/t072h28b10230 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 162330Z 00000KT CAVOK 22/03 Q1023 NOSIG
20250917014502	EA1JAY-1>APRS,TCPIP,qAC,THIRD:;LEMD 170145z4029.38N/00333.83W_000/t066h37b10230 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 170100Z 00000KT CAVOK 19/04 Q1023 NOSIG
20250917020003	EA1JAY-1>APRS,TCPIP,qAC,FIRST:;LEMD 170200z4029.38N/00333.83W_000/t066h37b10230 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 170100Z 00000KT CAVOK 19/04 Q1023 NOSIG