Garmin 430 tips and tricks

[stuckingfk]

After flying with these two 430's for quite some time, I have picked up a few things that others haven't and thought I'd pass it on to anyone who wants to read.

And I would like anyone else to post their tips too, so I can learn more along with others.

1. Declutter/Clutter is the Clear Button when on Nav 2 page. This shows roads, airports, towns, rivers, lakes. If you don't want it, hit clear, if you still think there is too much, hit clear again until you get a 3 right by map scale. After 3, if you hit clear again, it goes to most clutter and shows nothing by map scale number.

2. Best way I have found to fly an approach using GPS guidance, top GPS Nav 2 with Data Fields Off (Go to Menu), then have the bottom GPS on the Nav 1 page with your DME information, GS, TRK, DTK, etc.

3. People, use the nearest book, then scroll through the pages to find what you need. This is much much easier than plugging it in with the Direct button.

4. Flying NDB approaches using the GPS without loading the approach. Waypoint should be NDB, then go to Nav 2 page, hit OBS, but in the outbound course to NDB. This will give you a nice white line to follow on the inbound/outbound if your examiner doesn't let you load the approach. Hit the CDI button so GPS shows and follow your Nav instrument it is tied to.

I have many more, but I gotta run. Any others, please post.

[TallBoy85]

There was some little trick where if you held the radio tuning knob in for a certain amount of time, your active com was automatically tuned to 121.50...guess they should have labeled it the panic button.

[roundout]

yes, the <-C-> button which switches comm frequencies from standby to active, if you hold that down for about 3 seconds it switches active comm to 121.5.

[BobDDuck]

Not really a trick, but not very well document all the same, if you are flying a visual approach you can tune the OBS on NAV1 to the runway heading and then click the OBS button on the 430. This will draw an extended runway centerline on the GPS to help with when to turn final. Also I find using the NRST feature to find FSS or Flightwatch availibility is pretty useful as well. One that doesn't get a whole bunch of use is the Sunrise/Sunset calculator. I've used this a few time to figure out when I could start logging night time.

Ethan

[DE727UPS]

How can I build a waypoint using lat/long and then create a course to that waypoint?

I'm doing my first IFR student in my 152/G. I swear that little box does more than the FMC on the 767.

[av8rmsu]

[ QUOTE ]
How can I build a waypoint using lat/long and then create a course to that waypoint?

I'm doing my first IFR student in my 152/G. I swear that little box does more than the FMC on the 767.

[/ QUOTE ]


go to the user waypoints and create it.

then use the direct feature...or i usually put it into a flight plan

[Looking4Lower]

[ QUOTE ]
4. Flying NDB approaches using the GPS without loading the approach.

[/ QUOTE ]

I might be wrong, but I think this is a no-no. I know that you can sub the GPS for an NDB, but I don't think you can create your own homemade GPS overlay approach over an existing NDB approach. It would need to have an official overlay that says "or GPS" on the approach plate (AIM 5-4-5 (3)).

I believe this is because when you select a "direct to" waypoint, the 430/530 will stay in "enroute" sensitivity mode with 5 nm accuracy which isn't nearly enough for an approach.

I'm not 100% sure about this one...does anybody have any insights?











sorry, I hate to hijack the thread

[roundout]

as long as you don't use the GPS as primary nav, then you should be ok with this. it'd be much like shooting a VOR approach and backing it up with the 430.

[roundout]

you can also turn the CDI sensitivity scale to 5, 1, and .3 manually using the AUX>CDI page.

[stuckingfk]

[ QUOTE ]
you can also turn the CDI sensitivity scale to 5, 1, and .3 manually using the AUX>CDI page.

[/ QUOTE ]

There was something I didn't know. Thanks Grant! For some reason I thought the accuracy was 2, 1, and .3 according to the Instrument Flying Handbook.

And to the previous poster, you can use it for guidance only. Weird thing is, I did that about an hour ago, and it was much more accurate than the NDB approach.

[Looking4Lower]

[ QUOTE ]
[ QUOTE ]
you can also turn the CDI sensitivity scale to 5, 1, and .3 manually using the AUX>CDI page.

[/ QUOTE ]

There was something I didn't know. Thanks Grant! For some reason I thought the accuracy was 2, 1, and .3 according to the Instrument Flying Handbook.

And to the previous poster, you can use it for guidance only. Weird thing is, I did that about an hour ago, and it was much more accurate than the NDB approach.

[/ QUOTE ]

