Hi,it seems that there is a bug in the calculation of the vertical angle between the FAF (Final Approach Fix) and the RWY. The profile diamond is always indicating that the A/C is below the calculated path. (when comparing to an ILS G/S) On the 747 and the 737 this works more or less flawlessly.What parameters does the MD-11 use to calculate this path?Can you have a look on this for the next service pack?Jan-Paul Schuchna

Your PROF is limited to 2000 ft, which is probably your intitial go around altitude but this is why you are below the diamond. If you flew a non precision approach and set the ALT to MDA the diamond should track the path down to that level.

Your PROF is limited to 2000 ft, which is probably your intitial go around altitude but this is why you are below the diamond. If you flew a non precision approach and set the ALT to MDA the diamond should track the path down to that level.

That didn't make any difference, it was still too high. I have also tried an RNAV Approach with ALT set to Min. Prof, here it also was something like 150ft to 200ft to high. Jan-Paul Schuchna

again, Check Airman and myself have brought this matter up with no positive response if it is a bug or not. It probably isnt a bug, in that if you look on some Jeppesen charts, you will see that vertical path line of the Minimum Descent Altitude in the profile box on the chart, doesnt continue down to the runway but levels off and goes to the runway threshold or Missed approach point and then the missed approach procedure begins. What we have noticed is that when you select a non-ILS approach and you enter the MIN PROF altitude in the prompt, the runway elevation on the flightplan page changes to a soft constraint equal to the MIN PROF you entered which is why the plane will not descend after passing the FAF: so it could probably be a bug or a design feature to incorporate the above mentioned point. but there are only 2 workarounds.1. Find out the descent angle and descend in FPA mode.2. Cheat and set the MIN PROF to 200ft above the runway elevation (i think 200 AGL is the minimum entry it will accept)

again, Check Airman and myself have brought this matter up with no positive response if it is a bug or not. It probably isnt a bug, in that if you look on some Jeppesen charts, you will see that vertical path line of the Minimum Descent Altitude in the profile box on the chart, doesnt continue down to the runway but levels off and goes to the runway threshold or Missed approach point and then the missed approach procedure begins. What we have noticed is that when you select a non-ILS approach and you enter the MIN PROF altitude in the prompt, the runway elevation on the flightplan page changes to a soft constraint equal to the MIN PROF you entered which is why the plane will not descend after passing the FAF: so it could probably be a bug or a design feature to incorporate the above mentioned point. but there are only 2 workarounds.1. Find out the descent angle and descend in FPA mode.2. Cheat and set the MIN PROF to 200ft above the runway elevation (i think 200 AGL is the minimum entry it will accept)

The second solution didn't work either, the FMS states always "Entry out of range". But, lets say the airport is at 1300 MSL, the FMS would accept an value of 1500. Maybe you have to enter the MSL here an not AGL? The Manual also states the 200ft AGL. But anyway this also doesn't change anything with the wrong calculated path. Jan-Paul Schuchna