No Mark, if you look at the noise trace it is reasonable, and at the
'photo landing' time noise is relatively low. The problem is clearly
the setting of the TP zone radius, and the 'photo landing' is at the
closest approach to the waypoint, since the flight path never enters the
zone within the radius set.

In SeeYou, go into Edit/Flight Properties/Observation Zone. Change the
two waypoint radii from 3km to 30km. The flight is now analysed as
completed at a speed of 82.58 kph.

Interestingly, the analysis also shows that every thermal was turning
right.

I have seen traces where SeeYou interprets a noise peak (due to opening
the DV panel for extra ventilation) as an engine run, but this isn't one
of them.

At 11:00 11 November 2008, Mark Dickson wrote:
I don't think the problem is with Seeyou, I think the problem is with
your
302. I often get a similar result from Seeyou using a 302. The problem
is
with the engine noise detector; despite having a pure sailplane the 302
is
too sensitive and picks up noise that is assumed to be engine noise by
Seeyou. Next time you open one of your flights in seeyou, right click,
select flight properties and check pure glider.
There is a modification that Dickie Feakes (UK) does to the 302 to solve
this problem; maybe you have someone in the US that can do the same.