Here come Foreflight's enhanced approach charts

A thought…

Which approach? Hete’s one local to me. Were you in the grey “not to scale” area when your airplane disappeared? Did it reappear when you returned to the georeferenced portion? That would be expected.

View attachment 143064
I think you have the GP profile here...I was on FF.
We were shooting the GPS 9 into KWAY, traveling in from the east.

Was the course reversal in your flight plan?
It was loaded both in the 650 in the plane, and is automatically charted in FF (the two were bluetooth connected).
 
I think you have the GP profile here...I was on FF.
We were shooting the GPS 9 into KWAY, traveling in from the east.


It was loaded both in the 650 in the plane, and is automatically charted in FF (the two were bluetooth connected).
Sorry. Yes, I was thinking GP.
 
  • Like
Reactions: SLB
I think you have the GP profile here...I was on FF.
We were shooting the GPS 9 into KWAY, traveling in from the east.
I didn't do your approach but if this is what you saw, I think it's normal. If it's something different, dunno.

If you set up the approach in FF with ZUNKO as the IAF and go to the APR Profile view, you will see that it doesn't go outbound further than ZUNKO. You can slide the Profile view to see a little more, but but less than 5 miles further. IOW, when you fly the course reversal, you are flying beyond the limits of the APR profile, so you don't see it. When you come back in range, it reappears.
 
Last edited:
I didn't do your approach but if this is what you saw, I think it's normal. If it's something different, dunno.

If you set up the approach in FF with ZUNKO as the IAF and go to the APR Profile view, you will see that it doesn't go outbound further than ZUNKO. You can slide the Profile view to see a little more, but but less than 5 miles further. IOW, when you fly the course reversal, you are flying beyond the limits of the APR profile, so you don't see it. When you come back in range, it reappears.
That makes sense. I tried 2 more today, a GPS at 2G9 (with a PT) and the ILS (vectors) at KJST. Tried using an IAP and Vectors to final setting on each approach and got no icon on profile. It did finally appear during the ILS, but not until we were 4 nm from the runway.
 

Attachments

  • IMG_0015.jpeg
    IMG_0015.jpeg
    683.1 KB · Views: 34
  • IMG_0017.png
    IMG_0017.png
    3.2 MB · Views: 35
  • IMG_0016.jpeg
    IMG_0016.jpeg
    744.8 KB · Views: 31
  • IMG_0018.jpeg
    IMG_0018.jpeg
    748.3 KB · Views: 35
From what I read earlier in the thread, today is supposed to be the day this is released. But I see nothing different from when I flew last week. Is there something I need to do to enable this feature? Or do I just need to wait a few hours?
 
From what I read earlier in the thread, today is supposed to be the day this is released. But I see nothing different from when I flew last week. Is there something I need to do to enable this feature? Or do I just need to wait a few hours?
Typical FF update day is Wednesdays. I don't see anything about an early push. We also don't know if there are any remaining beta issues.

As you probably know, sometimes our iOS settings mean that we don't automatically get an update installed even if it's available, so I usually go to the appstore to get it if I heard of a new release.
 
My version is 17.6. Is there a more recent update? (There doesn't APPEAR to be, based on that the button in App Store says "Open" rather than "Get", but I've long ago stopped trusting anything Apple puts out, including App Store.)
 
Typical FF update day is Wednesdays. I don't see anything about an early push. We also don't know if there are any remaining beta issues.

As you probably know, sometimes our iOS settings mean that we don't automatically get an update installed even if it's available, so I usually go to the appstore to get it if I heard of a new release.
I got an updated Beta on Friday, but won't get to it until tomorrow. Hopefully the issues I saw will be resolved.
 
Hmm... I could swear I read somewhere that the target roll-out date was supposed to be July 27 (today). Now I can't find it. Foreflight's page says that Dynamics Procedures "is on short final, with a post-Oshkosh ETA"... :oops:
 
