Garmin unveiling?

On Thu, 12 Jul 2007 18:45:27 -0400, B A R R Y
wrote:

Can't you just program the route from Navaid to Navaid, and if
necessary, add the intersections where the airway bends?

Airways always run from something to something else (a Navaid or
intersection). Even a current databased 196 has the pints that define
an airway. While you still need the chart to program it, once it's
programmed, you can easily follow an airway.

That's what I do, but it's really annoying when they give you a
crossing restriction on a fix that isn't a turnpoint in an airway so
now you have to go fishing to find it rather than the entire set of
waypoints constituting an airway being in the plan automatically like
the higher-end FMS.

On Thu, 12 Jul 2007 18:57:15 -0400, Peter Clark
wrote:

That's what I do, but it's really annoying when they give you a
crossing restriction on a fix that isn't a turnpoint in an airway so
now you have to go fishing to find it rather than the entire set of
waypoints constituting an airway being in the plan automatically like
the higher-end FMS.

What happens if you're needing to leave or join the airway midway,
such as at an intersection bend?

If you were to program the airway as a waypoint, wouldn't the unit
expect you to fly it from beginning to end?

On Thu, 12 Jul 2007 19:00:00 -0400, B A R R Y
wrote:

On Thu, 12 Jul 2007 18:57:15 -0400, Peter Clark
wrote:

That's what I do, but it's really annoying when they give you a
crossing restriction on a fix that isn't a turnpoint in an airway so
now you have to go fishing to find it rather than the entire set of
waypoints constituting an airway being in the plan automatically like
the higher-end FMS.

What happens if you're needing to leave or join the airway midway,
such as at an intersection bend?

In the Mustang G1000 and high-end FMS (Collins ProLine, Honeywell a-la
Boeing/Airbus etc) system you program it as entry point, airway, exit
point and it fills in all the waypoints inbetween for you. So, for
example, BOSOX V1 DPK as dialled into a real system with airways (like
the CNX80 or Mustang/FMS) would automatically populate your flight
plan legs window with: BOSOX GRIPE GRAYM DVANY HFD WEGOT MAD BELTT
DPK. To fly that with a 430/530/non-Mustang G1000 would require
dialling in BOSOX GRAYM HFD MAD BELTT DPK. Say Bradly says cross
WEGOT at 11000, now you have to go find WEGOT on the chart and add it
to the plan in the right place then set up the VNAV profile. Pain in
the rear when with the other systems you can just highlight WEGOT,
fill in 11000 for the ALT, and have it tell you the descent rate
required to make the restriction since all waypoints are already in
there.

On Jul 12, 4:00 pm, B A R R Y wrote:
On Thu, 12 Jul 2007 18:57:15 -0400, Peter Clark

wrote:

That's what I do, but it's really annoying when they give you a
crossing restriction on a fix that isn't a turnpoint in an airway so
now you have to go fishing to find it rather than the entire set of
waypoints constituting an airway being in the plan automatically like
the higher-end FMS.

What happens if you're needing to leave or join the airway midway,
such as at an intersection bend?

If you were to program the airway as a waypoint, wouldn't the unit
expect you to fly it from beginning to end?

In the King GPS I had you put two way points and the airway. You could
enter and exit the airway at any waypoint. However, because the GPS
had airways it was smart enough to make all the airway turns and not
just go direct from the first way point to the last (which may have a
mountain in the middle).

-Robert

On Thu, 12 Jul 2007 18:00:39 -0700, "Robert M. Gary"
wrote:


What happens if you're needing to leave or join the airway midway,
such as at an intersection bend?

If you were to program the airway as a waypoint, wouldn't the unit
expect you to fly it from beginning to end?

In the King GPS I had you put two way points and the airway. You could
enter and exit the airway at any waypoint. However, because the GPS
had airways it was smart enough to make all the airway turns and not
just go direct from the first way point to the last (which may have a
mountain in the middle).

Well, Cessna has announced the bug fix/feature list for the latest
G1000 software. It does include airways in the flight plan.

7/23/07 - SB 07-34-02A

Fixes the departure/arrival not overwriting waypoints properly bug
Fixes the 400 storm cell issue with the GDL69A. Also enhances pilots
interface (whatever that means)
Adds inset map into the reversionary mode
Audible alert for user selected BARO minimums
Allows transponder code entry via FMS knob
Adds RX and SQ indicators to the TX indicator for VHF comms
Allows user-selectable lookahead time for track vector
Adds victor airways to flight plan capability
Changes to TAWS system to reduce nuisance alerts, and adds an inhibit
key
Changes splash screen on the MFD to show database status differently
Auto-acknowledge Aural Alert (Configuration changes to ensure aural
alerts are provided at system startup, whatever that means)
Adds support for JeppView
Adds support for Garmin SafeTaxi and FliteChart
Allows XM channel to be dialled in directly
Adds current track bug on HSI
Adds wind component breakout window
Adds VNAV guidance
Adds bug for DH/MDA
Auto-disables TIS on the ground to prevent nuisance alerts, adds "TIS
UNAVAILABLE" mute key
Enhances highlighting of waypoints underlying depicted TFRs
Adds support for ADF Superflag when ADF Superflag signal is sensed

On 07/25/07 13:15, Peter Clark wrote:

Well, Cessna has announced the bug fix/feature list for the latest
G1000 software. It does include airways in the flight plan.

7/23/07 - SB 07-34-02A

Fixes the departure/arrival not overwriting waypoints properly bug
Fixes the 400 storm cell issue with the GDL69A. Also enhances pilots
interface (whatever that means)
Adds inset map into the reversionary mode
Audible alert for user selected BARO minimums
Allows transponder code entry via FMS knob
Adds RX and SQ indicators to the TX indicator for VHF comms
Allows user-selectable lookahead time for track vector
Adds victor airways to flight plan capability
Changes to TAWS system to reduce nuisance alerts, and adds an inhibit
key
Changes splash screen on the MFD to show database status differently
Auto-acknowledge Aural Alert (Configuration changes to ensure aural
alerts are provided at system startup, whatever that means)
Adds support for JeppView
Adds support for Garmin SafeTaxi and FliteChart
Allows XM channel to be dialled in directly
Adds current track bug on HSI
Adds wind component breakout window
Adds VNAV guidance
Adds bug for DH/MDA

Oh ... I hate it when they add bugs ;-\

Auto-disables TIS on the ground to prevent nuisance alerts, adds "TIS
UNAVAILABLE" mute key
Enhances highlighting of waypoints underlying depicted TFRs
Adds support for ADF Superflag when ADF Superflag signal is sensed



--
Mark Hansen, PP-ASEL, Instrument Airplane, USUA Ultralight Pilot
Cal Aggie Flying Farmers
Sacramento, CA

Thanks Guys. It sounds like the bank account (and credit card
balance) will not be assalted this year.

Bob

On Jul 25, 5:17 pm, wrote:
Thanks Guys. It sounds like the bank account (and credit card
balance) will not be assalted this year.

Bob


heck yea...start saving up and chattin' up the mrs. for next year......