APRS Packet Errors for CT1EBQ (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
20220810154554CT1EBQ>APBPQ1,CQ0PCV-3*,qAR,CQ0PQC-5:;SO-50 *165403h3900.00N3900.00WSAOS16:54 mEl10 Az281 Lat39N Long39W Rg2747Km @IM58 Mode:FM
20220810164355CT1EBQ>APBPQ1,CQ0PCV-3*,qAR,CQ0PQC-5:;JAISAT 1 *175204h2200.00N2200.00WSAOS17:52 mEl12 Az218 Lat22N Long22W Rg2307Km @IM58 Mode:XPDR
20220810164655CT1EBQ>APBPQ1,CQ0PCV-3*,qAR,CQ0PQC-5:;CAPE 3 *175503h3200.00N3200.00WSAOS17:55 mEl17 Az258 Lat32N Long32W Rg2286Km @IM58 Mode:APRS
20220810185055CT1EBQ>APBPQ1,WIDE1-1,WIDE3-3,qAR,CT1EDG-3:;RS-15 *195904h6000.00N6000.00WSAOS19:59 mEl34 Az321 Lat60N Long60W Rg5263Km @IM58 Mode:XPDR
20220810204353CT1EBQ>APBPQ1,WIDE1-1,WIDE3-3,qAR,CT1EDG-3:;FO-99 *215204h2100.00N2100.00WSAOS21:52 mEl12 Az213 Lat21N Long21W Rg2367Km @IM58 Mode:XPDR
20220810211458CT1EBQ>APBPQ1,CQ0PCV-3*,qAR,CQ0PQC-5:;PSAT2 *222303h2900.00N2900.00WSAOS22:23 mEl14 Az244 Lat29N Long29W Rg2279Km @IM58 Mode:APRS