Too each his own I guess. As a pilot who has managed to accumulate all the
minor badges with the little shiny stones on without actually having a claim
turned down for documentation reasons my approach would be to state the TP
styles in use, both 'distances' to the actual tps and the shorter version if
BC's are used.

Ian


"Eric Greenwell" wrote in message
...
tango4 wrote:
Beer cans grew out of the use of the early GPS systems that were unable
to
accept the programming of a sector based 'observation zone'. The really
silly thing is that now the technology has caught up we have just
embedded
the beercan more firmly in the rules.

What you need, having declared a point turnpoint, is a piece of software
that calculates the centre point of a beercan that has its centre 1km
beyond
the actual point on the external bisector of the inbound and outbound
tracks!

This means that you declare the 'false' beercans and just fly into their
observation beercans and head for home. Either that or just declare 1km
longer for each tp used.

Of course you now have to write on the declaration the type of OO
sectors
used, the normal task distance and the 'corrected' task distance.

Will written declarations really require the task distances, when the
electronic declarations won't?

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

Eric Greenwell
Washington State
USA