powersloshin said..The main reason to post to KA72 is that all files are available for download and scrutiny by all members, if kept public. So any post can be easily checked with other software if wanted.
And I give you an example from my files, where the max speed track is impossible, but the error was not picked up by GPS Results or GPSSpeed reader either, so I just posted the second best speed, which was legit:
www.ka72.com/Track/t/503671I also downloaded the file you mention and same issue: both SpeedReader and GPS Result validate the crash data.
Only if you disable the filters in GPS Speedreader, or change their values. Note that when you do this, the "Post to GPSTC" button on the result web page is disabled, so you cannot post this directly from Speedreader.
Here is the region in Speedreader with default filters enabled:

The entire crash region is filtered (red) because the error estimate is above the threshold (1.2 knots for Motion data).
This region is obviously NOT filtered by ka72.com. The likely reason is that ka72.com uses a different threshold - most likely either 2 or 4
m/s. The important part is the unit: it should be knots (as in GPSResults and in GPS Speedreader), but instead is m/s, so it's actually about 3.9 knots (or even 7.8 knots), which is way too high.
The unit bug for the speed accuracy filters actually means that
the error estimates in GT-31 data are totally ignored by ka72.com, since the threshold (7.8 knots) is higher than the maximum value in GT-31 data(just below 5 knots). For Motion data, they are just much too high. All this has been pointed out many months ago, but nothing changed on ka72. Quite ironic, considering that only units with error estimates can be approved for GPSTC, but for postings made from ka72, error estimate filters do not work (and probably never have worked).