Recommended Posts

There is (what can only be described as) a software bug in the Thrust Reference setting software in the 777. While this bug manifests itself in several situation on normal and non-normal operations, it manifests significantly with flight safety implications during VNAV engine-out approaches.

I discovered this issue back in the late 90′s when I was working in the simulator. I kept noticing it and writing it up for the sim engineers to fix. They would report back that they’d fixed it (or couldn’t understand what was wrong). Another instructor would review the fix and misunderstand what the original report was about and clear the fault. Then, later, I’d see it again and report it – and round and round we went.

Eventually the sim engineers hunted me down and got me to show them exactly what the problem was – which I did. We all referred to the FCOM, agreed that it was not working, but then one of the engineers asked me, “what does the aircraft do?”. “Ummmm“, I said… so I went and checked. Lo and Behold – the sim wasn’t the problem, the aircraft was. Oops.

I brought this to the attention of several levels of the training and technical management, without much interest, so I circulated an e-mail amongst instructors and ensure my students were aware of it.

In early 2000′s, a friend of mine at Cathay approached me about it (someone sent him the email) and they chased it down with CAE/Boeing as well (to no avail as far as I can work out – the anomaly is still there). Then about 3 years ago a pilot upgrading to Command at Emirates was commencing an engine out NPA (Non Precision Approach) into a high altitude airport in Africa and managed to stall the aircraft because of this (actually, I would suggest there was some SA involved as well). This kicked off another flurry of investigation – including approaching me for details (which amused me greatly since I’d left the airline and come to V). But again, nothing much seems to have come from that because the anomaly is still there …

Boeing’s airplane design is such that GA (Go Around) is set as the thrust limit (displayed above the N1 indication) any time the flaps are extended (FCOM 04.20.16 refers) or the glide slope is captured. One assumes that Boeing’s intent was that GA should remain the thrust limit to either Landing or the Go-Around in order to provide maximum available thrust for manoeuvring while configured for landing.

However when VNAV is engagedafter flaps have been extended, the Thrust Limit is reset to CRZ. Irrespective of the demands of the situation (weight, density altitude, configuration, selected airspeed, etc). By design, the auto throttle cannot command more than this selected Thrust Limit: CRZ.

In most normal ops situations this reduced thrust limit is adequate to preserve airspeed irrespective of configuration (engine out, gear, flap) – particularly in the 777-300ER. But 777′s with less thrust such as the -300/-200 – or in performance limiting situations such as weight in excess of MALW, high density altitudes, etc. – insufficient thrust can exist to maintain airspeed/altitude.

Prior to a low speed excursion, stick shaker activation and AP stall protection, the problem can be corrected by:

Selecting GA through the FMC Thrust Lim page;

Pressing the CLB/CON switch (only CON* thrust limit will be selected, not GA);

* While CON thrust should be enough to maintain speed at maximum landing weight, higher weights may require even more thrust.

Scenario Description

Assume a 777 at maximum landing weight, approaching the final approach fix (FAF) at platform altitude for an engine out NPA. The crew intend to use VNAV for the approach but have manoeuvred to the initial approach altitude using Basic Modes (FLCH/VS). Configured correctly at Flap 5/Flap 5 speed, thrust reference will most likely be GA – set automatically when the Flaps were extended.

At 3 nm from the FAF, Gear Down/Flaps 20/Flap 20 speed is selected. Thrust levers retard to slow the aircraft to Flaps 20 speed. Meanwhile the PF will set the minima in the altitude select window on the MCP, check track, engage VNAV PATH and speed intervene.

Speed Protection? At minimum manoeuvring speed, low speed protection would normally kick in (minimum AFDS speed or eventually auto throttle wakeup), but in this case this protective feature is limited by the CRZ thrust limit setting. The only low speed protection (through the autopilot) that will function is stall protection – as the aircraft approaches stick shaker speed, it will pitch forward and descend with failed FMA AFDS mode indications.

Prior to a low speed excursion and stick shaker activation, the problem can be corrected by selecting GA through the FMC Thrust Lim page or pressing the CLB/CON switch (CON thrust limit only will be selected) – or simply pushing the thrust levers forward – whether disconnecting the A/THR first or not. CON thrust should be enough to maintain speed at maximum landing weight. Higher weights may require more thrust.

Additionally:

On all approaches (after flap selection), FLCH may set CLB/CON, but glide slope intercept will reset to TO/GA.

This anomaly does not impact on other NNM procedures (such as Windshear and GPWS). These recalls require either TO/GA Switch activation and/or manual thrust.

About Ken

Ken has flown numerous Boeing and Airbus types. He is currently a Boeing 777 Check and Training Captain with a major international airline serving as the Fleet Standards Manager (and formerly as the Training Manager). Connect with Ken onTwitter.

AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

Donation Goals

AVSIM's 2018 Fundraising Goal

Donate to our annual general fund. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.