Good point.

But what if it was just a few dozen extra miles at 150mph? Enough, for
example, to get a record, but not so much that the eyes go wide with
wonder?

Seems clear that tampering can be managed from outside the unit while
producing secure, valid record files. I've been amused, for instance,
that the OLC will highlight a flight if it is downloaded improperly or
transfered among media prior to uploading, but otherwise assume all is
well.

It's tough to thwart a determined cheater. But since the vast majority
of cheating is a matter more of convenience than maliceaforethought, to
most of us the emphasis on security seems draconian. Now that we have
clear evidence that there are external devices that can spoof our
recorders, is it the next step to require that recorders have some
protection against such possibilities? Or is this where we throw up our
hands and say "enough" and put the responsibility back into the hands
of the observer?

As an SN10 owner, I've always wondered at the prohibition of external
GPS engines. Doesn't seem like the cable is really at issue anymore.
Granted, it would take a smart guy with access to the proper tools, but
that's also true of altering files post flight.

Note that 1XX's trace may not be the result of a random anomaly but an
indication of intential interference from a ground based transmitter.
If I can spoof the signal, can't I then create the file? With the right
set of tools and expertise (and an observer willing to cut some
corners), I could fly to 100,000 feet and circumnavigate the globe...
and deliver uncorrupted proof of my accomplishment. Getting people to
accept the proof then is just a matter of proportion.


Eric Greenwell wrote:
wrote:
With the recent concerns (last year) over the security of traces, I'm
surprised the validation softward didn't have some trouble with your
data. If I were an alogorithm, I would take special interest in your
118 statute mile leg completed at 474 miles per hour. Fly impressive do
you, Jedi master.

The algorithm that checks for this kind of problem resides in the head
of the official evaluating the flight. Clearly bad points, temporarily
dropped GPS signals or power loss, etc, are infrequent and best handled
by a person, as they do not automatically invalidate a file or a flight.
The IGC validation software checks the flight file for (basically)
tampering only, and not external problems.


--
Change "netto" to "net" to email me directly

Eric Greenwell
Washington State
USA