APRS Packet Errors for FW2332 (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
20260210161107	FW2332>APRS,TCPXX*,qAX,CWOP-4:/101611z4737.94N/12235.79W_323/001g000t040P000h00b10201L017FW2332 101710Z 32001KT 10SM CLR 04/04 A3012 RMK AO2 SLP201 T00440043=
20260210161121	FW2332>APRS,TCPXX*,qAX,CWOP-7:/101609z4737.94N/12235.79W_335/001g000t040P000h00b10201L029FW2332 101708Z 33001KT 10SM CLR 04/04 A3012 RMK AO2 SLP201 T00430043=
20260210161307	FW2332>APRS,TCPXX*,qAX,CWOP-4:/101613z4737.94N/12235.79W_021/001g000t040P000h00b10204L022FW2332 101712Z 02001KT 10SM CLR 04/04 A3013 RMK AO2 SLP204 T00440043=
20260210163713	FW2332>APRS,TCPXX*,qAX,CWOP-4:/101637z4737.94N/12235.79W_349/-000g000t041P000h00b10200L019FW2332 101736Z 350-00KT 10SM CLR 05/05 A3012 RMK AO2 SLP200 T00510051=
20260210182737	FW2332>APRS,TCPXX*,qAX,CWOP-5:/101827z4737.94N/12235.79W_024/-000g000t048P000h89b10193L069FW2332 101926Z 020-00KT 10SM FEW001 09/07 A3010 RMK AO2 SLP193 T00910074=