APRS Packet Errors for KLNS (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
20260208173920K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *173919h4007.34NA07617.66WDLancaster Airport
20260208180748K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *180747h4007.34NA07617.66WDLancaster Airport
20260208183238K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *183237h4007.34NA07617.66WDLancaster Airport
20260208190054K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *190053h4007.34NA07617.66WDLancaster Airport
20260208192839K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *192838h4007.34NA07617.66WDLancaster Airport
20260208195433K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *195432h4007.34NA07617.66WDLancaster Airport
20260208202050K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *202049h4007.34NA07617.66WDLancaster Airport
20260208204913K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *204912h4007.34NA07617.66WDLancaster Airport
20260208211640K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *211639h4007.34NA07617.66WDLancaster Airport
20260208214415K2IE-15>APRX29,WIDE2-2,qAR,W3AD-1:;KLNS *214414h4007.34NA07617.66WDLancaster Airport
20260208221101K2IE-15>APRX29,WIDE2-2,qAR,N3TJJ-11:;KLNS *221059h4007.34NA07617.66WDLancaster Airport