I got an updated Beta on Friday, but won't get to it until tomorrow. Hopefully the issues I saw will be resolved.
Got a chance to use it in a Redbird session Saturday (it's too damn hot to fly around here) and one I saw earlier seems to have been fixed.
 
  • Like
Reactions: SLB
Hmm... I could swear I read somewhere that the target roll-out date was supposed to be July 27 (today). Now I can't find it. Foreflight's page says that Dynamics Procedures "is on short final, with a post-Oshkosh ETA"... :oops:
You might have. No surprise they would want to roll it out sometime during OSH, but "supposed to be" doesn't mean "will be."
 
Hmm... I could swear I read somewhere that the target roll-out date was supposed to be July 27 (today). Now I can't find it. Foreflight's page says that Dynamics Procedures "is on short final, with a post-Oshkosh ETA"... :oops:
I would expect it'll be in version 17.7 (you can see what version you have in More->About). I don't yet see it on the app store.
 
Hmm... I could swear I read somewhere that the target roll-out date was supposed to be July 27 (today). Now I can't find it.
I think what you might have seen was: "...ForeFlight's Dynamic Procedures feature will be released after the EAA AirVenture Oshkosh show, which ends on July 27, 2025..."

It's not the actual release date, just that it is going to come out after OSH. And this Wednesday is the last Wednesday in July, so there's a good chance it will be release then.
 
I would expect it'll be in version 17.7 (you can see what version you have in More->About). I don't yet see it on the app store.
Kent, as I think I said, I have 17.6. So you're probably right - it'll likely be in 17.7, unless the rollout is delayed further.
 
I think what you might have seen was: "...ForeFlight's Dynamic Procedures feature will be released after the EAA AirVenture Oshkosh show, which ends on July 27, 2025..."
Maybe - but I don't think so. The problem is that I can't find the source now, so no way to tell. In any case, it's good to know that it's not something about my account or subscription level (I have "Foreflight Essentials"), that it's just not yet in any production release.
 
Maybe - but I don't think so. The problem is that I can't find the source now, so no way to tell. In any case, it's good to know that it's not something about my account or subscription level (I have "Foreflight Essentials"), that it's just not yet in any production release.
Subscription level doesn’t count right now. It’s going to be released at all subscription levels for a 3-month preview, then “Essentials” and above.
 
Subscription level doesn’t count right now. It’s going to be released at all subscription levels for a 3-month preview, then “Essentials” and above.
Yes, I know. I don't care about "come-on" promotional periods - I care about the pricing scheme after the promotion expires. Until I read that Essentials will include Dynamic Procedures, I wasn't sure whether this was something I wanted to even try out, since I have no intention of paying for the Premium version for a nice, but not really essential, bell or whistle.
 
That makes sense. I tried 2 more today, a GPS at 2G9 (with a PT) and the ILS (vectors) at KJST. Tried using an IAP and Vectors to final setting on each approach and got no icon on profile. It did finally appear during the ILS, but not until we were 4 nm from the runway.
I came across a similar situation. Looking at your screenshots, it the segment is not shown as magenta, so it appears to me that somewhere on the procedure, the sequencing of the active leg did not occur. In my case, I think it was during an HILPT. I reported it to ForeFlight.
 
Got a chance to use it in a Redbird session Saturday (it's too damn hot to fly around here) and one I saw earlier seems to have been fixed.
Still seeing the same problem in today’s flight.
 
I tried updating the app and it still just says Open instead of Update. That's as of noon today.
I got an update to 17.7.3 today about 3:00 (after my flight, unfortunately). Try again tomorrow I guess.
 
I wish the pilot could opt to remove unneeded notes (uncompensated Baro VNav systems, helicopter vis reductions, DME/DME RNP-0.3 NA, RNP Approach GPS and the WAAS Ch information) from the chart.

I wish the pilot could select to remove from the selections charts that do not apply to the crew/aircraft (NDB and Cat 1 and 2 ILS.

I wish FDC NOTAMs could be automatically populated to the charts preflight.

I wish NACO would quit putting ILS and LPV minimum data in a thinner row than approaches with higher minimums.
 
I wonder if FF is somewhat hamstrung by their relationship with Jeppesen which holds them back from getting too far into charting.

Edit: just saw that you basically say the same thing above..,
If you read the FAQs, Jeppesen is responsible for the latest product although you are not required to up grade to Jepp charts.
 
Sort of. Jepp is the data source for Foreflight. I don't see anything more than that.
Does Dynamic Procedures require a subscription to Jeppesen charts?

Dynamic Procedures is powered by Jeppesen data, a subscription to Jeppesen charts is not required to use Dynamic Procedures.

While they want to maintain the market value of the Jepp product, FF being hamstrung would not be an accurate description. More like GMC giving you a few more bells and whistles than Chevrolet on a pick up.
 
Last edited:
Just downloaded it. Anxiously going to fly on the sim.
 
I wish the pilot could opt to remove unneeded notes (uncompensated Baro VNav systems, helicopter vis reductions, DME/DME RNP-0.3 NA, RNP Approach GPS and the WAAS Ch information) from the chart.

I wish the pilot could select to remove from the selections charts that do not apply to the crew/aircraft (NDB and Cat 1 and 2 ILS.

I wish FDC NOTAMs could be automatically populated to the charts preflight.

I wish NACO would quit putting ILS and LPV minimum data in a thinner row than approaches with higher minimums.
Pretty much describes GarminPilot Smart Charts :)
 
I just tried this on 17.7.4 with X-Plane 11. It didn't work. The airplane representation moved smoothly along the plan view perfectly. However, the profile view did not depict the aircraft position or altitude properly. The position was stuck at the IAF and the altitude didn't change as the plane followed the glideslope.

I like the sidebar. It depicts the essential information like GP, but it is a bit ragged. What is nice and unique to FF is the view of the approach and short final.

OTOH, I have flow the same approach with GP and the function was impeccable. I still love FF, but if this is prologue, we need .5 release.
 
Does Dynamic Procedures require a subscription to Jeppesen charts?

Dynamic Procedures is powered by Jeppesen data, a subscription to Jeppesen charts is not required to use Dynamic Procedures.
Right. They use Jepp data rather than Garmin data.
 
Downloaded the update last night. First approach I loaded with this new feature was KDHN ILS 32 with IVGIF as the IAF (DME ARC). Glide slope intercept is 2200'. Nowhere in the briefing strip, stepdown guidance, profile view or augmented procedure shown on the approach plate is this altitude shown. Instead, 2167', the glide slope altitude at the LOC FAF, is shown. Seems an error or at least an oversight if trying to use this new feature to brief/shoot an approach. I looked at several other ILS approaches that have differing altitudes published for GS intercept vs GS altitude at the non-precision approach FAF. All the ones I looked at had the same error. I sent ForeFlight an email. Haven't heard back yet.
 
Downloaded the update last night. First approach I loaded with this new feature was KDHN ILS 32 with IVGIF as the IAF (DME ARC). Glide slope intercept is 2200'. Nowhere in the briefing strip, stepdown guidance, profile view or augmented procedure shown on the approach plate is this altitude shown. Instead, 2167', the glide slope altitude at the LOC FAF, is shown. Seems an error or at least an oversight if trying to use this new feature to brief/shoot an approach. I looked at several other ILS approaches that have differing altitudes published for GS intercept vs GS altitude at the non-precision approach FAF. All the ones I looked at had the same error. I sent ForeFlight an email. Haven't heard back yet.
They give the product to all the subscribers free so you guys can proof test it for them. Then when you have performed your free evaluation and the product is tweaked, you have to upgrade to get it.
 
They give the product to all the subscribers free so you guys can proof test it for them. Then when you have performed your free evaluation and the product is tweaked, you have to upgrade to get it.
:rolleyes::rolleyes::rolleyes:

Dude... ForeFlight has a sizable testing team. I'm on it, as are some other PoAers. They've been working on this feature for a long time, and we've been testing it for months.

I'm sure there will be some things found now that it's rolling out to orders of magnitude more people, but ForeFlight certainly doesn't want the general community to "test it for them". That's a good way to make your customers angry and give your product a bad reputation.
 
Downloaded the update last night. First approach I loaded with this new feature was KDHN ILS 32 with IVGIF as the IAF (DME ARC). Glide slope intercept is 2200'. Nowhere in the briefing strip, stepdown guidance, profile view or augmented procedure shown on the approach plate is this altitude shown. Instead, 2167', the glide slope altitude at the LOC FAF, is shown. Seems an error or at least an oversight if trying to use this new feature to brief/shoot an approach. I looked at several other ILS approaches that have differing altitudes published for GS intercept vs GS altitude at the non-precision approach FAF. All the ones I looked at had the same error. I sent ForeFlight an email. Haven't heard back yet.
It's a feature not a bug ;) When you flew the approach, you may have noticed that you captured the glideslope at 2600; no need to descend to 2200. So the relevant altitude for that leg is the 2167 confirmation altitude. The LOC-only version has the 2200 stepdown.

I'm fine with it, but I mentioned to FF that they are likely to get some negative feedback from the dive and drivers out there for what amounts to choosing a technique rather than remaining true to the source document.
 
FF has a Dynamic Procedures webinar today at noon central.

 
Back
Top