Transferring Flight Plan from Foreflight - Runways and Crossing Altitudes?

[Harold Roberts]

Should I expect that when I transfer a flight plan from Foreflight, and I have the runway of an airport selected in Foreflight, will this runway be in the EFIS flight plan and will the HITS boxes for landing at the runway be active? On a recent x-country, the runway did not transfer and I had to manually add it in the EFIS.

When I manually add a runway to an airport waypoint, I notice that the HITS boxes on the flight leg go to the center of the airport, not to the entryway of the HITS boxes for the runway glide HITS boxes. If I put in an altitude along with the runway will the HITS boxes for the leg join the glideslope HITS boxes for the runway at the altitude entered?

Along similar lines, if I have crossing altitudes identified in Foreflight will these also transfer for each leg?

Finally, if I have a waypoint at one altitude and another at a different altitude, will the HITS boxes ascend or descend on a particular leg?

Thanks,

H. Roberts

[Harold Roberts]

Hi, I posted this a month ago. Any comments?

[Jonathon]

Hal neither runway information nor enroute altitude profiles are going to push over from Foreflight, so these will need to be manually added from the FPL menu afterward.

HITS boxes for enroute flight plans are always drawn level with the altitude bug, and will not show a descent or ascent profile if one is entered into the flight plan.

The HITS boxes for the enroute flight plan and the HITS boxes for the final glidepath to destination runway are drawn separately. They not intended to coincide, as this would be suggestive that the pattern be flown as a straight-in approach, and this would not be appropriate. In an ideal world we would render HITS boxes for a proper left or right handed traffic pattern as entered into most appropriately given the inbound direction of the flight plan. The reality, however, is that such a feature is beyond the scope of our current EFIS platform.