787 "unrealistic airspeed" AD
Thread Starter
Join Date: Sep 2014
Location: Canada
Posts: 1,257
Likes: 0
Received 0 Likes
on
0 Posts
787 "unrealistic airspeed" AD
Boeing, FAA warn 787 pilots of bad airspeed data
More from:
https://www.flightglobal.com/news/ar...d-data-423735/
Boeing 787 pilots are being warned not to make sudden control inputs in response to a “sudden, unrealistic” drop in airspeed shown on cockpit displays.
The US Federal Aviation Administration (FAA) will adopt an airworthiness directive on 1 April requiring 787-8 and 787-9 operators to update the flight manual with the warning message.
The FAA accelerated the release of the airworthiness directive, bypassing the normal rulemaking process to make operators adopt the change as quickly as possible.
Boeing made an identical recommendation to 787 operators on 4 March, which the FAA directive will make mandatory.
The fleet has made three reports of displayed airspeed plunging significantly below actual airspeed, the FAA says. In each case, the 787 was flying in conditions involving significant water ingestion and possibly icing of two of the three pitot tubes feeding speed and altitude information to the air data system. ...
In one case, the pilot reacted to the inaccurate data by commanding a “significant” nose-down dive, over-riding the auto-pilot in the process. ...
The US Federal Aviation Administration (FAA) will adopt an airworthiness directive on 1 April requiring 787-8 and 787-9 operators to update the flight manual with the warning message.
The FAA accelerated the release of the airworthiness directive, bypassing the normal rulemaking process to make operators adopt the change as quickly as possible.
Boeing made an identical recommendation to 787 operators on 4 March, which the FAA directive will make mandatory.
The fleet has made three reports of displayed airspeed plunging significantly below actual airspeed, the FAA says. In each case, the 787 was flying in conditions involving significant water ingestion and possibly icing of two of the three pitot tubes feeding speed and altitude information to the air data system. ...
In one case, the pilot reacted to the inaccurate data by commanding a “significant” nose-down dive, over-riding the auto-pilot in the process. ...
https://www.flightglobal.com/news/ar...d-data-423735/
Join Date: Jun 1996
Location: Check with Ops
Posts: 741
Likes: 0
Received 0 Likes
on
0 Posts
In one case, the pilot reacted to the inaccurate data by commanding a “significant” nose-down dive, over-riding the auto-pilot in the process. ...
No other indications of any wrong-doing, normal pitch attitude, normal thrust but the airspeed suddenly drops so let's just shove the nose down. Probably the same sort of person who sits there overriding the auto throttles and wanking the thrust levers back and forth for every knot of speed change in turbulence
Controversial, moi?
I thought the 787 had automatic switching to an AOA display in event of unreliable airspeed ?
If the ADRS and IRS calculated speeds disagree you get an 'UNRELIABLE AIRSPEED' EICAS and you DO NOT get automatic AOA airspeed display.
Now there's a great idea......NOT!
No other indications of any wrong-doing, normal pitch attitude, normal thrust but the airspeed suddenly drops so let's just shove the nose down. Probably the same sort of person who sits there overriding the auto throttles and wanking the thrust levers back and forth for every knot of speed change in turbulence
No other indications of any wrong-doing, normal pitch attitude, normal thrust but the airspeed suddenly drops so let's just shove the nose down. Probably the same sort of person who sits there overriding the auto throttles and wanking the thrust levers back and forth for every knot of speed change in turbulence
Join Date: Sep 1999
Location: United Kingdom
Posts: 929
Likes: 0
Received 0 Likes
on
0 Posts
Interesting in that I have seen a sudden loss of airspeed on a couple of occasions. If I hadn't pitched down immediately & got the airspeed increasing. Well you would be reading about it on here. Jet streams & surprise CAT are not uncommon so IMHO get the nose down so you know your airspeed will be increasing & then asses, confirm the situation & act appropriately. To ignor seems to be an odd thing to do.
Well I guess Boeing suspect pilots can no longer fly so will end up crashing anyway.
Well I guess Boeing suspect pilots can no longer fly so will end up crashing anyway.
Join Date: Mar 2001
Location: I wouldn't know.
Posts: 4,497
Likes: 0
Received 0 Likes
on
0 Posts
It sounds to me that some pilots need a bit more dual experience at the weekend on a single engine piston.
Pegase Driver
Join Date: May 1997
Location: Europe
Age: 73
Posts: 3,668
Likes: 0
Received 0 Likes
on
0 Posts
Well I guess Boeing suspect pilots can no longer fly
1980 Ziegler : " this aircraft cannot stall, even if the pilots wants to .." or " it can be flown by my concierge ( janitor) "
Welcome back in time.
Join Date: Sep 2013
Location: UK
Posts: 730
Likes: 0
Received 0 Likes
on
0 Posts
Why have manufacturers stopped having proper redundancy on the latest aircraft? Look at the 737, from Jurassic to NG, and the information on the primary flight displays or main panel all comes from completely different sources, be it independent gyros in the Jurrassic's FDs and independent pitot static systems, or with parallel but independent ADIRUs in the NG, with independent sources to each. The standby instruments are also completely independent. Look at the 777 and you have a single ADIRU supplying all main flight instruments, even the standby attitude not being truly independent of the main instruments, fed by the SAARU, which is the back up for the main instruments. How is it that the bigger, dearer and supposedly more advanced aircraft have less redundancy and less indication to pilots of which system is malfunctioning?
Join Date: Aug 2007
Location: between supple thighs
Posts: 243
Likes: 0
Received 0 Likes
on
0 Posts
For those of you that don't have access to the FCOM Bulletin.
There have been several events where the indicated airspeed shown to the pilots
dropped rapidly (within a few seconds) to below 50kts. These events are
suspected to have been caused by temporary blockage of multiple pitot tubes
when near weather systems with high moisture content. In all events, the
blockage cleared within several seconds. During some events, the FLIGHT
CONTROL MODE, AUTOPILOT DISC, and other messages were shown
(along with a flight control reversion to secondary mode). In one event, the PFD
automatically switched to AOA speed; and in another event, the AIRSPEED
UNRELIABLE message was shown. Depending on the duration and nature of
the pitot blockage, FLIGHT CONTROL MODE, NAV AIRDATA SYS, NAV
AIRSPEED DATA, AIRSPEED UNRELIABLE, AUTOPILOT DISC,
AIRSPEED LOW EICAS messages can show during similar events.While, in all these events, the air data system recovered and the fault detection
system provided alert level EICAS messages where expected, a possible flight
crew response to an initial sudden drop in indicated airspeed could be to apply
pitch inputs which may result in ‘G’ excursions. If the crew applies strong nose
down force to the yoke without disconnecting the autopilot, when the autopilot
disconnects (as a result of the manual force applied), a sudden nose down
command would be applied to the airplane. This nose down input could be
amplified by the low column forces being fed back to the pilot as a result of the
low airspeed being indicated.
As a result of the above events, Boeing is making improvements to the flight
control system and force feedback to mitigate the negative effect of large control
inputs in these scenarios, and is also making improvements to the EICAS Alert
logic related to air data faults. In addition, Boeing is continuing to investigate the
pitot blockage event rate to determine if any design improvements are warranted.
In response to concerns about possible negative crew reaction to an initial sudden
drop in airspeed, the FAA intends to issue an Airworthiness Directive to require
operators to incorporate a procedure into their AFM which instructs crews to
avoid abrupt control inputs in response to sudden unrealistic drops in indicated
airspeed. This procedure also reminds pilots that if manual flight is desired, the
autopilot should be disconnected prior to any manual flight control inputs.
There have been several events where the indicated airspeed shown to the pilots
dropped rapidly (within a few seconds) to below 50kts. These events are
suspected to have been caused by temporary blockage of multiple pitot tubes
when near weather systems with high moisture content. In all events, the
blockage cleared within several seconds. During some events, the FLIGHT
CONTROL MODE, AUTOPILOT DISC, and other messages were shown
(along with a flight control reversion to secondary mode). In one event, the PFD
automatically switched to AOA speed; and in another event, the AIRSPEED
UNRELIABLE message was shown. Depending on the duration and nature of
the pitot blockage, FLIGHT CONTROL MODE, NAV AIRDATA SYS, NAV
AIRSPEED DATA, AIRSPEED UNRELIABLE, AUTOPILOT DISC,
AIRSPEED LOW EICAS messages can show during similar events.While, in all these events, the air data system recovered and the fault detection
system provided alert level EICAS messages where expected, a possible flight
crew response to an initial sudden drop in indicated airspeed could be to apply
pitch inputs which may result in ‘G’ excursions. If the crew applies strong nose
down force to the yoke without disconnecting the autopilot, when the autopilot
disconnects (as a result of the manual force applied), a sudden nose down
command would be applied to the airplane. This nose down input could be
amplified by the low column forces being fed back to the pilot as a result of the
low airspeed being indicated.
As a result of the above events, Boeing is making improvements to the flight
control system and force feedback to mitigate the negative effect of large control
inputs in these scenarios, and is also making improvements to the EICAS Alert
logic related to air data faults. In addition, Boeing is continuing to investigate the
pitot blockage event rate to determine if any design improvements are warranted.
In response to concerns about possible negative crew reaction to an initial sudden
drop in airspeed, the FAA intends to issue an Airworthiness Directive to require
operators to incorporate a procedure into their AFM which instructs crews to
avoid abrupt control inputs in response to sudden unrealistic drops in indicated
airspeed. This procedure also reminds pilots that if manual flight is desired, the
autopilot should be disconnected prior to any manual flight control inputs.
Join Date: Aug 2007
Location: Utterly insignificant little blue-green planet, unregarded yellow sun, unfashionable end, western spiral arm, Milky Way
Age: 38
Posts: 276
Received 0 Likes
on
0 Posts
This procedure also reminds pilots that if manual flight is desired, the
autopilot should be disconnected prior to any manual flight control inputs.
autopilot should be disconnected prior to any manual flight control inputs.
Join Date: Feb 2004
Location: Australia
Posts: 1,307
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Aluminium shuffler
Look at the 777 and you have a single ADIRU supplying all main flight instruments
If there are certain failures, the selection of good data is being done by the boxes automatically through fault monitoring and voting (i.e. mid value selection). Mid-value selection of certain data is what an older generation aircraft (such as the 747-400 or 767) would be doing during the critical phase of Autoland.
The boxes are automatically supplying the best available data that the pilots would use under normal and some abnormal situations. And if things get really bad, you still have the option of going back to the basics by selecting SAARU "single channel" data if you, say, want to know the data that a particular pitot/static system is producing.
Join Date: Sep 2013
Location: UK
Posts: 730
Likes: 0
Received 0 Likes
on
0 Posts
While I understand that the 777 ADIRU is more advanced then the 737 NG's, I'd still rather have completely independent systems for left and right sides. I just don't trust any single system, regardless of its internal redundancies, to automatically ignore bad inputs and always display the right data. This seems to be borne out by the 787 cases here.
Right from the start of our careers we are taught to trust our instruments, but more and more often, the modern instruments are having simultaneous widespread failures. AF447 was a good example, but that was well after issues with pitot heads had been identified and the accident could have been avoided if the faulty units had been replaced. Now the 787 is getting similar issues. So, do we now have to change mindsets and start second guessing the instruments?
With single source systems, any failure can lead to all displays showing the same error. I don't know if that was a factor in the AF447 accident as I don't know their architecture, but I think that despite its flaws, you have to go a long way to beat the 737's simplicity and redundancy. More modern types seem to have too much networking and too many vulnerabilities to a single fault.
Right from the start of our careers we are taught to trust our instruments, but more and more often, the modern instruments are having simultaneous widespread failures. AF447 was a good example, but that was well after issues with pitot heads had been identified and the accident could have been avoided if the faulty units had been replaced. Now the 787 is getting similar issues. So, do we now have to change mindsets and start second guessing the instruments?
With single source systems, any failure can lead to all displays showing the same error. I don't know if that was a factor in the AF447 accident as I don't know their architecture, but I think that despite its flaws, you have to go a long way to beat the 737's simplicity and redundancy. More modern types seem to have too much networking and too many vulnerabilities to a single fault.
AS, to answer to your concerns and increase confidence in aircraft systems, it would be necessary to study CS 25 certification requirements together with the manufacturers design submission and system implementation.
Simply, aircraft instrument displays must not present hazardously misleading information (definition and risk level in CS 25). This requirement is often achieved by using independent sensors and some form of cross monitoring or confidence voting; where ‘bad’ data is eliminated or the display shut down to prevent display.
A simple analogy is like the glass half full, half empty dilemma. Arbitration between the two opposing views requires a third party and only then in avionics terms is ‘amalgamated’ data used.
The Boeing problem appears to be in the inability to prevent the display of erroneous data, either because arbitration has failed or the inability to determine ‘bad’ sensed data and thus shutdown the display. In terms of beer glasses, there is little value of agreeing half full etc, if the beer is already flat.
The Boeing problem may be similar to that of ice crystals and pitots, where either the atmosphere is not as expected or that the sensor is susceptible to unusual conditions (or both); in this instance water.
This condition is very serious and requires (technical) rectification in the sensing system; however as a side problem, human reaction to an erroneous display appears to have identified a further issue in the control system.
Meanwhile in our ill-experienced litigious society, manufacturers have to explain the basic responses to pilots.
Something like warning people who have been brought up and now dependant on automated alcho-pops and fizzy mixes, not to drink flat beer, which of course requires an understanding of what ‘good’ beer is in the first place.
Simply, aircraft instrument displays must not present hazardously misleading information (definition and risk level in CS 25). This requirement is often achieved by using independent sensors and some form of cross monitoring or confidence voting; where ‘bad’ data is eliminated or the display shut down to prevent display.
A simple analogy is like the glass half full, half empty dilemma. Arbitration between the two opposing views requires a third party and only then in avionics terms is ‘amalgamated’ data used.
The Boeing problem appears to be in the inability to prevent the display of erroneous data, either because arbitration has failed or the inability to determine ‘bad’ sensed data and thus shutdown the display. In terms of beer glasses, there is little value of agreeing half full etc, if the beer is already flat.
The Boeing problem may be similar to that of ice crystals and pitots, where either the atmosphere is not as expected or that the sensor is susceptible to unusual conditions (or both); in this instance water.
This condition is very serious and requires (technical) rectification in the sensing system; however as a side problem, human reaction to an erroneous display appears to have identified a further issue in the control system.
Meanwhile in our ill-experienced litigious society, manufacturers have to explain the basic responses to pilots.
Something like warning people who have been brought up and now dependant on automated alcho-pops and fizzy mixes, not to drink flat beer, which of course requires an understanding of what ‘good’ beer is in the first place.
