Back to Squawk list
  • 12

Pilot radioed alert on doomed Indonesian jet's previous flight

The pilot of a Lion Air flight from Indonesia's Bali island on Sunday made a radio alert minutes after take-off due to technical problems, but they were overcome and he pushed on to Jakarta. The same jet crashed on another flight hours later, killing all 189 people on board. Herson, chief of the airport authority for the Bali-Nusa Tenggara area, told Reuters that after the alert the pilot updated the control tower to say that the plane was flying normally and he would not return to the… ( さらに...

Sort type: [Top] [Newest]

Apparently the recorders have been located and we all await the analysis. However, in the absence of evidence to the contrary, usually these computer driven systems only act on the input they receive. When these inputs are not in sync with what the pilot wants or expects to happen, there is mass confusion until new inputs correct the situation. The perception that it’s an aircraft issue prevails until it’s not! I always remember back when the ac reacts differently, the pilot messed up. Then the autopilot was added between the pilot and the ac. Then the FMS got in between the autopilot and the pilot, then the auto thrust got in between the pilot, the FMS, the Autopilot & the aircraft, so the further removed the pilot was from the actual flying of the aircraft the less understanding of the systems operation in the abnormal. Automation is a wonderful thing, until it’s not?
At least they weren't in 5000 feet of water so, small consolation, but not an AF447 battle to find the boxes. The FDR will tell the tale and system integration is now so embedded I don't know how they can even anticipate all the possible failure modes. The loss of ADCs in the last generation of aircraft I retired on cost half the panel and all of the autopilot. The Emirates A380 bust tells me that it is more important than ever to be able to identify and utilize what is left. And he said "all the whistles and bells didn't help". You are spot on about the automation and to quote someone here from a while back, "The automation is great till it fails, then it leads to a more complicated accident investigation". And I'll say, If it takes Rhodes scholars to design them these days, maybe we need Rhodes scholars to fly them. Good luck with that.
Don't forget that crucial inputs are the pitot-static, altimeter & ADI systems that exist regardless of automation. If you don't know how fast, how high or your pitch, the computers won't know it either.
FlightRadar posted the details of the speed/altitude fluctuations.
Looking at the FLightAware log chart of the a/c's previous flight the night before it crashed (JT43)...there was also a similar issue with a sudden drop in altitude combined with (or caused by?) a sudden decrease in airspeed! Could this be the result of an extreme AOA?
It's been reported that prior to this flight maintenance had worked on the ac while loaded with pax. I'm sure they felt undue pressure to expedite the plane's release...
Yep! According to the MSN report I posted as a link...there were issues with the air conditioning and cabin lights! Any connection with a/c performance?
According to the FR24 graphic readout, the plane had virtually levelled out at approx. 5000 ft. and approx. 325 mph. This would suggest level, stable flight with more than adequate lift. Cockpit displays still give the flight crew accurate airspeed, attitude and elevation read outs, do they not? How hard is it for a pilot to know how the a/c is flying? Then the plane drops out of the sky or nosedives? Crazy! Maybe the previous flight crew should have left some urgent notations or a memo for the crew that followed as to their peculiar experience on that a/c? Crucial information, yes?


アカウントをお持ちではありませんか? 今すぐ登録(無料)!機能やフライトアラート、その他様々な設定をカスタマイズできます!