See You Mobile Declared Task Pilot Name

On 8/05/2013 01:48, Paul Remde wrote:
Hi Pete,

I don't use written declarations. I've never had a problem in 15 years
with electronic declarations for many badge and record flights. If it
is done correctly it is extremely reliable.

But how reliable is it if NOT 'done correctly'? How easy is it to know
it's been 'done correctly' electronically compared to a written
declaration?. Written ones are inherently 'extremely reliable' for
those of us who aren't software gurus.

If software was reliable, straightforward and predictable, the number of
posts on r.a.s. would be halved.

GC



Best Regards,

Paul Remde
________________________________

"Pete Startup" wrote in message
...

For the flights that matter? - hand written declaration every time. Would
you trust your diamonds to gadgets?

At 05:58 07 May 2013, Wade wrote:
If see you mobile was registered to someone else and they are letting you
borrow their PDA for a badge flight, the name attached to the
registration
is what gets declared to any other devices linked up (Cambridge 302 for
example).

I can enter a separate pilot in the Cambridge 302/303 but I don't want a
task declared through to the 302/303 with a different name from see you
mobile. Does anyone know a good solution to this one?

Thanks
Wade

On Tuesday, May 7, 2013 7:09:54 PM UTC-7, GC wrote:
But how reliable is it if NOT 'done correctly'? How easy is it to know

it's been 'done correctly' electronically compared to a written

declaration?. Written ones are inherently 'extremely reliable' for

those of us who aren't software gurus.


If software was reliable, straightforward and predictable, the number of

posts on r.a.s. would be halved.
------------------------------------------------------------------------------------------------------------

On June 16, 2004, this happened to me - only time since 1996.

I was not aware of any problem until my OO opened the trace.

Then, learned:

Declaration is NOT VALID!
Task: Triangle - (305.9km)
Task distance: 305.9km

Points:
1) Ephrata
2) Waterville
3) Davenport
4) Ephrata

All reached turn points rounded ok. Task Completed.
Distance: 305.9km, Duration: 04:16:53, Speed: 38.55kts

Sent to The Badge Lady anyway.
She asked if OO had verified a written declaration before take-off.
If done, Badge leg done ok; if not, sorry.

Flew for fun on June 20 and 21, then flew another 300+km triangle on the 22nd.

Oh, yeah, did a verified written declaration before that flight – and every Badge leg fight attempt since, including my next ones.

Hi Roy,

Did you do the failed electronic task declaration before or after take-off?

Paul
_________________________

"Roy Clark, "B6"" wrote in message
...

On Tuesday, May 7, 2013 7:09:54 PM UTC-7, GC wrote:
But how reliable is it if NOT 'done correctly'? How easy is it to know

it's been 'done correctly' electronically compared to a written

declaration?. Written ones are inherently 'extremely reliable' for

those of us who aren't software gurus.


If software was reliable, straightforward and predictable, the number of

posts on r.a.s. would be halved.
------------------------------------------------------------------------------------------------------------

On June 16, 2004, this happened to me - only time since 1996.

I was not aware of any problem until my OO opened the trace.

Then, learned:

Declaration is NOT VALID!
Task: Triangle - (305.9km)
Task distance: 305.9km

Points:
1) Ephrata
2) Waterville
3) Davenport
4) Ephrata

All reached turn points rounded ok. Task Completed.
Distance: 305.9km, Duration: 04:16:53, Speed: 38.55kts

Sent to The Badge Lady anyway.
She asked if OO had verified a written declaration before take-off.
If done, Badge leg done ok; if not, sorry.

Flew for fun on June 20 and 21, then flew another 300+km triangle on the
22nd.

Oh, yeah, did a verified written declaration before that flight – and every
Badge leg fight attempt since, including my next ones.