737-500 missing in Indonesia
td. Thank you; my thoughts relate to the need for meaningful instrument displays re thrust asymmetry, and crews prioritising these over thrust lever position.
Also, considering a range of scenarios, indications, analysis, and action:-
- AT clutch slip could involve two cues; instruments and TL. ~ AT malfunction; disengage AT.
- Engine/FCU fault; probably only instruments. ~ Engine malfunction; review other engine instruments and related systems.
Presumably modern FADEC controlled engines have the capability for cross monitoring and alerting displays; e.g. similar to air data instruments ‘disagree’.
Are there any aircraft which have such a system?
Associated refs;
https://www.faa.gov/aircraft/air_cer...ne_psm_icr.pdf
“Although the vast majority of propulsion system malfunctions are recognized and handled appropriately, there is sufficient evidence to suggest that many pilots have difficulty identifying certain propulsion system malfunctions and reacting appropriately”.
https://www.aia-aerospace.org/wp-con...ITT_Report.pdf
Powerplant Indications Task Team Report;
‘… opportunities for safety improvements’, para 1.4 onwards.
Investigation of (Automatic) Asymmetric Thrust Detection
https://core.ac.uk/download/pdf/42702866.pdf
Also, considering a range of scenarios, indications, analysis, and action:-
- AT clutch slip could involve two cues; instruments and TL. ~ AT malfunction; disengage AT.
- Engine/FCU fault; probably only instruments. ~ Engine malfunction; review other engine instruments and related systems.
Presumably modern FADEC controlled engines have the capability for cross monitoring and alerting displays; e.g. similar to air data instruments ‘disagree’.
Are there any aircraft which have such a system?
Associated refs;
https://www.faa.gov/aircraft/air_cer...ne_psm_icr.pdf
“Although the vast majority of propulsion system malfunctions are recognized and handled appropriately, there is sufficient evidence to suggest that many pilots have difficulty identifying certain propulsion system malfunctions and reacting appropriately”.
https://www.aia-aerospace.org/wp-con...ITT_Report.pdf
Powerplant Indications Task Team Report;
‘… opportunities for safety improvements’, para 1.4 onwards.
Investigation of (Automatic) Asymmetric Thrust Detection
https://core.ac.uk/download/pdf/42702866.pdf
Only half a speed-brake
Further to td's explanation, there's a controlling circuitry in the Classic called PMC, I seem to recall. It's job is to fine-tune everything controlling the N1s and if operational the engines behave very gracefully.
BananaJoe somewhere near?
I.e. most likely in your scenario the PMC would feed inputs to A/T for matching N1 first, resulting in the stagger described and not the other way around. The governing input is the N1, not throttle angle.
BananaJoe somewhere near?
I.e. most likely in your scenario the PMC would feed inputs to A/T for matching N1 first, resulting in the stagger described and not the other way around. The governing input is the N1, not throttle angle.
safetypee
It was found that flight crew would often start troubleshooting things like low oil pressure or an IDG dropping offline when the actual problem was the engine had quit. So starting with the 747-400, Boeing implemented an "ENG X FAIL" message on EICAS - the logic was pretty basic (N2/N3 well below idle) - Similar ENG FAIL logic was included in the 767 EICAS but for reasons I never understood it was never turned on...
777 took it a step further - partly due to the implementation of TAC (Thrust Asymmetry Compensation) which could hide a thrust asymmetry caused yaw, they implemented L/R ENG THRUST which indicated an engine was producing less than commanded thrust (by at least 10% IIRC) and not recovering. I think the ENG THRUST logic was in the FADEC but I wouldn't swear to it. The 777 also has L/R ENG FAIL with somewhat more sophisticated logic than the 747-400.
The 787 and 747-8 have the ENG FAIL and ENG THRUST messages.
It was found that flight crew would often start troubleshooting things like low oil pressure or an IDG dropping offline when the actual problem was the engine had quit. So starting with the 747-400, Boeing implemented an "ENG X FAIL" message on EICAS - the logic was pretty basic (N2/N3 well below idle) - Similar ENG FAIL logic was included in the 767 EICAS but for reasons I never understood it was never turned on...
777 took it a step further - partly due to the implementation of TAC (Thrust Asymmetry Compensation) which could hide a thrust asymmetry caused yaw, they implemented L/R ENG THRUST which indicated an engine was producing less than commanded thrust (by at least 10% IIRC) and not recovering. I think the ENG THRUST logic was in the FADEC but I wouldn't swear to it. The 777 also has L/R ENG FAIL with somewhat more sophisticated logic than the 747-400.
The 787 and 747-8 have the ENG FAIL and ENG THRUST messages.
There's always the case where the engine doesn't annunciated a failure condition at high altitude or at low power during approach, yet over time the drag asymmetry can lead to an unstable aircraft mode (pitch and/or roll) which can manifest itself and confuse the crew if they fail to note such changes.
So just how far to you go with engine controls or instruments, either in design or annunciating to the crew?
So just how far to you go with engine controls or instruments, either in design or annunciating to the crew?
Join Date: Aug 2002
Location: Castletown
Posts: 241
Likes: 0
Received 0 Likes
on
0 Posts
That is a great question.
Case in point and a very subtle failure that happened to a friend. When leaving FL360, on descent, the thrust levers were at idle and the number 2 engine flamed out. At that time the only caution that the crew saw was the engine generator message indicating an "off line" condition.
If the descent had an intermediate level off, then that would have been interesting.
Case in point and a very subtle failure that happened to a friend. When leaving FL360, on descent, the thrust levers were at idle and the number 2 engine flamed out. At that time the only caution that the crew saw was the engine generator message indicating an "off line" condition.
If the descent had an intermediate level off, then that would have been interesting.
I’m not a pilot (my Dad was) but, if I’m flying an aircraft w misbehaving auto-throttles, would I not at minimum 1) watch the throttles closely during climb and/or 2) have my hand on the throttle quad at all times such that even if I was looking elsewhere I would feel the split?
I know it’s easy for a non-pilot like me to say, but....any comments?
I know it’s easy for a non-pilot like me to say, but....any comments?
Some pilots say that non moving Airbus FBW thrust levers are a bad thing, yet there have been several accidents in recent years with Boeing thrust levers that didn't move when they should have, but the situation was not noticed by the pilots.
The Airbus system requires the pilots to look at the N1/EPR gauges every instrument scan to confirm what the engines are doing. This is a very GOOD thing, and avoids getting caught out.
Join Date: Aug 2000
Posts: 1,501
Likes: 0
Received 0 Likes
on
0 Posts
You are of course required to monitor the engine instruments in a Boeing as well, thrust lever movement is not the primary engine indication. They add an element to the monitoring. It is very easy to get lazy when it comes to engine monitoring in an Airbus.
Yes, my point was that several recent Boeing crashes have been a direct result of pilots NOT looking at the engine instruments, but assuming - from the proxy of the thrust lever position(s) - what the engines were doing. But even then, the wrong thrust lever position - for example an asymmetry - has not been noticed. In particular, a common theme seems to be not noticing when the thrust lever(s) don't move, but should have moved.
The danger is that some use the moving thrust levers as their engine monitoring and get out of the vital habit of checking the engine instruments in every scan,
In Airbus FBW, pilots must look at the engine instruments to know what the engines have been commanded to do and are doing, (apart from large accelerations felt through the body).
The danger is that some use the moving thrust levers as their engine monitoring and get out of the vital habit of checking the engine instruments in every scan,
In Airbus FBW, pilots must look at the engine instruments to know what the engines have been commanded to do and are doing, (apart from large accelerations felt through the body).
Join Date: Apr 2010
Location: IRS NAV ONLY
Posts: 1,230
Likes: 0
Received 0 Likes
on
0 Posts
Are you trying to sell the lack of tactile feedback in Airbus FBW design (both thrust levers and sidestick) as positive?
It's not. The fact that you have to stare inside the flightdeck to monitor what automation is doing, instead of being able to look outside and feel with hands on controls that the autopilot is starting to do something silly, isn't a positive in my book.
It's not. The fact that you have to stare inside the flightdeck to monitor what automation is doing, instead of being able to look outside and feel with hands on controls that the autopilot is starting to do something silly, isn't a positive in my book.
Join Date: Aug 2000
Posts: 1,501
Likes: 0
Received 0 Likes
on
0 Posts
The danger in an Airbus is that engine instruments are not included in the scan. You can use BIG letters as much as you want, but movable levers are not dangerous.
If thrust is assymetric, thrust levers split, aircraft in a yaw/roll and the pilots fail to notice, they are not doing their job.
If thrust is assymetric, thrust levers split, aircraft in a yaw/roll and the pilots fail to notice, they are not doing their job.
It's two different planes with different operating philosophies... Stop arguing whether one of them is better. In either of them you should be trained for and know about the traps you can fall into, and in either of them you are not doing your job properly if a major thrust asymmetry goes unnoticed. Whether you don't pay attention to thrust levers that have moved or to engine instruments, you are not doing your job. If anything, autothrust is the danger as it brings out the lazy part in any pilot. Bring back manual thrust only, wohoo! /sarcasm
Join Date: Aug 2011
Location: Australia
Posts: 423
Likes: 0
Received 0 Likes
on
0 Posts
Following through the history of this crash up to present date, it looks increasingly like the scene in the 737 simulator described by Centaurus at Post 309 date 18 January 2021, is uncomfortably close to that of what really happened.
Join Date: May 2000
Location: Seattle
Posts: 3,195
Likes: 0
Received 0 Likes
on
0 Posts
ok, if it is mandatory to scroll back your logs for maintenance actions, how far do you have to scroll back? One flight, two flights, a week?
What I am triggered on is that you call others “derelict in their duties” for something that is good practice but not required.
What I am triggered on is that you call others “derelict in their duties” for something that is good practice but not required.
It is also covered under FAR 91.103 in the US:
§91.103 Preflight action.
Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that
flight.
Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that
flight.
Intruder
"Recent maintenance history and recurrent maintenance problems certainly are relevant to the flight!"
So how many previous sectors' log entries should a crew expect to have to trawl through when accepting an aircraft ?
"Recent maintenance history and recurrent maintenance problems certainly are relevant to the flight!"
So how many previous sectors' log entries should a crew expect to have to trawl through when accepting an aircraft ?
Join Date: Feb 2008
Location: victoria bc
Age: 82
Posts: 77
Likes: 0
Received 0 Likes
on
0 Posts
You nailed it Intrance. The convenience of autothrottle may have tipped the balance in the wrong direction where control of the airplane is concerned. Too much automation has disengaged the pilot.
Only half a speed-brake
DaveReidUK
That's an easy one: About last 3 flying days' worth, or back to the previous WY check. When a new logbook is started the old one remains on-board, officially.
The real dilemma behind your question is understood, but it's one of those few that fortunately do not need a lawyer-proofed solution. Working the job does it.
That's an easy one: About last 3 flying days' worth, or back to the previous WY check. When a new logbook is started the old one remains on-board, officially.
The real dilemma behind your question is understood, but it's one of those few that fortunately do not need a lawyer-proofed solution. Working the job does it.
Last edited by FlightDetent; 21st Apr 2021 at 19:58.
"Mildly" Eccentric Stardriver
fatbus
Things may have changed, but way back, it wasn't acceptable to have an open defect. If it couldn't be cleared, it went as an ADD "Acceptable Deferred Defect", which was in a separate section of the log. If not acceptable, the aircraft wasn't airworthy.
It could be aa simple as "Recurring defect not detectable on the ground. Crews are requested to monitor", but it would be there; right in your face.
Things may have changed, but way back, it wasn't acceptable to have an open defect. If it couldn't be cleared, it went as an ADD "Acceptable Deferred Defect", which was in a separate section of the log. If not acceptable, the aircraft wasn't airworthy.
It could be aa simple as "Recurring defect not detectable on the ground. Crews are requested to monitor", but it would be there; right in your face.