IFD and ForeFlight Approach Transfer Errors

Has anyone else run across this (or can try it out to see if you can replicate it)?

Having some issues transferring certain approaches from IFD to ForeFlight (and vice versa).  It only happens with VOR approaches (not VOR/DME) and not with every one of them.  See pics of two examples: the VOR Z RWY 32 into Gulfport (KGPT) does not transfer properly (red block in FF FPL with text "3.KGPT.D32-Z"); the VOR Y RWY 32 at the same airport (KGPT) works fine (green block in FF FPL with text "VTF: VOR Y RWY 32".  

It doesn't matter if you choose VTF or some other initial point.  It also doesn't matter if you create the flight plan in IFD or FF - although IFD -> FF will at least transfer (with the approach not working) but FF -> IFD will not transfer at all.

I have not found the error with any other type approach so far (obviously have not tested them all).  Here's a non-exhaustive list of some that I've tried and which ones worked (and which did not).

Can someone try some of these on their setup and let me know if they do or do not have the same issues?  I've reached out to Avidyne support and they say it's a ForeFlight or Jeppesen issue - ForeFlight is looking into it but nothing so far. 

My software revision is 10.2.4.1 and I'm using an IFD440 with IFD100 (FF is latest version; all Jep databases are the latest), if that makes any difference.

Thanks!

Thank you Steve!  And I believe you're onto something here.  Of the 20 non-DME approaches I looked at (meaning, the FAA classifies them in the title section as just "VOR" not "VOR/DME") here's the stats:

DME Required: 9

Number of those which did not transfer: 8

DME not required: 11

Number of those which did not transfer: 0

The one exception was the VOR RWY 33 to KTBN, which says "DME or RADAR required"; this approach transferred fine.  The other eight just said "DME required" and none of them transferred.

So, it does seem that "DME Required" are the magic words (or, in this case, the bad words) that cause problems.

Hopefully you and Jeppesen can get that coding straight so all will transfer peacefully.  :)

Thanks again!

Steve,

Did you ever arrive at a fix for the approaches not being available on a flight plan that was transferred from Foreflight?

AviSteve wrote: I understand why it's occurring, but I haven't received feedback yet from Jeppesen as to why the approaches are coded that way.

I don't understand what the difference would be between loading the destination in the IFD as opposed to uploading it from Foreflight.  It's only when you load the flight plan from Foreflight that you lose the ability to add a procedure.  As soon as you dump the flight plan uploaded from Foreflight and do it manually, it works fine.  It's like the IFD doesn't recognize the destination in a route uploaded from Foreflight as a destination and thus no procedure is allowed.  What would be the difference?  That pretty much makes the ability to upload the flight plan pretty useless for IFR flying, assuming you will be shooting an approach at the destination.