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
20241226183003EA1JAY-1>APRS,TCPIP*,qAC,THIRD:;LEMD *261830z4029.38N/00333.83W_000/t050h71b10260 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 261730Z 00000KT CAVOK 10/05 Q1026 NOSIG
20241226194502EA1JAY-1>APRS,TCPIP*,qAC,SECOND:;LEMD *261945z4029.38N/00333.83W_000/t045h87b10270 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 261900Z 00000KT CAVOK 07/05 Q1027 NOSIG
20241226200003EA1JAY-1>APRS,TCPIP*,qAC,NINTH:;LEMD *262000z4029.38N/00333.83W_000/t045h87b10270 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 261900Z 00000KT CAVOK 07/05 Q1027 NOSIG