Originally Posted by
mabg88
Thank you all for the replies.
I will take a pic of the actual data base for LOC 02 at VNKT since I'm going there in a few days. We stopped shooting the LOC there cuz the coding of the mcdu leaves you high on the approach flying a A333 with 1T bellow max landing weight (usually). Unlike the VOR which has the correct data in the mcdu to xcheck the chart alt and distance with the actual flight path of the aircraft. As mentioned in another post, we fly it NAV-FPA (No FLS installed) and xchecking the recommended altitudes of the chart while the mcdu has a different coding reduces your situation awareness. Any how, I just wanted to make sure that I was not missing something regarding the math. I'll post the pic of the coding once I have it for those who are interested.
The coding I have
GURAS /+11500
C022
º 5NM
CL02/+9300
C022
º TRK022º 3-5.3º FF02/+9000
C022
º 1-5.3º LOC11/+8420
C022
º 3-5.3º 75LOC/+6720
C022
º 2-5.3º 55LOC/+5590
C022
º 1-5.3º 45LOC/+5280
C022
º 2-5.3º KTM/4750
This corresponds to the charted altitudes. Linear regression through the altitude/distance table on the Jepp chart works out that they used 5.21 degrees.
That to me looks like the coding inside 55LOC is wrong, should be
-3.0º, looked at a machine with xLS, the approach is not in the data base.
This time of year its ISA+25 or more, so your true altitude at the FAF is more like 9500ft despite it indicating 9000ft on the altimeter, the non xLS machines are not temperature compensated. Something like FPA -5.9 will need to be flown to meet the profile. This should be flown in LOC-FPA.