On the same day, but at a different turnpoint, Greg Kendall also
experienced his Flymaster tracker missing a turnpoint, just as Jonny's Flymaster
tracker did.

Here are the two track logs, one of the Flymaster Tracker and one from Greg's
5030.

Let's take a little closer look:

The red line track is from his 5030 and the blue is from the Flymaster tracker.

Daniel Velez, the remote scorekeeper, finds the missing data from the Flymaster
tracker:

Actually there is 1 minute and 06 seconds of missing info that the
tracker had an "invalid" reception (as I understand) so it didn't recorded a
position on the IGC file during that period.

B2131023259416N11127605WA0000001540

B2131033259424N11127594WA0000001539

B2132093259986N11127490WA0000001387

B2132103259996N11127494WA0000001386

On the last day my Flymaster tracker quits recording data on my
final glide to just short of goal. It stops when I'm a little over 3,000'. The
red line is the Flymaster Tracker:

It was fortunate that Daniel caught this problem as it wasn't obvious unless you
looked at the altitude data. Pilots might consider this if they see a result that
shows you short of where you thought you landed. Daniel caught this before we
saw any preliminary data.

Note that the Flymaster tracker also consistently records a higher GPS altitude
than the 6030's barometric altitude, even though they start at the same
altitude:

Your Flymaster tracker might show you going into airspace, while your 6030 shows
you below the floor of the airspace. You might want to check with the
scorekeeper if you find yourself penalized for air space infringements that your
6030 showed you avoiding.