Air Asia’s slogan “Now Everyone Can Fly” took a new dimension on Air Asia flight AK-5748 when a snake appeared on the flight.
On 10 February 2022, an Air Asia Airbus A320-200, registration 9M-RAN performing flight AK-5748 from Kuala Lumpur (KUL) to Tawau (TWU) in Malaysia, was enroute at FL330 over the South China Sea about 250nm westnorthwest of Kuching (Malaysia) when a snake appeared in the overhead lockers in the passenger cabin. The crew diverted the aircraft to Kuching for a safe landing about 45 minutes later.
A replacement A320-200N continued the flight and reached Tawau with a delay of about 5:50 hours.
The occurrence aircraft was still on the ground in Kuching about 28 hours after landing.
Video posted on YouTube shows the outline of a small snake in the structure of the overhead lockers, above passenger heads.
The Airbus A320-216(WL), with tail number 9M-RAN was put it to service in May 2019 and belongs to lessor Castlelake.
Another incident at Emirates in Dubai, this time a Boeing 777 passenger flight bound for India was accelerating for take off at Dubai – without air traffic control clearance – meanwhile another Emirates jet was crossing runway at the same time.
Incident: Emirates B773 at Dubai on Jan 9th 2022, rejected takeoff without clearance due to crossing aircraft
An Emirates Boeing 777-300, registration A6-EQA performing flight EK-524 from Dubai (United Arab Emirates) to Hyderabad (India), was accelerating for takeoff from Dubai’s runway 30R when the crew was instructed to reject takeoff at high speed (above 100 knots over ground) due to a crossing aircraft. The aircraft slowed safely and vacated the runway via taxiway N4 behind the aircraft, that had crossed the runway.
An Emirates Boeing 777-300, registration A6-EBY performing flight EK-568 from Dubai (United Arab Emirates) to Bangalore (India), was taxiing for departure and was cleared to cross runway 30R from taxiway M5A to N4 and was entering the runway just when EK-524 began the takeoff roll.
According to information The Aviation Herald received from two independent sources, EK-524 began their takeoff roll without ATC clearance. Tower subsequently instructed EK-524 to stop. According to information EK-524 may have reached 130 KIAS when they rejected takeoff. According to ADS-B data transmitted by the aircraft’s transponder EK-524 had reached 100 knots over ground about 790 meters/2600 feet down the runway and about 1700 meters/5700 feet short of taxiway N4.
EK-568 continued taxi and departed normally. EK-524 taxied back the holding point of runway 30R and departed about 30 minutes after the rejected takeoff.
On Jan 13th 2022 the airline reported, that EK-524 was instructed by tower to abort takeoff on Jan 9th 2022, the crew rejected takeoff successfully. There was no damage to the aircraft and there were no injuries. An internal investigation has been initiated, UAE’s GCAA also opened an investigation.
Aviation is incredibly safe, and for every disaster there are many catastrophes that are narrowly avoided. It would appear that an Emirates Boeing 777 departing Dubai about a week ago nearly had a major incident after takeoff. Let me share what I’ve been able to piece together so far about this incident.
In this post:
What happened to this Emirates plane on takeoff?
The flight in question is Emirates EK231 from Dubai (DXB) to Washington Dulles (IAD), which was scheduled to depart at 2:25AM on December 20, 2021. The flight was operated by one of Emirates’ newest Boeing 777-300ERs, with the registration code A6-EQI.
Based on what I’ve been told and have been able to piece together:
Before departure, the pilots forgot to set the flight director to an altitude of 4,000 feet, but rather left it at an altitude of zero feet (which the previous crew had presumably set on approach to Dubai)
After takeoff, the plane’s nose pitched down, to the point that the plane was at 175 feet and flying at 262 knots (this is supported by actual flight data, which you can find below); as a point of comparison, under normal circumstances the plane would be flying at well under 200 knots at that altitude
While I haven’t been able to figure out more details about this, I’m told that the plane sustained damage, yet the pilots made the decision to continue to Washington (I’m still working on figuring out what kind of damage we’re talking about, as the plane operated the return flight later that day)
I’ve been told that all four pilots have been fired, and that the US Federal Aviation Administration is now investigating this incident, given that the flight was US-bound (note that I haven’t gotten official confirmation of either of these, though at a minimum I’d assume the pilots are suspended pending an investigation)
For those curious, below is some data from Flightradar24 for the flight in question vs. a more “standard” flight on the same route. You’ll want to look at the right two columns, with the left column being the altitude, and the right column being the speed.
Here’s the data for the flight in question:
Then here’s the data for the same flight several days earlier:
As you can tell, that data is vastly different. This sounds concerning — a Boeing 777 (presumably) full of passengers and fuel was descending right after takeoff, to the point that it was lower than many high rises in Dubai, and flying at a very fast pace.
Emirates has sent a memo to pilots
While Emirates hasn’t yet officially commented on this incident, the airline did send out the following alert to pilots today, essentially referencing the incident:
CREWS ARE REMINDED THAT THERE ARE NO FCOM NORMAL PROCEDURE REQUIREMENTS TO CHANGE THE MCP AFTER LANDING OR SHUTDOWN. THERE HAVE BEEN TIMES WHEN THE MCP “ALTITUDE WINDOW” HAS BEEN SET TO THE AIRPORT ELEVATION WHICH MAY CAUSE ISSUES ON THE SUBSEQUENT DEPARTURE. CREWS SHALL NOT SET AIRPORT ELEVATION ON THE MCP AFTER LANDING OR SHUT DOWN.
I wonder what it was like on the plane
I’d be curious to hear from a passenger onboard, because I wonder if passengers had any clue what was going on:
On the one hand, perhaps passengers didn’t really know what was going on, since it was dark outside, and most people aren’t really avgeeks and paying attention to every aircraft movement
On the other hand, perhaps passengers totally knew what was going on, given that the plane was barely climbing after takeoff, but rather just kept flying faster and faster
While I feel safe flying with Emirates, in general I’m not surprised to see things like this happen once in a while:
Emirates pilots deal with a lot of fatigue, given that they often operate ultra long haul flights departing in the middle of the night; no matter how hard you try, this has to take a toll on you
In general Emirates hires 777 pilots with less experience than you’d find at some other airlines; that’s largely because it’s Emirates’ smallest plane, and Emirates isn’t going to consistently have a couple of people with 10,000+ flights hours at the controls (as you’d find on American and United, for example)
Then there’s coronavirus, which in general has caused a lot of pilots to become a bit rusty, since many have only recently been brought to work after being furloughed
Bottom line
While I’m sure more information will emerge soon, it’s my understanding that an Emirates Boeing 777 had a pretty frightening departure out of Dubai about a week ago. Specifically, the altitude for after takeoff was set to ground level rather than 4,000 feet, and as a result the plane didn’t climb very high, but rather just sped up. The plane ended up flying at 261 knots just 175 feet over the ground, which must have been frightening for those on the ground and in the air.
Since the FAA is allegedly investigating the incident, hopefully we end up learning more. If anyone has more details on the incident, please chime in!
Reported by OneMileAtATime by Ben Schlappig on 28 December 2021.
Singaporean Transport Safety Investigation Bureau Investigators noted that the crew had been facing several individual pressures prior to the departure and highlighted that:
The Singapore Airlines captain inadvertently miskeyed, typing ‘500’ rather than ‘500A’, which neither crew member noticed.
This error stopped the Boeing 777 aircraft climb at 500ft.
The pilot cross-checking process failed.
Time pressure resulted in the first officer’s not carrying out a habitual scan of the entries.
The captain called for autopilot engagement at 360ft – an early selection because he wanted to reduce workload
The captain “did not realise that the aircraft had stopped climbing”, says the inquiry, and had called for flap retraction believing the 777 had passed 1,000ft. Investigators state that the crew “did not verify” altitude information from the instrument displays.
SIA 777 stopped climb at 500ft after crew’s waypoint entry error
Pilots of a Singapore Airlines Boeing 777-300ER inadvertently entered an incorrect waypoint altitude constraint prior to departure, resulting in several alerts from the ground-proximity warning system as the aircraft climbed out of Shanghai Pudong.
The take-off runway assigned had been changed from 34L to 35R which meant the aircraft’s standard departure route switched from HSN 22X to HSN 12X.
This required updating the flight-management computer with the new departure route. The first waypoint on this route, identified as PD062, did not have any speed or altitude crossing constraint which meant the field on the computer’s route display was blank.
Although this was not abnormal, the captain “preferred to have the speed constraint explicitly displayed”, says the Singaporean Transport Safety Investigation Bureau, in its inquiry into the 2 September 2019 incident.
He decided to enter the speed constraint of 250kt, as shown on the departure charts. The 777’s flight-management computer required speed constraints to have a corresponding altitude constraint, so the captain chose to enter ‘500A’ – meaning that the PD062 waypoint should be crossed at 500ft or above.
But the captain inadvertently miskeyed, typing ‘500’ rather than ‘500A’, which neither crew member noticed. This error meant the aircraft’s autopilot would limit the aircraft to 500ft ahead of the waypoint crossing.
“The first officer observed the [captain’s] inputs, as part of the cross-checking process, and accepted the inputs as correct,” the inquiry says, adding that “time pressure” resulted in the first officer’s not carrying out a habitual scan of the entries.
As the aircraft took off from runway 35R, in darkness, the captain called for autopilot engagement at 360ft – an early selection because he wanted to reduce workload, given the need for the crew to spend time converting Chinese metric altitude clearances to feet.
Source: Martin Oertle/Creative Commons
Pilots on the 777 (9V-SWD) engaged the autopilot just after lift-off
But the autopilot selection meant the aircraft initially climbed to 750ft before descending to 500ft in compliance with the altitude constraint entered for the PD062 waypoint.
The captain “did not realise that the aircraft had stopped climbing”, says the inquiry, and had called for flap retraction believing the 777 had passed 1,000ft. Investigators state that the crew “did not verify” altitude information from the instrument displays.
As the flaps started retracting, the enhanced ground-proximity warning system activated and issued an unexpected ‘don’t sink’ alert, which startled the pilots. The captain nevertheless chose to complete the flap retraction, suggesting to the first officer that the alert might have been due to a pitch reduction resulting from a tailwind.
Nine seconds after the initial alert, the crew received a second ‘don’t sink’ warning, and a third some 9s after that.
“The flight crew then realised that the aircraft had levelled off and they needed to reinitiate a climb,” says the inquiry.
While the captain selected ‘flight level change’ mode in response, he then reverted to ‘vertical navigation’ mode. Flight-data recorder information showed this made no difference to the 777’s altitude, and the aircraft remained at 480-500ft.
Another ‘don’t sink’ caution was triggered, followed shortly afterwards by a ‘pull up’ warning, prompting the captain to disengage the autopilot, pitch the aircraft nose-up and advance the thrust levers.
The aircraft climbed to 1,780ft but, after the captain called for the autopilot to be re-engaged, started descending again towards the 500ft constraint altitude.
At this point the first officer noticed the erroneous constraint entry for the waypoint, and understood the aircraft’s behaviour, informing the captain that the entry needed to be cancelled. Once the entry was deleted, the aircraft was able to climb without further problems and the jet proceeded to Singapore.
“This occurrence is an apt reminder of the guidance given in the flight crew training manual that, when automation does not perform as expected, the flight crew should reduce the level of auto-flight and identify and resolve the condition,” says the inquiry.
“The original level of auto-flight should only be resumed after they have regained proper control of the flight path and performance level.”
Investigators noted that the crew had been facing several individual pressures prior to the departure, including weather concerns, minimum equipment list considerations, and problems downloading route information as a result of a difficult controller-pilot datalink connection.
A change in Boeing’s 737 MAX manufacturing process that was insufficiently vetted caused an electrical system problem.
In this change, fasteners were used to hold a backup electrical power unit in place, rather than rivets. Fasteners did not provide a complete electrical grounding path to the unit.
What’s at stake with new 737 MAX electrical issues
After the events of the past few years it’s no surprise that when the 737 MAX has an issue, it receives a lot of coverage. And the latest 737 MAX headlines concerning potential electrical problems are no doubt a big headache for Boeing and its operators alike. It’s bad publicity at the worst possible time for the 737 MAX, when everyone involved will have been hoping for a smooth and quiet reintroduction to service. But it also raises new questions and concerns, on top of many already existing ones, about Boeing’s manufacturing processes and corporate culture. So just what is going on here, and what’s at stake?
To be clear, this appears completely unrelated to the issues that caused two fatal crashes of the type prior to its worldwide grounding. So just how serious are these new electrical problems?
The Seattle Times published an in-depth piece on what the actual issue is last week. According to that article, a “A minor change in Boeing’s 737 MAX manufacturing process that was insufficiently vetted caused an electrical system problem.” It seems that in this change, fasteners were used to hold a backup electrical power unit in place, rather than rivets. Boeing has said that it discovered the issue while building a new MAX and that, according to the Seattle Times article, the fasteners “did not provide a complete electrical grounding path to the unit.”
Boeing did recently begin delivering 787s again. And aside from this issue the 737 MAX has had a relatively smooth rollout with dozens of airlines sending them back into the skies and it being mostly a non-event outside of avgeek circles. Indeed it seems that the expected public mass anxiety about getting back on a 737 MAX was greatly exaggerated, and most people aren’t even noticing that they’re on one.
But the fundamental issues at Boeing remain an ongoing concern, and even as the company fixes aircraft problems as they come up, many are wondering just how deep these problems go, and whether we’ve now seen the end of them. This latest 737 MAX issue only feeds those concerns.
Airline software super-bug: Flight loads miscalculated because women using ‘Miss’ were treated as children
Weight blunder led to wrong thrust used on takeoff, says UK watchdog
A programming error in the software used by UK airline TUI to check-in passengers led to miscalculated flight loads on three flights last July, a potentially serious safety issue.
The error occurred, according to a report [PDF] released on Thursday by the UK Air Accidents Investigation Branch (AAIB), because the check-in software treated travelers identified as “Miss” in the passenger list as children, and assigned them a weight of 35 kg (~77 lbs) instead of 69 kg (~152 lbs) for an adult.
The AAIB report attributes the error to cultural differences in how the term Miss is understood.
“The system programming was not carried out in the UK, and in the country where it was performed the title Miss was used for a child, and Ms for an adult female, hence the error,” the report says.
The Register asked TUI where the system programming was done, but the company ignored that question in its response to our inquiry.
“The health and safety of our customers and crew is always our primary concern,” a TUI spokesperson said in an emailed statement. “Following this isolated incident, we corrected a fault identified in our IT system. As stated in the report, the safe operation of the flight was not compromised.”
Potentially fatal math
Flight load miscalculations have the potential to affect aircraft handling and to create serious safety issues: the figures are used for figuring out fuel levels, altitude, takeoff thrust, and so on. The 2018 fatal crash of Cubana de Aviación Flight 972, for example, has been attributed to excessive load, as has the 1997 crash of Fine Air Douglas DC-8 cargo flight.
According to the AAIB, the software issue was first spotted on July 10, 2020, when three adult passengers identified as Miss were checked in as children. Airline personnel caught the discrepancy and proceeded to make adjustments manually.
On July 17, the developer(s) working on the check-in application “adapted a piece of software, which changed the title of any adult female from Miss to Ms automatically.”
Alas, the revised code could only convert honorifics for passengers prior to check-in. Bookings made with the title Miss that had already checked in, including those checking in online 24 hours prior to departure, could not be changed.
“On 20 July, 2020, the programmer was making enhancements to the program to improve its performance,” the report says. “This should not have stopped the program from working, but as this was a ‘fix,’ it could not be known for sure. A combination of the [TUI] teams not working over the weekend [to make manual corrections] and the ‘online’ check-in being open early on Monday 20 July, 24 hours ahead of the flight, meant the incorrectly allocated passenger weights were not corrected.”
On 21 July, 2020, three TUI Airways flights departed from the UK with inaccurate load sheets as a result of the software issue, which would not be fixed until July 24, 2020.
The first of these, and the only one detailed in the report, was TUI Airways flight BY-7226, a Boeing 737-800 with the registration G-TAWG. The plane travelled from Birmingham International Airport in the UK to Palma de Mallorca in Spain, carrying 167 passengers and 6 crew.
The 737-800 departed with a takeoff weight that exceeded the load sheet (the projected weight) by 1,244 kg (~2743 lbs) because the load sheet listed 65 children on board, compared to the 29 children expected from the flight plan – which includes the actual weight. The load sheet also varied from the flight plan due to errant baggage weight calculations.
The result of all this was that the plane used less thrust to take off than it should have – 88.3 per cent instead of 88.9 per cent given its actual takeoff weight and environmental conditions. Fortunately, this was “marginally” more than the minimal regulatory requirements – 88.2 per cent – and the flight made it to its destination safely.
It’s suggested this won’t happen again: “An upgrade of the system producing load sheets was carried out to prevent reoccurrence,” the report concludes. ®
Boeing 737 Sriwijaya Flight 182 Crashed in Indonesia Just After Takeoff on 9 January 2021.
Did the downturn of air travel caused by COVID-19 contribute to this crash?
The Sriwijaya 737 aircraft had been in storage for 9 months in Surabaya and was inspected on 14 December 2020 and since 19 December 2020 operated 132 flights.
Storage may have been a factor in the crash, aircraft must be kept operating otherwise they deteriorate. Mothballed planes pose a safety risk.
Boeing whistleblower raises doubts over 787 oxygen system
John Barnett says tests suggest up to a quarter of the oxygen systems could be faulty and might not work when needed.
He also claimed faulty parts were deliberately fitted to planes on the production line at one Boeing factory.
Boeing denies his accusations and says all its aircraft are built to the highest levels of safety and quality.
The firm has come under intense scrutiny in the wake of two catastrophic accidents involving another one of its planes, the 737 Max.
Mr Barnett, a former quality control engineer, worked for Boeing for 32 years, until his retirement on health grounds in March 2017.
From 2010 he was employed as a quality manager at Boeing’s factory in North Charleston, South Carolina.
This plant is one of two that are involved in building the 787 Dreamliner, a state-of-the-art modern airliner used widely on long-haul routes around the world. Despite early teething problems following its entry into service the aircraft has proved a hit with airlines, and a useful source of profits for the company.
But according to Mr Barnett, 57, the rush to get new aircraft off the production line meant that the assembly process was rushed and safety was compromised. The company denies this and insists that “safety, quality and integrity are at the core of Boeing’s values”.
In 2016, he tells the BBC, he uncovered problems with emergency oxygen systems. These are supposed to keep passengers and crew alive if the cabin pressurisation fails for any reason at altitude. Breathing masks are meant to drop down from the ceiling, which then supply oxygen from a gas cylinder.
Without such systems, the occupants of a plane would rapidly be incapacitated. At 35,000ft, (10,600m) they would be unconscious in less than a minute. At 40,000ft, it could happen within 20 seconds. Brain damage and even death could follow.
Although sudden decompression events are rare, they do happen. In April 2018, for example, a window blew out of a Southwest Airlines aircraft, after being hit by debris from a damaged engine. One passenger sitting beside the window suffered serious injuries and later died as a result – but others were able to draw on the emergency oxygen supplies and survived unharmed.
Mr Barnett says that when he was decommissioning systems which had suffered minor cosmetic damage, he found that some of the oxygen bottles were not discharging when they were meant to. He subsequently arranged for a controlled test to be carried out by Boeing’s own research and development unit.
This test, which used oxygen systems that were “straight out of stock” and undamaged, was designed to mimic the way in which they would be deployed aboard an aircraft, using exactly the same electric current as a trigger. He says 300 systems were tested – and 75 of them did not deploy properly, a failure rate of 25%.
Mr Barnett says his attempts to have the matter looked at further were stonewalled by Boeing managers. In 2017, he complained to the US regulator, the FAA, that no action had been taken to address the problem. The FAA, however, said it could not substantiate that claim, because Boeing had indicated it was working on the issue at the time.
Boeing itself rejects Mr Barnett’s assertions.
It does concede that in 2017 it “identified some oxygen bottles received from the supplier that were not deploying properly. We removed those bottles from production so that no defective bottles were placed on airplanes, and we addressed the matter with our supplier”.
But it also states that “every passenger oxygen system installed on our airplanes is tested multiple times before delivery to ensure it is functioning properly, and must pass those tests to remain on the airplane.”
“The system is also tested at regular intervals once the airplane enters service,” it says.
This is not the only allegation levelled at Boeing regarding the South Carolina plant, however. Mr Barnett also says that Boeing failed to follow its own procedures, intended to track parts through the assembly process, allowing a number of defective items to be “lost”.
He claims that under-pressure workers even fitted sub-standard parts from scrap bins to aircraft on the production line, in at least one case with the knowledge of a senior manager. He says this was done to save time, because “Boeing South Carolina is strictly driven by schedule and cost”.
On the matter of parts being lost, in early 2017 a review by the Federal Aviation Administration upheld Mr Barnett’s concerns, establishing that the location of at least 53 “non-conforming” parts was unknown, and that they were considered lost. Boeing was ordered to take remedial action.
Since then, the company says, it has “fully resolved the FAA’s findings with regard to part traceability, and implemented corrective actions to prevent recurrence”. It has made no further comment about the possibility of non-conforming parts making it onto completed aircraft – although insiders at the North Charleston plant insist it could not happen.
Mr Barnett is currently taking legal action against Boeing, which he accuses of denigrating his character and hampering his career because of the issues he pointed out, ultimately leading to his retirement. The company’s response is that he had long-standing plans to retire, and did so voluntarily. It says “Boeing has in no way negatively impacted Mr Barnett’s ability to continue in whatever chosen profession he so wishes”.
The company says it offers its employees a number of channels for raising concerns and complaints, and has rigorous processes in place to protect them and make sure the issues they draw attention to are considered. It says: “We encourage and expect our employees to raise concerns and when they do, we thoroughly investigate and fully resolve them.”
But Mr Barnett is not the only Boeing employee to have raised concerns about Boeing’s manufacturing processes. Earlier this year, for example, it emerged that following the Ethiopian Airlines 737 Max crash in March, four current or former employees contacted an FAA hotline to report potential issues.
Mr Barnett believes that the concerns he has highlighted reflect a corporate culture that is “all about speed, cost-cutting and bean count (jobs sold)”. He claims managers are “not concerned about safety, just meeting schedule”.
That’s a view which has support from another former engineer, Adam Dickson, who was involved with the development of the 737 Max at Boeing’s Renton factory in Washington state.
He tells the BBC there was “a drive to keep the aeroplanes moving through the factory. There were often pressures to keep production levels up.
“My team constantly fought the factory on processes and quality. And our senior managers were no help.”
In it, the manager complained about workers being “exhausted” from having to work at a very high pace for an extended period.
He said that schedule pressure was “creating a culture where employees are either deliberately or unconsciously circumventing established processes”, adversely affecting quality.
For the first time in his life, the email’s author said, he was hesitant about allowing his family aboard a Boeing aircraft.
Boeing says that together with the FAA, it implements a “rigorous inspection process” to ensure its aircraft are safe, and that all of them go through “multiple safety and test flights” as well as extensive inspections before they are allowed to leave the factory.
Boeing recently commissioned an independent review of its safety processes, which it says “found rigorous enforcement of, and compliance with, both the FAA’s aircraft certification standards and Boeing’s aircraft design and engineering requirements.” It said that the review had “established that the design and development of the [737] Max was done in line with the procedures and processes that have consistently produced safe airplanes.”
Nevertheless, as a result of that review, in late September the company announced a number of changes to its safety structures. They include the creation of a new “product and services safety organization”.
It will be charged with reviewing all aspects of product safety “including investigating cases of undue pressure and anonymous product and safety concerns raised by employees”.
Mr Barnett, meanwhile, remains deeply concerned about the safety of the aircraft he helped to build.
“Based on my years of experience and past history of plane accidents, I believe it’s just a matter of time before something big happens with a 787,” he says.
“I pray that I am wrong.”
Reported by BBC News on 6 November 2019 by By Theo Leggett, Business correspondent.
Arlington, Virginia — An American Airlines mechanic appeared in a Miami court Friday after being charged with sabotaging a jetliner. The aircraft was filled with passengers and set to take-off.
At 10:30 a.m. on July 17th, American Airlines flight 2834 pulled out of gate 49 at Miami International Airport headed for the Bahamas. But pilots noticed a problem and as the plane, with 150 people aboard, moved into position on the runway, they were forced to turn around.
According to investigators, American Airlines mechanic Abdul-Majeed Marouf Ahmed Alani, who appeared in a Florida court Friday, was seen on surveillance video tampering with the plane’s navigation systems just an hour before it was scheduled to depart. Alani, who’s worked for American since 1988, said he tried to sabotage the plane because he was upset about a stalled contract dispute between his union and American Airlines and that it had affected him financially.
Captain Laura Einsetler said had the plane taken off, it could have been catastrophic.
“It is significant. Any time we reject a takeoff, that’s a big deal,” she said.
Alani said he hoped sabotaging the plane would allow him to get overtime pay to fix it. American Airlines called it a disturbing event and said that it has been cooperating with the investigation.
Pilot Who Hitched a Ride Saved Lion Air 737 Day Before Deadly Crash
Jumpseat rider played critical role in Indonesian cockpit
Pilot actions show multiple errors required to crash 737 Max
An off-duty pilot saved the 737 Max from a crash. The next day, the same plane on flight JT610 crashed into the sea.
As the Lion Air crew fought to control their diving Boeing Co. 737 Max 8, they got help from an unexpected source: an off-duty pilot who happened to be riding in the cockpit.
That extra pilot, who was seated in the cockpit jumpseat, correctly diagnosed the problem and told the crew how to disable a malfunctioning flight-control system and save the plane, according to two people familiar with Indonesia’s investigation.
The next day, under command of a different crew facing what investigators said was an identical malfunction, the jetliner crashed into the Java Sea killing all 189 aboard.
The previously undisclosed detail on the earlier Lion Air flight represents a new clue in the mystery of how some 737 Max pilots faced with the malfunction have been able to avert disaster while the others lost control of their planes and crashed. The presence of a third pilot in the cockpit wasn’t contained in Indonesia’s National Transportation Safety Committee’s Nov. 28 report on the crash and hasn’t previously been reported.
The so-called dead-head pilot on the flight from Bali to Jakarta told the crew to cut power to the motor in the trim system that was driving the nose down, according to the people familiar, part of a checklist that all pilots are required to memorize.
By contrast, the crew on the flight that crashed the next day didn’t know how to respond to the malfunction, said one of the people familiar with the plane’s cockpit voice recorder recovered as part of the investigation. They can be heard checking their quick reference handbook, a summary of how to handle unusual or emergency situations, in the minutes before they crashed, Reuters reported, citing people it didn’t name.
Lion Air spokesman Danang Prihantoro declined to comment on the role of a third pilot, saying, “All the data and information that we have on the flight and the aircraft have been submitted to the Indonesian NTSC. We can’t provide additional comment at this stage due the ongoing investigation on the accident.”
The Indonesia safety committee report said the plane had had multiple failures on previous flights and hadn’t been properly repaired.
Airline mechanics tried four times to fix related issues on the plane starting Oct. 26, according to the Indonesia preliminary report. After pilots reported issues with incorrect display of speeds and altitude in the two prior flights, workers in Denspasar, Bali, replaced a key sensor that is used by the Boeing plane to drive down its nose if it senses an emergency.
Flight data shows the sensor, called the “angle of attack” vane, which measures whether air is flowing parallel to the length of the fuselage or at an angle, was providing inaccurate readings after that.
However, the pilots on the harrowing Oct. 28 flight from Bali to Jakarta didn’t mention key issues with the flight after they landed, according to the report.
Their request for maintenance didn’t mention they had been getting a stall warning since about 400 feet after takeoff as a result of the faulty angle-of-attack sensor. It was still giving false readings the next morning on the flight that crashed, according to flight data.
Representatives for Boeing and the Indonesian safety committee declined to comment on the earlier flight. Boeing rose 1.1 percent to $377.59 at 12:03 p.m. in New York. The company’s market value tumbled about $28 billion through Tuesday after the Ethiopian Airlines crash.
The safety system, designed to keep planes from climbing too steeply and stalling, has come under scrutiny by investigators of the crash as well as a subsequent one less than five months later in Ethiopia. A malfunctioning sensor is believed to have tricked the Lion Air plane’s computers into thinking it needed to automatically bring the nose down to avoid a stall.
Boeing’s 737 Max was grounded March 13 by U.S. regulators after similarities to the Oct. 29 Lion Air crash emerged in the investigation of the March 10 crash of Ethiopian Airlines Flight 302. In the wake of the two accidents, questions have emerged about how Boeing’s design of the new 737 model were approved.
The Transportation Department’s inspector general is conducting a review of how the plane was certified to fly and a grand jury under the U.S. Justice Department is also seeking records in a possible criminal probe of the plane’s certification.
The FAA last week said it planned to mandate changes in the system to make it less likely to activate when there is no emergency. The agency and Boeing said they are also going to require additional training and references to it in flight manuals.
“We will fully cooperate in the review in the Department of Transportation’s audit,” Boeing spokesman Charles Bickers said in an email. The company has declined to comment on the criminal probe.
After the Lion Air crash, two U.S. pilots’ unions said the potential risks of the system, known as the Maneuvering Characteristics Augmentation System, or MCAS, hadn’t been sufficiently spelled out in their manuals or training. None of the documentation for the Max aircraft included an explanation, the union leaders said.
“We don’t like that we weren’t notified,’’ Jon Weaks, president of the Southwest Airlines Pilots Association, said in November. “It makes us question, ‘Is that everything, guys?’ I would hope there are no more surprises out there.’’
Following the Lion Air crash, the FAA required Boeing to notify airlines about the system and Boeing sent a bulletin to all customers flying the Max reminding them how to disable it in an emergency.
Authorities have released few details about Ethiopian Airlines Flight 302 other than it flew a “very similar” track as the Lion Air planes and then dove sharply into the ground. There have been no reports of maintenance issues with the Ethiopian Airlines plane before its crash.
If the same issue is also found to have helped bring down Ethiopian Airlines Flight 302, one of the most vexing questions crash investigators and aviation safety consultants are asking is why the pilots on that flight didn’t perform the checklist that disables the system.
“After this horrific Lion Air accident, you’d think that everyone flying this airplane would know that’s how you turn this off,” said Steve Wallace, the former director of the U.S. Federal Aviation Administration’s accident investigation branch.
The combination of factors required to bring down a plane in these circumstances suggests other issues may also have occurred in the Ethiopia crash, said Jeffrey Guzzetti, who also directed accident investigations at FAA and is now a consultant.
“It’s simply implausible that this MCAS deficiency by itself can down a modern jetliner with a trained crew,” Guzzetti said.
MCAS is driven by a single angle-of-attack sensor near the nose even though there are two of the sensors on the plane. Boeing is planning to alter the system to rely on both sensors to reduce the chances of a malfunction.