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
20241222054503EA1JAY-1>APRS,TCPIP*,qAC,THIRD:;LEMD *220545z4029.38N/00333.83W_000/t028h92b10310 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 220500Z 00000KT CAVOK M02/M03 Q1031 NOSIG
20241222060003EA1JAY-1>APRS,TCPIP*,qAC,FOURTH:;LEMD *220600z4029.38N/00333.83W_000/t028h92b10310 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 220500Z 00000KT CAVOK M02/M03 Q1031 NOSIG
20241222094503EA1JAY-1>APRS,TCPIP*,qAC,NINTH:;LEMD *220945z4029.38N/00333.83W_000/t032h92b10320 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 220900Z 00000KT CAVOK M00/M01 Q1032 NOSIG
20241222100003EA1JAY-1>APRS,TCPIP*,qAC,FOURTH:;LEMD *221000z4029.38N/00333.83W_000/t032h92b10320 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 220900Z 00000KT CAVOK M00/M01 Q1032 NOSIG
20241222101502EA1JAY-1>APRS,TCPIP*,qAC,FIRST:;LEMD *221015z4029.38N/00333.83W_000/t037h86b10320 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 220930Z 00000KT CAVOK 03/01 Q1032 NOSIG
20241222103003EA1JAY-1>APRS,TCPIP*,qAC,FIRST:;LEMD *221030z4029.38N/00333.83W_000/t037h86b10320 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 220930Z 00000KT CAVOK 03/01 Q1032 NOSIG