Yesterday I was with a fellow in his non-Avidyne airplane, following along his round-robin on my Foreflight. Just like Garmin and King, Foreflight doesn't like round-robin flight plans. The problem with all these devices is that they presume the intermediate airports are waypoints at which landings are not anticipated, therefore approaches cannot be loaded for them. Furthermore, only Avidyne (to my knowledge) supports loading multiple approaches at one time - such a nice feature for IFR practice or training.

I have not yet used bi-directional communications with Foreflight and Avidyne IFDs - primarily because I file everything direct destination and let ATC modify it if they want (which they do less than 10% of the time on my numerous flights below 12,000 east of the Mississippi). 

Since Foreflight now integrates with Avidyne, I'm going to suggest to them that they allow a flightplan such as my round-robin with chosen approaches at each airport to be displayed properly on Foreflight - just as it is on the IFDs.

Tomorrow I am going to do some hangar flying and connect my Bluetooth keyboard and connect my Foreflight to my IFD through my Stratus 2S wireless, and once all that working, learn how to pass flightplans between the IFD and Foreflight. I'm also going to try using my new 

My question is - does anyone know what Foreflight does if I push a flightplan like my round-robin containing chosen approaches from the IFD to Foreflight?

 

This is a very neat feature of the IFDs, but it doesn't always work so well and it can be much more difficult to straighten out in an IFD than a Garmin when things start getting weird.  Sometimes you can't sequence an approach properly and the only way to fix it is to delete an approach to a previous airport, which is not very intuitive.  Some people put bogus waypoints between approaches all the time to try to work around this issue.  You have to do this prior to loading the approaches since you can't always load a waypoint between approaches.

Maybe I am missing something, but would you not just go direct to next airport or IAF after done with the current approach.

The IFD makes switching to the next airport so dang easy anyway... I don't think I would gain anything by trying to weave all of the airports and their approaches together... seems un-realistic thing to do imo.

Doug 

Yes, I very seldom push a flight plan, it is so fast to enter into the IFD.

* Orest

This doesn't always work.  If your alternate IAF shares a waypoint with the missed hold point from your original intended destination, the IFD sucks the IAF into the missed of the previous approach.  If you go direct to that waypoint, you'll loose the procedure turn.  The only way is to delete the previous approach.  It may not be a daily problem, but it's a gotcha hiding out there.  Having your alternate near your intended destination is not uncommon in areas with typical localized fog.

If you hit direct to the alternate while you are on the missed then set up an approach for the alternate, you'll have to turn the AP off while you set up the approach so it doesn't start pulling you off in the wrong direction and this essentially is the same as adding a bogus waypoint (the airport prior to the approach).

It is often good practice to go into heading mode, when altering your flight plan, but I've not seen the behavior you outline above. 

When adding an approach, one of two things will happen. If already direct the airport, the approach will be added after the airport with another instance of the airport itself, so as not to disturb your current leg. If you are not direct the airport, then the approach will be added before the airport in sequence, and you will eventually need to tell the navigator how you want to transition from the last existing flight plan leg, to one of the approach segments.

* Orest