Nice one! I'll put this into the default TCD file. Thanks!
An option for finding such places on other tracks would be to disable safety ratings temporarily, have standard races and then take a look into the LOG file, because every raised and withdrawn yellow flag is now reported together with nodes where this happened.
Very hard to fix this error. It it bad communication between Airio and LFS server, bad data being received that look almost like LFS packets but are not - decoding rutines process the data assuming they have correct form and fail at that.
This broken communication almost never happens when Airio runs locally, on the same PC where also LFS server(s) run. The less reliable the connection between Airio and server the higher the probability of TCP errors leading to Airio disconnects (and automatic reconnect attempts within 5 minutes).
Practical note: I was getting many such errors when running Airio from my PC through Wi-Fi to very remote servers. The connection was broken every so often - bad packets received turned into errors (captured, reported) in the InSim library, leading to disconnects. The solution is to move Airio closer to the LFS server.