While we're talking about Garmin GPS

I presume you mean non-radar full position reports. That is where having the
route as a flight plan would be quite useful.


Windecks wrote:

On an IFR proficiency flight with my partner the other day, we got into a
little debate about the best way to use the Garmin 430 for ATC position
reporting. He uses the cursor on the map page to point at an airport or
NAVAID, then reads out the distance and (reciprocal) bearing. I go to NRST,
and pick an airport or VOR which have continually updated distance and
bearing. For those 430/530 users out there, which way do you prefer?

Wouldn't it be nice to have a 'Position' button; an easy to reach menu
choice, softkey or button that gives the following configurable readout
(don't display what you don't want):

- Distance and reciprocal bearing to the nearest airport
(22nm NW Reid Hillview KRHV)
- Distance and reciprocal bearing to the nearest VOR
(10nm SW Mustang FMG or maybe 215 Radial?)
- Distance and reciprocal bearing to the nearest NDB
- Distance and reciprocal bearing to the nearest intersection
- Distance and reciprocal bearing to the nearest VFR reporting point
- If within 2nm of any of the above, a message that says "Vicinity Squaw
Valley SWR" e.g.

Punch the button, wait for the frequency to clear, then just read off the
position to our friends with the big screens. Punch the button again and
you go back to the previous display. NRST works just fine for me, but it's
always fun to bitch about your expensive, useful panel toys..

wrote in message
...

I presume you mean non-radar full position reports. That is where having
the
route as a flight plan would be quite useful.


In that case you'd just report the compulsory reporting points and any
non-compulsory reporting points as instructed by ATC as you encountered
them.

"Steven P. McNicoll" wrote:

wrote in message
...

I presume you mean non-radar full position reports. That is where having
the
route as a flight plan would be quite useful.


In that case you'd just report the compulsory reporting points and any
non-compulsory reporting points as instructed by ATC as you encountered
them.

And, that is where having the route as a flight plan loaded into the Garmin
would be useful.

wrote in message
...

And, that is where having the route as a flight plan loaded into the
Garmin
would be useful.


Since all the necessary information is provided by the more traditional nav
gear, just how is it useful to load the flight plan into the Garmin?

"Steven P. McNicoll" wrote:

wrote in message
...

And, that is where having the route as a flight plan loaded into the
Garmin
would be useful.


Since all the necessary information is provided by the more traditional nav
gear, just how is it useful to load the flight plan into the Garmin?

It provides an electronic "how goes it" log and ensures you fly legs rather
than direct-to. When the new "G" capstone routes in SE Alaska fire up, there
won't be any underlying VOR route structure, so it will become even more useful
to have a flight plan loaded.

wrote in message
...

It provides an electronic "how goes it" log and ensures you fly legs
rather than direct-to.


As does the more traditional nav gear. So nothing is gained by having the
route as a flight plan loaded into the Garmin.

Steven P. McNicoll wrote:


wrote in message
...

It provides an electronic "how goes it" log and ensures you fly legs
rather than direct-to.


As does the more traditional nav gear. So nothing is gained by having the
route as a flight plan loaded into the Garmin.

When you're *at* a waypoint, it shouldn't make a difference by which means
you've identified the waypoint. You're there. That's what you report.

As I understand this conversation, it's when you're not at a way point that
this discussion rears its head.

However, that does beg the question: on an IFR flight, when would you report
your position while not at a waypoint? I suppose ATC might ask for some
unknown reason (RADAR failure, and shifting into non-RADAR mode, perhaps?),
but I've never experienced that myself.

- Andrew

For non-radar flight plans, sure, you use the reporting points on your
flight plan and those requested by ATC, and they're usually already entered
on the FPL page.

I often launch VFR from an uncontrolled field and then ask for flight
following. Also, my home field is Class C and I need to get a squawk to
approach and land, even if VFR. These requests usualy comes from some
random point enroute, hence the position requirement. Also, it's useful
when asking for a popup IFR clearance, which doesn't happen for me all that
much.

So, a question for the controller types out there--what do you want to hear
on these requests? Type, equipment, altitude? Position in relation to the
nearest VOR? I usually give my callsign, position from the closest VOR, and
equipment if it's an IFR request. They then give me a squawk and ask for an
ident.


wrote in message
...
I presume you mean non-radar full position reports. That is where having
the
route as a flight plan would be quite useful.


Windecks wrote:

On an IFR proficiency flight with my partner the other day, we got into
a
little debate about the best way to use the Garmin 430 for ATC position
reporting. He uses the cursor on the map page to point at an airport or
NAVAID, then reads out the distance and (reciprocal) bearing. I go to
NRST,
and pick an airport or VOR which have continually updated distance and
bearing. For those 430/530 users out there, which way do you prefer?

Wouldn't it be nice to have a 'Position' button; an easy to reach menu
choice, softkey or button that gives the following configurable readout
(don't display what you don't want):

- Distance and reciprocal bearing to the nearest airport
(22nm NW Reid Hillview KRHV)
- Distance and reciprocal bearing to the nearest VOR
(10nm SW Mustang FMG or maybe 215 Radial?)
- Distance and reciprocal bearing to the nearest NDB
- Distance and reciprocal bearing to the nearest intersection
- Distance and reciprocal bearing to the nearest VFR reporting point
- If within 2nm of any of the above, a message that says "Vicinity Squaw
Valley SWR" e.g.

Punch the button, wait for the frequency to clear, then just read off
the
position to our friends with the big screens. Punch the button again
and
you go back to the previous display. NRST works just fine for me, but
it's
always fun to bitch about your expensive, useful panel toys..