APRS Packet Errors for PC4L-11 (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
20260329195215PC4L-11>APETBT,qAO,PC4L-10:@195210h0000.00N/00000.00EO/A=000000 BALLOON
20260329195525PC4L-11>APETBT,qAO,PC4L-10:@195518h0000.00N/00000.00EO/A=000000 BALLOON
20260329195839PC4L-11>APETBT,qAO,PC4L-10:@195826h0000.00N/00000.00EO/A=000000 BALLOON
20260329210340PC4L-11>APETBT,qAO,PC4L-10:@000000h0000.00N/00000.00EO/A=000000 BALLOON
20260329210645PC4L-11>APETBT,qAO,PC4L-10:@000000h0000.00N/00000.00EO/A=000000 BALLOON
20260329210951PC4L-11>APETBT,qAO,PC4L-10:@000000h0000.00N/00000.00EO/A=000000 BALLOON
20260329211257PC4L-11>APETBT,qAO,PC4L-10:@000000h0000.00N/00000.00EO/A=000000 BALLOON
20260329211732PC4L-11>APETBT,qAO,PC4L-10:@000000h0000.00N/00000.00EO/A=000000 BALLOON
20260329212254PC4L-11>APETBT,qAO,PC4L-10:@000000h0000.00N/00000.00EO/A=000000 BALLOON
20260329212604PC4L-11>APETBT,qAO,PC4L-10:@000000h0000.00N/00000.00EO/A=000000 BALLOON
20260329213539PC4L-11>APETBT,qAO,PC4L-10:@213534h0000.00N/00000.00EO/A=000000 BALLOON