On Sep 30, 3:15*pm, Judy Ruprecht wrote:
[snip]
Please check your User Guide for the 302 - I seem to recall that the
omni-present declaration is a user-set option in this model... if so, you
may want to see what the other option(s) is/are.
[snip]

Judy

I am pretty sure there are no settings in the Cambridge 302 that
change this type of declaration behavior or persistence. There are no
settings exposed in the Cambridge utilities or in the documented
dataport commands, and the 302 documentation describes only one
behavior of "Header data is stored with each flight log file. This
means pilot name and task declarations can be changed from flight to
flight." After hassles with people clobbering past declarations with
the Model 20/25 I bet they were happy to be able to claim that.

I suspect the main area of confusion is always just editing/defining a
task vs. actually declaring it, whether doing so from a PDA or from a
Cambridge 303.

So with a 302 you can change the declaration and it will persist for
all future flights until changed again or deleted. The documentation
implies the change to the task is supposed to be made to the next
flight log--in principle stopping you accidentally editing your
current declaration. But I have never tested what actually happens
with the 302 if you try this.

Darryl