APRS Packet Errors for LEMD (last 24 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
20250508070003	EA1JAY-1>APRS,TCPIP,qAC,FOURTH:;LEMD 080700z4029.38N/00333.83W_000/t050h93b10110 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 080600Z 00000KT 9999 SCT019 10/09 Q1011 NOSIG
20250508071503	EA1JAY-1>APRS,TCPIP,qAC,SIXTH:;LEMD 080715z4029.38N/00333.83W_000/t052h87b10110 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 080630Z 00000KT 9999 BKN019 11/09 Q1011 NOSIG
20250508073003	EA1JAY-1>APRS,TCPIP,qAC,FIFTH:;LEMD 080730z4029.38N/00333.83W_000/t052h87b10110 Aeropuerto de Adolfo Suárez Madrid-Barajas: LEMD 080630Z 00000KT 9999 BKN019 11/09 Q1011 NOSIG