PPRuNe Forums - View Single Post - A320 MCDU approach abbreviations
View Single Post
Old 7th October 2007 | 13:35
  #5 (permalink)  
laic
 
Joined: Mar 2007
Posts: 37
Likes: 0
From: youguessit
D as in database?

It's in case of a (NPA) non-precision approach using RNAV. So in your case, it has to be RNAV VOR 34 approach to have this kind of coding. Right?
I mentioned that D could stand for Database, because for instance if you had FMGS failure(s), you would have to refer to your VOR 34 approach plate which could have for instance a higher MDA, using the good old VOR rose technique.
RNAV approach can be performed, provided:
The approach stored in the navigation Database has been validated, and is approved by the operator.
The final approach (FAF to runway or MAP) as extracted from the navigation Database and inserted in the F-Plan including altitude constraints, is not revised by the crew.
The approach trajectory is laterally intercepted before the FAF, or equivalent waypoint in the FM F-PLN, so that the aircraft is correctly established on the final course before starting the descent.
Mind you, D in this case could mean a DME related waypoint, but what I stated above is correct regarding the use of RNAV.
Maybe a LOC only approach would have a different coding. May be not if the waypoints are DME related.
I do not fly the airplane anymore so I cannot verify any of the above. Airbus issued an FCOM bulletin regarding this coding some time ago. I don't have it anymore unfortunately.
Let me know.

Last edited by laic; 7th October 2007 at 14:33.
laic is offline  
Reply