Media reporting crash investigators saying FDR showing airspeed indicator problems over several flights.
AF447 was an airspeed indicator problem but in the dark.
This one in daylight and clear weather.
this Lion Air plane had trouble with the air speed indicator on its last four flights. This information is apparently confirmed by the flight data recorder.
AF447 was a minor issue, which was turned into an accident by a totally unwarranted response. If the pilot flying had simply flown the current attitude (which would have been about 2.5º nose up), and left the power exactly where it was (about 85%), nothing would have happened. It would have reverted to alternate law, and after a few minutes the airspeed would have started working again.
I am feeling a huge difference between real pilots, to whom something like a simple airspeed indicator fault is something that is naturally overcome, and human drones that do not have a capacity any bigger than automatic systems and responses. Do you agree?
It confirms what we already know. There was issues with ASI and elevator feel unit.Media reporting crash investigators saying FDR showing airspeed indicator problems over several flights.
I managed to get bits of the previous post flight maintenance reports from various sources. It looks like the unreliable airspeed indications from the last 4 flights may not have been caused by a single generated warning/fault on the sensor detection (ie: not purely a pitot issue).Am now getting info (which needs confirmation) that over the past week, whenever a problem occur, it would appear, get rectified according to the FIM and TSM, then fly again, get the same warning, fix it again, then the aircraft would generate a different problem. If this is true then the guys on the ground had little chance to pick up on them as a "repetitive problem" (which would require a different kind of troubleshooting). When taking a step back, it does appear that this may be an ADR issue (not a sensor input to the ADR, but the ADR itself). The major problem with this, is the STS (Speed Trim System)... which if taking erroneous ADR feeds, could lead to...
You need to dissociate G loading and attitude. The two are not the same thing. Whilst -1G from straight and level will quickly give you a steep dive, it would also allow you to fly straight and level...if you happened to roll inverted first.
AF447 was a minor issue, which was turned into an accident by a totally unwarranted response. If the pilot flying had simply flown the current attitude (which would have been about 2.5º nose up), and left the power exactly where it was (about 85%), nothing would have happened. It would have reverted to alternate law, and after a few minutes the airspeed would have started working again.
Speed trim is applied to the stabilizer automatically at low speed, low weight, aft C of G and high thrust - i.e. on most take-offs. Speed trim is a dual channel system. Sometimes you may notice that the speed trim is trimming in the opposite direction to you, this is because the speed trim is trying to trim the stabilizer in the direction calculated to provide the pilot with positive speed stability characteristics. The speed trim system adjusts stick force so the pilot must provide significant amount of pull force to reduce airspeed or a significant amount of push force to increase airspeed. Whereas pilots are typically trying to trim the stick force to zero. Occasionally these may be in opposition.
IIRC, wasn't it a pitot issue and the first officer didn't relinquish control from his joystick, whether absent mindedly or not, resulting in the captain not able to control the plane from a stall? Been a while since I watched one of the air crash investigation shows on it.
AFF Supporters can remove this and all advertisements
Responding to the Lion Air jetliner crash that killed 189 people in Indonesia last week, manufacturer Boeing and US aviation regulators intend to issue twin safety warnings about potentially suspect flight-control software that can confuse pilots and lead to a steep descent of the affected aircraft type, according to people familiar with the matter.
The moves are the first public indication that investigators suspect a possible software glitch or misinterpretation by pilots – related to an essential system that measures how high or low a plane’s nose is pointed – may have played an important part in the sequence of events that caused the Boeing 737 Max 8 to plunge into the Java Sea.
The anticipated actions by Boeing and the US Federal Aviation Administration are preliminary, these people said, and are expected to stop short of urging or mandating replacement or inspection of any specific onboard system. Rather, they amount to an official red flag for pilots, highlighting potential hazards stemming from the interaction of certain software with various other coughpit alerts, and reiterating the importance of following standard procedures under such circumstances.
The moves are the first public indication that investigators suspect a possible software glitch or misinterpretation by pilots – related to an essential system that measures how high or low a plane’s nose is pointed – may have played an important part in the sequence of events that caused the Boeing 737 Max 8 to plunge into the Java Sea.
It's not a fly by wire aircraft, so the amount of control any software can have is limited.
I’ll be interested to see the actual Boeing bulletins, as opposed to a media interpretation.
Can the 737 systems in any scenario input a pitch down independent of pilot command?
Runaway trim,