APRS Packet Errors for WLKMTN (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
20190221181810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221184810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221191810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221194810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221201810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221204810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221211810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221214810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221221810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine
20190221231810WLKMTN>BEACON,qAO,BALLPT:;NEAR Chemult 147.4700 MHZ T162.2 MEETING: 1st SAT at ODOT La Pine