RNAV Approach A320 fully managed
Thread Starter
Join Date: Dec 2008
Location: Birmingham
Age: 39
Posts: 181
Likes: 0
Received 0 Likes
on
0 Posts
RNAV Approach A320 fully managed
Bonjour guys.
having a question concerning the A320 and and a RNAV Approach fully managed.
In MRS for example you have some stepdown altitudes. Like after 5 NM descend from 5000 to 3000 etc... my question is: if i press the Approach button at the beginning of the Approach, the aircraft will fly in the final Approach mode. Will the System respect all my altitudes i put in in the window? like it descends to 3000 keeps it until i dial 2000?
coming from the MD 80 and we didnt have These Kind of System there.
Thanks!
having a question concerning the A320 and and a RNAV Approach fully managed.
In MRS for example you have some stepdown altitudes. Like after 5 NM descend from 5000 to 3000 etc... my question is: if i press the Approach button at the beginning of the Approach, the aircraft will fly in the final Approach mode. Will the System respect all my altitudes i put in in the window? like it descends to 3000 keeps it until i dial 2000?
coming from the MD 80 and we didnt have These Kind of System there.
Thanks!
Join Date: Mar 2004
Location: FL 391
Posts: 106
Likes: 0
Received 0 Likes
on
0 Posts
Hello and welcome to zeu Bus.
In FINAL APP mode the Bus flies the defaulted FMGS profile with constraints.
In my airline the SOP for fully managed NPA i.e. RNAV app calls for the defaulted FMGS restrictions not to be modified.
The only thing you have to do with the FCU is reset the ALT window to the missed approach altitude, once you are level at your platform altitude or at the profile intercept at latest ( FINAL APP announced on the FMA ).
A word of caution though and it had been part of a recently issued NOTAM in my airline, expect the bus to "nosedive" between 2 hard altitude constraints above the platform altitude and it did happen to me: Initial App Alt
( Platform Altitude ) at 2000 Ft, "intercepted the profile" in FINAL APP at 3000 Ft and the plane initiated a 1500 Fpm rate of descent to change 1000 Ft of Altitude as it was chasing the 2000 Ft constraint. Pretty unpleasant.
Bottom line, descend in V/S mode down to your platform altitude while complying with a specific initial descent profile then press APP once you are level at the platform altitude ( VDEV at 1 or 2 dots above ) then arm the APP and watch it doing an excellent job in the final approach.
I hope this helps
In FINAL APP mode the Bus flies the defaulted FMGS profile with constraints.
In my airline the SOP for fully managed NPA i.e. RNAV app calls for the defaulted FMGS restrictions not to be modified.
The only thing you have to do with the FCU is reset the ALT window to the missed approach altitude, once you are level at your platform altitude or at the profile intercept at latest ( FINAL APP announced on the FMA ).
A word of caution though and it had been part of a recently issued NOTAM in my airline, expect the bus to "nosedive" between 2 hard altitude constraints above the platform altitude and it did happen to me: Initial App Alt
( Platform Altitude ) at 2000 Ft, "intercepted the profile" in FINAL APP at 3000 Ft and the plane initiated a 1500 Fpm rate of descent to change 1000 Ft of Altitude as it was chasing the 2000 Ft constraint. Pretty unpleasant.
Bottom line, descend in V/S mode down to your platform altitude while complying with a specific initial descent profile then press APP once you are level at the platform altitude ( VDEV at 1 or 2 dots above ) then arm the APP and watch it doing an excellent job in the final approach.
I hope this helps
Join Date: Aug 2013
Location: PA
Age: 59
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
A word of caution though and it had been part of a recently issued NOTAM in my airline, expect the bus to "nosedive" between 2 hard altitude constraints above the platform altitude and it did happen to me: Initial App Alt
( Platform Altitude ) at 2000 Ft, "intercepted the profile" in FINAL APP at 3000 Ft and the plane initiated a 1500 Fpm rate of descent to change 1000 Ft of Altitude as it was chasing the 2000 Ft constraint. Pretty unpleasant.
( Platform Altitude ) at 2000 Ft, "intercepted the profile" in FINAL APP at 3000 Ft and the plane initiated a 1500 Fpm rate of descent to change 1000 Ft of Altitude as it was chasing the 2000 Ft constraint. Pretty unpleasant.
Makes one check to make sure there is the + sign in front of the altitude, and that seemed to solve the problem. 'at' to the system is when there is no plus or minus coded on the altitude.
Unfortunately, as far as I remember, you have no means to add a "+" or "-" when entering your own.
