freq function

When I’m in the aircraft, at the same position, and enroute between A and B or B and C, I still get the information for airport A. This is not the case with the PROC button, which shows the correct next airport in my plan.

What am I doing wrong with the panel mount IFD 440, versus the simulator?

I should have been clearer. The Airport tab, which is the first tab that comes up on the Frequency page, is where I see frequencies associated with the ATIS or tower. If I fly from point A to point B, I reliably see the information about the destination airport once I’ve departed the origin airport.

If I include a series of airports along my route, the Airports tab, in the simulator, will show the information for each of these airports as I approach them. IRL, I only see the destination Airport’s information in this tab, and when the flight is a round robin coming back to the origin airport, it means I just see the same information in this tab all the time.

I pointed out how the PROC function works since this is how I expected the FREQ function to work; it shows the procedures available for the next airport in the flight plan, and subsequent presses of the PROC key advance from airport to airport in the flight plan. You can’t push the FREQ key multiple times on the 440, which doesn’t have a FREQ button, but it should still show the information for the next airport in the flight plan, as it does in the simulator.

Why is this useful? The Frequency Enroute tab provides many of the frequencies that you might want in terms of flight following, including Centers, Approach Controls, and even FSSes. It doesn’t include tower airspace frequencies that you might fly through and want to request a transition of, or just check the ATIS as you overfly.

The only difference between the two now is loading the flight plan in the plane from ForeFlight, which as you know doesn’t understand multiple destinations in a flight plan.

Still, I would have thought importing the waypoints into a stored IFD route would have made each airport waypoint a potential “destination” along the route.

I’ll try this later this week and report back. 

I don’t want an enhancement; the way it works in the simulator is exactly how I’d like it to work, but perhaps importing a flight plan has some unexpected impact on the way it works. 

I’ll see if I can reproduce the behavior by importing a flight plan into the simulator from ForeFlight.

Thanks!