Go Back  PPRuNe Forums > Flight Deck Forums > Tech Log
Reload this Page >

Accidents caused by failure of GA autothrottle modes

Wikiposts
Search
Tech Log The very best in practical technical discussion on the web

Accidents caused by failure of GA autothrottle modes

Thread Tools
 
Search this Thread
 
Old 27th Dec 2009, 12:35
  #1 (permalink)  
Thread Starter
 
Join Date: Apr 2005
Location: Australia
Posts: 1,414
Likes: 0
Received 0 Likes on 0 Posts
Accidents caused by failure of GA autothrottle modes

The recently published NTSB report on the One-To-Go MD80 accident at Phuket, mentions the crew failed to push open the thrust levers as part of the go-around procedure. The aircraft subsequently failed to climb. They apparently relied on the GA mode to actuate the thrust levers while failing to see it was not correctly armed.

The report stated the autothrottles move up at eight degrees of angle per second; meaning it takes the throttles 5.2 seconds to reach full thrust position. It further stated the engines on the MD80 are capable of accelerating to go-around thrust faster than the rate given by the autothrottles.

Does anyone have the equivalent numbers above for the CFM 56 engines of Boeing 737's? Ie How many degrees of thrust lever movement per second on GA with autothrottles?

In the simulator, we often see pilots pressing the TOGA button to initiate an autothrottle go around and if for some reason TOGA did not work, the element of surprise sometimes sees the pilot fail to advance the thrust levers manually for a critical few seconds. Like the crashed MD80 they failed to advance the throttles manually when TOGA did not operate and instead relied implicitly on the autothrottles to actuate. Having pitched the aircraft manually to a go-around climb body angle there can be an alarming speed decay before the pilot realises something is amiss and he gets around to manually shoving the throttles to max thrust.

Is there any technical reason why in a go-around the pilot should not first manually open the throttles rapidly to go-around thrust and once there, then press TOGA? After all, this only takes a couple of seconds and is a good insurance against TOGA failure or pilot error. It would have prevented the MD 80 accident mentioned earlier. With a planned rate of rotation of three degrees per second on the way to the go-around attitude of around 15 degrees nose up, the slight delay involved before the TOGA button is actuated and sets the the flight director to GA mode, should not prove an unsurmountable problem.

By the time the thrust levers had manually reached go-around thrust lever angle, the nose up attitude would not yet have reached anywhere near 15 degrees.
A37575 is offline  
Old 27th Dec 2009, 12:45
  #2 (permalink)  
 
Join Date: Jun 2003
Location: UK
Posts: 3,053
Likes: 0
Received 29 Likes on 14 Posts
Could it be because you would then have one procedure for hand flown G/A and you would have to have another for a G/A off a fully coupled approach? I'm not sure your method would have the right consequences at 50' on a low vis approach.

I much prefer the Airbus solution where you just whack the levers forward as fast as you like. If you have flaps out then as soon as the levers hit the end stop then TOGA mode is engaged.
HundredPercentPlease is offline  
Old 27th Dec 2009, 14:08
  #3 (permalink)  
 
Join Date: Jun 2001
Location: UTC +8
Posts: 2,626
Likes: 0
Received 0 Likes on 0 Posts
The accident is not caused by failure of A/T TOGA mode; it's caused by the PF not shoving the thrust levers forward when the A/T didn't or was too slow. Manual inputs are elementary and instinctive anytime the automatics are not performing as they should. During any approach, in any airplane, irrespective of A/T operation, whether autoland or not, the PF must always keep one hand on the thrust levers.
GlueBall is offline  
Old 29th Dec 2009, 08:15
  #4 (permalink)  
Thread Starter
 
Join Date: Apr 2005
Location: Australia
Posts: 1,414
Likes: 0
Received 0 Likes on 0 Posts
so he can keep the PITCH moderated to SEE the THREAT ahead),
Threat? What "threat?" A normal go-around is not a threat. Or has this whole Threat and Error management gimmick got pilots shooting at shadows?
A37575 is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.