Agreed - and that brings me to my own tip that an examiner taught me on my ATP ride. When you're shooting a GPS approach, the approach mode accuracy is pretty decent but perfect. If you zoom WAY into the screen (Nav 1 or 2), you can see your displacement from the final approach course line. I'm talking about zooming down to 300-1000 feet resolution or so.

Even if your HSI needle shows you dead-on, if you zoom way down you can fine-tune your course to put you even more accurately on course, right to the runway centerline.

[Looking4Lower]

Here's one that some people might not know. If you're shooting an ILS-DME approach (or otherwise need to get a DME off an ILS localizer for some reason) then you can punch in the localizer identifier as your GPS waypoint (i.e. if the localizer I.D. is I-ABE, punch in IABE) and read the distance. The 430/530 lists localizer DME waypoints as intersections when they come up.

[mtsu_av8er]

Examiner tried to get me on that one for my CFII ride....EASY!!!

[stuckingfk]

[ QUOTE ]
Here's one that some people might not know. If you're shooting an ILS-DME approach (or otherwise need to get a DME off an ILS localizer for some reason) then you can punch in the localizer identifier as your GPS waypoint (i.e. if the localizer I.D. is I-ABE, punch in IABE) and read the distance. The 430/530 lists localizer DME waypoints as intersections when they come up.

[/ QUOTE ]

Commone knowledge around here!!

Doing the approach to the 35L ILS has IGFK as the DME to identify the OM, which is also identified by the NDB collocated with the OM.

Another thing I love, having the North Up option for the Nav 2 page. I have been teaching the students this and they love it. Basically what it does is when you have the approach loaded in, the inbound course looks exactly like the inbound course. So you can tell where at on the plate you are at all times.

[GaTechKid]

[ QUOTE ]
Not really a trick, but not very well document all the same, if you are flying a visual approach you can tune the OBS on NAV1 to the runway heading and then click the OBS button on the 430. This will draw an extended runway centerline on the GPS to help with when to turn final.

[/ QUOTE ]

Related to this, I learned on my checkride today that you can paint the airways on the GPS by selecting the navaid as your waypoint, spinning in the radial on your nav 1/2, and hitting the OBS button. It helps in intercepting the airway.

[PhotoPilot]

[ QUOTE ]
Here's one that some people might not know. If you're shooting an ILS-DME approach (or otherwise need to get a DME off an ILS localizer for some reason) then you can punch in the localizer identifier as your GPS waypoint (i.e. if the localizer I.D. is I-ABE, punch in IABE) and read the distance. The 430/530 lists localizer DME waypoints as intersections when they come up.

[/ QUOTE ]

I've tried to get that to work on the KLN-89B with no success. Anyone know if it's doable?

[pscraig]

[ QUOTE ]
Here's one that some people might not know. If you're shooting an ILS-DME approach (or otherwise need to get a DME off an ILS localizer for some reason) then you can punch in the localizer identifier as your GPS waypoint (i.e. if the localizer I.D. is I-ABE, punch in IABE) and read the distance. The 430/530 lists localizer DME waypoints as intersections when they come up.

[/ QUOTE ]

Not all localizers are in the database though. There seems to be no pattern to whether or not it's included. When I was in Richmond, none of the KRIC localizers were in the database, but localizers for nearby airports were.

[stuckingfk]

[ QUOTE ]
[ QUOTE ]
Here's one that some people might not know. If you're shooting an ILS-DME approach (or otherwise need to get a DME off an ILS localizer for some reason) then you can punch in the localizer identifier as your GPS waypoint (i.e. if the localizer I.D. is I-ABE, punch in IABE) and read the distance. The 430/530 lists localizer DME waypoints as intersections when they come up.

[/ QUOTE ]

Not all localizers are in the database though. There seems to be no pattern to whether or not it's included. When I was in Richmond, none of the KRIC localizers were in the database, but localizers for nearby airports were.

[/ QUOTE ]

A couple localizers near here don't have them. And both have the DME based off a VOR and not the localizer.

Not sure if that is the reason or not.

[Foxcow]

[ QUOTE ]
How can I build a waypoint using lat/long and then create a course to that waypoint?

I'm doing my first IFR student in my 152/G. I swear that little box does more than the FMC on the 767.

[/ QUOTE ]



Or you can hit the cursor button on the moving map page and get a movable hand. The larger knob will move it left and right while the smaller knob moves it up and down. When you have the cursor on the location you want, whether it be a lake, part of a road, an intersection, etc, hit direct to.... very handy.