Originally Posted by
CaptainMongo
Hello Vilas,
This is a good thread, you have authored several very good posts.
At our company we do not arm APPR until with in 100' of the FAF altitude. "Once the aircraft is established in NAV or LOC and within 100 feet of the FAF altitude, the APPR button may be armed ...."
This has been explained to us because of anomalies in coding contained in our FMGC. This requirement does not pertain to -V approaches because of different coding. (Which may be a North America issue)
As others have posted, if APPR is armed prior to being within 100' of FAF altitude the airplane does "unusual" things.
Regards,
Mongo.
(Lexxie747 your comments are noted as is your retirement. I've instructed on T-37's and flown F-16's in combat, plumbed the 727 and co-piloted the 777, was a Captain on the Jurassic 737 and Captain on the A-320. True professionals learn their aircraft as well as honing their craft - enjoy your retirement, it is well deserved.)
Dear Captain Mongo
My point of view is different.Arming within 100 ft of the FAF gives you a temporary solution, but I don't think this is the philosophy of RNAV apchs. If the plane does unusual things, just take over and report it. If we all do it like this , the manufacturers, apch designers, etc will not correct and investigate; they may think the system is working good.
When do you arm the APPR for an ILS? I've got unusual G/S and LOC captures as well, but I still arm the apch when on intercept hdg of final track, with loc deviation available and I keep monitoring.If things don't go as expected, I take over and I report