Hi,
using the Navigraph database with JeeHell A320 I can see an issue with the altitudes at the Final Descent Point of many approaches shown as “at or above” instead of “at” (exactly).
For example EDDF RNP Y RWY 07L, Navigraph chart correctly shows an altitude of 5000´ for DF450. The procedure loaded into JeeHell MCDU for DF450 shows “+5000” as altitude constraint, what likely has in consequence the aircraft is still to high when flying in managed mode until DF450.
Editing navrecord.dat I find:
PF|EDDF|ED|R07LY|R||20|DF450|ED|PC|E F||||TF||| ||||66.0|4.1|+|5000|||||EDDF|||PA|1|W|S|A|
Shouldn´t there be a “@” (or nothing?) in the field before 5000 to have it as an "at 5000´ " constraint?
As said, it is an issue not only of this approach, but of several procedures around the world, so it is impossible to correct all by hand. My only workaraound until now is to set all those values to “at” instead of “+” in the MCDU before reaching the approach, but that gets little bit boring and will not match with the real procedures.
I wonder, if that can be an issue with JeeHell only?
Hi,
Thank you very much for your report. I will check it, but you are absolutely right about your expectations. I will keep you informed here about any results!
Thank you again & enjoy a nice Sunday,
Richard
This topic was automatically closed after 7 days. New replies are no longer allowed.