On Sep 29, 6:49*pm, Uncle Fuzzy wrote:
On Sep 29, 6:13*pm, T8 wrote:





On Sep 29, 7:45*pm, Chris Ruf wrote:

On Sep 29, 2:45*pm, Judy Ruprecht wrote:

- * * * Almost all IGC Approved FRs accept the 6 characters permitted for US
registration numbers; use FR “set up” software to enter the glider’s
registration (“N”) number in the “Glider ID” data field.

So if we use the N number in the flight recorder then use that flight
recorder for a US contest we might have trouble with Winscore.
Winscore keys pilot identity off the Contest Number.

Maybe we request a modification and get winscore to read in either
contest ID or N Number and output Contest ID. *[would need to add N
number record to the Contestant data].

Without this change it would be a major hassle to have to switch back
and forth between Contest ID and N Number. *This could be mutually
exclusive if you wanted to do a declared task during a contest day.

Chris

The best fix would be to get the registration # requirement out of the
Sporting Code. *It adds NOTHING. *It's the OO's job to associate
pilot, flight recorder and sailplane at the start of the flight.
Having N number, serial number or even pilot name in the e-declaration
is meaningless without the OO to testify that things are, in fact
correct, and this done on the application (which the OO must sign).
No logical reason to do it twice.

-Evan Ludeman / T8- Hide quoted text -

- Show quoted text -

I'll grant that it seems redundant. *I have experience only with
Cambridge CFRs, but it takes just a minute or two to change the glider
reg number and / or pilot name. *If you are making your declaration
electronically, you're in there anyhow. *I use the Cambridge utility
3UTPC255.EXE from my laptop, or 3UTIQ257.exe from my pda. *Unless I'm
mis-reading the Badge Lady's post:

"...and in any case when pilot, aircraft or task data entered in an FR
cannot
be verified for accuracy and changed if necessary before take off:
- * * * The pilot prepares a written declaration ready for an OO’s
signature
- * * * On the intended flight date, the OO performs a pre-flight FR
installation check and the FR is turned on; a task may be entered if
desired
- * * * The OO waits a few minutes, then adds his/her signature, date
& time to
the written declaration
- * * * No further tinkering with FR task entry, and make sure the FR
remains ON
until after landing"

Sounds like a paper declaration is still valid, assuming the above
procedure is followed.
One thing to watch out for if you are making the declaration
electronically.... at least on the Cambridge units, I'm pretty sure
the power has to be cycled after making the delaration in order for
the CFR to log the flight.

I'll be a whole lot more upset if they ever get rid of sectors than
this bit of administrivia will get me. *I've proven to myself dozens
of times I can't hit a cylinder @ 16,000 feet without being head down
and locked staring at a pda.

Sounds like you are using a Cambridge 302, there should be no reason
to reboot a 302 after making a declaration. And I would not do that.
Basically set pilot and glider info and make the electronic
declaration and then don't touch anything. And then make and have the
OO sign the paper declaration just in case.

Ditto on the thanks to Judy.

Darryl