Aeroméxico Connect Flight 2431

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Aeromexico Connect Flight 2431
Aeroméxico Connect E190 XA-GAL approaching KJFK.jpg
XA-GAL, the aircraft involved, 2017
Accident
Date31 July 2018
SummaryLoss of control on takeoff due to low altitude windshear
SiteDurango, Mexico
24°08′16.71″N 104°31′02.46″W / 24.1379750°N 104.5173500°W / 24.1379750; -104.5173500Coordinates: 24°08′16.71″N 104°31′02.46″W / 24.1379750°N 104.5173500°W / 24.1379750; -104.5173500
Aircraft
Aircraft typeEmbraer 190AR
OperatorAeroméxico Connect
IATA flight No.5D431
ICAO flight No.SLI2431
Call signCostera 2431
RegistrationXA-GAL
Flight originDurango International Airport
DestinationMexico City International Airport
Occupants103
Passengers99
Crew4
Fatalities0
Injuries39
Survivors103 (all)

Aeroméxico Connect Flight 2431 (SLI2431/5D2431) was a Mexican domestic scheduled passenger flight bound for Mexico City that crashed on takeoff from Durango International Airport on 31 July 2018. Shortly after becoming airborne, the plane encountered sudden wind shear caused by a microburst. The plane rapidly lost speed and altitude and impacted the runway, detaching the engines and skidding to a halt about 1,000 feet (300 m) beyond the runway. The plane caught fire and was destroyed. All 103 people on board survived. 39 passengers and crew were injured.

A final report on the crash was released on 23 February 2019. Investigators found that the primary cause of the accident was adverse weather conditions encountered by the flight, and contributing factors included crew error, air traffic controller error, and the lack of equipment that could detect wind shear conditions at airports. Investigators determined that an unauthorized student pilot in the cockpit who was flying the plane during the takeoff caused the crew to be distracted, leading to a loss of situational awareness. The crew failed to react to dangerous weather conditions that were developing, and did not notice irregularities in the airspeed indicators that could have alerted them to potential hazards. The sole air traffic controller on duty at the airport at the time also failed to notify the aircraft of rapidly deteriorating weather conditions.

The accident and the subsequent investigation led to changes in Mexican aviation regulations to prevent non-assigned crew members from being present in the cockpit of an aircraft at any time during a flight. Investigators also made several recommendations for changes in flight crew and air traffic controller training, and to improve the capabilities of weather detection equipment in place at airports to improve overall aviation safety.

Accident[edit]

The flight, number 2431, was operated by Aeroméxico Connect and was a regularly scheduled flight from Durango International Airport to Mexico City International Airport.[1][2] Originally scheduled to leave at 2:56 pm Central Time (UTC−06:00), the departure was slightly delayed when the first officer observed a fuel leak from the number one engine and asked maintenance crews to investigate, who eventually concluded that the rate of leakage was within safe limits.[3](p9) The aircraft left the gate at 3:14 pm and proceeded to taxi to the end of runway 03. The pilot commented to the copilot that it had started to rain.[3](p10) As the plane taxied, the intensity of the rain increased and there were strong gusts of wind.[3] At 3:18 pm, the air traffic controller reported 20 knot winds from 90 degrees.[3](pp11,30) The flight information service for the airport published an updated weather report at 3:18 indicating the presence of thunderstorms and rain, reduced visibility, and the presence of cumulonimbus clouds. The air traffic controller did not see this update because he was working alone and was attending to Flight 2431.[3](p30) The rain became so heavy that the tower could not see the runway.[4] Even though the controller was in the best position to see the deteriorating weather conditions, he did not inform the aircraft about any of his observations.[4] The flight was cleared for takeoff at 3:21pm. Severe wind gusts caused several trees to become uprooted at the airport, knocking down power and communication lines.[4] A special weather update was sent out by the flight information service at 3:22 pm warning of thunderstorms and rain, 0 feet of visibility and a decrease in the ceiling to 0 feet, but this report was never received by the tower controller due to the power outage.[3](p30)

The aircraft proceeded down the runway. When it reached a speed of 147 knots, the pilot flying the plane rotated the controls to bring the aircraft airborne, and raised the gear when the craft was 2 feet above the runway.[3](p11)[4] The plane began its takeoff with a headwind, but the winds quickly shifted to a right crosswind of 11 knots, increasing to 33 knots as the plane proceeded down the runway.[4] The plane had reached its maximum altitude of about 30 feet (9 m) and a maximum indicated airspeed of 151 knots when the wind direction suddenly shifted to a 24-knot tailwind. The plane rapidly lost airspeed and altitude, and an audible alarm of "DON'T SINK" sounded in the cockpit.[4][3](p29) Five seconds later, the left wing struck the runway, and both engines broke away from the wings.[5] The plane skidded off the runway and came to rest about 1,000 feet (300 m) beyond the end of the runway.[5][6] All 103 people on board the plane were able to evacuate and survived the crash before a fire broke out that destroyed the aircraft.[7][1]

Aircraft[edit]

The aircraft was an Embraer 190, registration XA-GAL, msn 19000173. It was first delivered in 2008.[6] It was first delivered to US Airways as N960UW before being sold to Republic Airways Holdings in 2009. Under Republic Airways ownership, the aircraft was re-registered as N167HQ, operating for Midwest Airlines, a former subsidiary of Republic, and later for fellow Republic subsidiary (at the time) Frontier Airlines, until late 2013. After Republic retired its Embraer 190 aircraft from its operations, Republic then leased N167HQ to Aeroméxico Connect in 2014, who registered the aircraft as XA-GAL. At the time of its loss, the aircraft had flown a total of 27,257 hours, and had 18,200 takeoff and landing cycles.[6][3](p22)

When it was originally manufactured, the aircraft was equipped with a Honeywell WU-880 weather radar. This system can detect storms along the flight path of the aircraft and give pilots a visual indication of the intensity of the storm.[3](p27) The aircraft was also equipped with a wind shear detection and escape guidance system that can detect wind shear conditions and alert the pilots using a combination of visual and audio alarms. The audio alarms are disabled in the event of a higher priority audio alarm, such as the ground proximity sensor alarm.[3](pp27–29)

Crew[edit]

The pilot of the flight was 38-year-old Carlos Galván Meyran, a resident of Mexico City.[8][9][10] He held an ATPL license and had been working at Aeroméxico since 2010, as a pilot since 2011.[3](p18)[9] He had a total of 3,700 logged flight hours at the time of the crash.[3](p18) Galván completed his captain training for the Embraer E-Jet series in June 2017 and had logged 1,064 hours in the type.[3](p18) He occupied the left-hand seat in the cockpit during the flight, and suffered serious injuries in the accident, requiring hip and spine surgery which doctors called successful.[4][11][10]

The assigned first officer, Daniel Dardon Chávez, held an ATPL license and had a total of 1,973 logged flight hours, including 460 hours on the Embraer 190 aircraft.[4][10] He was 25 years old at the time of the accident and was originally from Metepec, State of Mexico.[12] He had become certified to copilot this type of aircraft in February 2018.[3](p19) He received minor injuries in the crash. During the flight, he was occupying the jump seat in the back of the cockpit instead of the right-hand seat normally occupied by the first officer.[4][3](p20)

Another pilot who flew for the airline, José Ramón Vázquez, was also in the cockpit.[10] He held a Commercial pilot license and had a total of 3,296 logged flight hours. He was certified to fly the Beechcraft King Air F90 and Beechcraft Super King Air 200 aircraft. He was in the process of receiving training to fly the E-Jets, but as of the time of the flight, he had only received initial classroom instruction, and had completed 64 hours of simulator time, and had not yet received his certification.[3](p20)[4] At the time of the flight, he occupied the right-hand seat in the cockpit normally occupied by the copilot, and was the pilot flying the plane until the last five seconds before the crash.[4][3](p21) He received minor injuries in the crash.[4]

Two female flight attendants were in the main cabin. The senior flight attendant had been employed since June 2012 and suffered a fractured lumbar vertebra.[3](p21) The junior flight attendant had been employed for about a week and received minor injuries in the crash.[4][3](p21)

Passengers[edit]

The plane departed with 99 passengers and four crew members.[3](p15) Two of the passengers were airline employees being shuttled between locations, including the pilot in training who was in the cockpit. Of the passengers, excluding the pilot in training, 31 were Mexican citizens, 65 were United States citizens, one was a Spanish citizen, and one was a Colombian citizen.[3](p15)

Aftermath[edit]

Immediately after the crash, passengers reported seeing smoke and flames as they rushed to escape the plane.[11] Some passengers said that a door had been torn off and that plane's fuselage had broken in two, allowing them to jump directly out of a gap in the side of the aircraft.[7] The crew was able to open the emergency exit slides and safely evacuate all of the occupants within 90 seconds. About 3 to 4 minutes after coming to a stop, and after all passengers had been evacuated, the aircraft exploded and was engulfed in flames.[13][14][4] The air traffic controller attempted to contact the aircraft, and when it received no response he contacted the approach sector controller to see if they were in contact with the aircraft.[4] The controller dispatched an airport service vehicle to inspect the runway. The driver saw the aircraft's engines at the side of the runway and smoke rising from beyond the runway.[4] Airport officials activated the emergency operation center at the airport, and dispatched firefighters to assist with the rescue and to extinguish the fire.[11][15]

After reports about the crash came in, Aeroméxico sent a team to Durango to provide assistance to affected passengers and their families. The company announced that it would cover all medical, accommodation, transportation, and incidental expenses resulting from the crash.[16] It praised the actions of the crew and said that the crew's quick and efficient evacuation of the plane was instrumental in avoiding additional serious injuries and fatalities.[17] It also said that the pilot's expertise and professionalism had prevented the loss of life in the accident.[18]

Different sources gave conflicting reports about the number of injuries from the incident. The Ministry of Health initially reported that there were 18 passengers injured.[19] The Red Cross said there were 97 injuries.[19] The governor of Durango told media that 49 people had been treated for injuries at hospitals.[13] Two days after the crash, Aeroméxico reported that 17 passengers were still hospitalized, 16 were in the process of being released, and 24 had already been released from medical care.[20] The final official accident report stated that there were 14 serious injuries and 25 minor injuries.[3](p15)

About a month after the crash, Aeroméxico announced that the three pilots who were in the cockpit that day had been fired from the company. It said that while it did not feel that the crash was the fault of the pilots, they had violated company procedures by not following their assigned roles during the flight by allowing the trainee pilot to take control of the aircraft.[10] The labor union representing the pilots protested the termination, saying that the decision was carried out based only on a preliminary accident report, and that a full investigation into the accident was still ongoing.[10] Shortly afterward, Mexico's Directorate General of Civil Aeronautics (DGAC) issued a change in regulations that prohibited airlines from allowing inactive pilots and flight attendants from flying in the cockpit of aircraft.[21][22] Aeroméxico pilots opposed this change and called for a strike, viewing the sudden removal of a travel benefit as a violation of their collective bargaining agreement between the union and the airline.[23][21]

Investigation[edit]

Illustration of a microburst. The air moves in a downward motion until it hits ground level. It then spreads outward in all directions.

Shortly after the crash, the DGAC announced that it had formed commission to investigate the crash.[4] The commission received assistance from the US National Transportation Safety Board and the US Federal Aviation Administration. Additional assistance was provided by Embraer SA, who had built the aircraft, and General Electric Co., who had built the engines on the aircraft.[24] Investigators quickly located the flight data recorders for the aircraft and found them to be in perfect condition.[25]

On 5 September, a little over a month after the accident, José Armando Constantino Tercero, the lead investigator from the DGAC, announced that the final conclusion had not yet been reached, but that the cause of the accident appeared to be sudden wind shear from a microburst. He said that the pilots had not received any notice of the adverse conditions prior to starting the takeoff, and that neither human nor mechanical failure appeared to be to blame for the crash.[26][18] He also said that analysis of the cockpit voice recorder revealed that an unauthorized pilot training was taking place during the flight, and that the trainee pilot had been occupying the copilot seat and flying the plane until shortly before the crash.[26] This was not in accordance with aviation regulations, and he said that administrative proceedings had been initiated.[18] Nevertheless, he stressed that neither the presence nor the actions of any of the pilots caused the accident.[18] Shortly afterward, the airline announced that it had fired the three pilots who were in the cockpit of the flight.[10]

The investigators conducted a series of flight tests in full flight simulators in Mexico and Brazil using the same weather conditions that existed at the time of the flight, with crews with similar levels of experience as the crew of Flight 2431.[3](p51) The simulator crews were not given advance notice of the situation that they were about to encounter.[3](p51) In one situation, the flight crew turned on the weather radar, recognized the signs of wind shear from the variations and visual cues on the instruments, and successfully aborted the takeoff. In a second scenario, the wind shear weather conditions were not loaded into the simulator until after the takeoff roll had started. In that case, the simulated flight reached a maximum altitude of about fifteen feet before losing altitude and impacted the ground with the landing gear. The simulator group concluded that because the crew did not notice the presence of wind shear during the takeoff, they could not have been unable to recover the aircraft in time to avoid the accident.[3](pp51–52)

Final report[edit]

On 23 February 2019, the final report was released in Spanish only. It concluded that the accident was caused by "impact with the runway caused by a loss of control of the airplane during the final phase of takeoff as a result of wind shear at low altitude which caused a loss of speed and altitude."[4][3](p66)[27] The investigation found no mechanical malfunctions in the aircraft that led to the accident.[3](p64)

The investigation identified contributing factors to the accident caused by the flight crew. One factor was that the pilot of the plane, who was not a certified instructor, was giving an instruction to a student pilot who was flying the plane at the time. This caused a loss of situational awareness and the pilots did not maintain a "sterile cockpit", one that was free from distractions. It found that among other mistakes, the pilot and the student pilot failed to notice that the airspeed indicator on the pilot's side was giving different information than the airspeed indicator on the copilot's side, which could have provided information about the dangerous weather conditions at the time. Additionally, it found that the pilots failed to follow standard operating procedures during the flight, including configuring the aircraft for the weather conditions that it encountered immediately before and during the takeoff.[3](p66)[4][27]

The investigation also identified contributing factors from the air traffic controller. It said that the tower controller failed to follow proper procedures that were in place for when the weather conditions created the possibility of low altitude wind shear. It faulted the controller for failing to inform the departing flight about the rapidly deteriorating visibility and changes in wind speed and direction, and it said that the controller did not have adequate supervision and assistance in the air traffic control tower.[3](p66)[4]

The investigation made several recommendations to the airline to prevent similar accidents from happening in the future. It said that the airline make should changes to its operating procedures to prevent a person who is not an assigned crew member from taking the controls of the aircraft during any phase of that flight. It recommended additional training to air crews on sterile cockpit procedure, to ensure that crews are able to maintain full awareness of the aircraft and external conditions. It also recommended additional training on how to recognize potential wind shear situations in storms and how to address those situations during flight. It recommended training on the use of maximum thrust during takeoff, the verification of the aircraft configuration for the current weather conditions, and the active monitoring of airspeed, altitude, and vertical speed instruments during takeoff. It recommended changes to procedures to identify and resolve situations where there is a disagreement between flight instruments, and procedures for establish a safe altitude before for raising the landing gear. Because the commission found that incorrect barometric pressures had been entered into the flight control computer of the aircraft, it recommended additional care be exercised by flight crews in keeping track of the information that it receives from air traffic control to guarantee that the information used for the flight is correct. The third pilot had been listed as a passenger, but his absence from the passenger compartment had not been noted the flight attendants. The commission recommended that the airline revise its cabin crew operating procedures to identify and address situations where passengers are not in their expected place on the plane.[3](pp67–69)[27]

The commission also made recommendations to the airport operator and to the Mexican civil aviation agency. It said that the air traffic controllers should not operate alone and that there should be additional personnel to receive and communicate adverse weather conditions to aircraft. It found that the DGAC had not published guidelines on how to recognize wind shear situations, or the hazards of wind shear in different types of storms, so it recommended that the DGAC develop a program to identify and classify the level of risk in storms. It also found that the airport did not have equipment to detect the presence of wind shear, so it recommended that the agency implement a program to install facilities to detect variations in the longitudinal, lateral, and vertical direction of winds so that they can be included in navigational aids. It recommended that airports identify and eliminate risks that can interrupt power, voice communications, and data communications in the control towers. Finally, the investigation found that CCTV cameras that had been installed at the airport were helpful during the investigation, but it was hampered by the lack of time stamps on the video, so it recommended that all cameras in place at airports include time stamps on the recordings.[3](pp69–71)

References[edit]

  1. ^ a b Darrah, Nicole (July 31, 2018). "Aeromexico jet crashes after takeoff in northern Mexico, officials say". Fox News. Retrieved July 31, 2018.
  2. ^ News, A. B. C. "85 injured after Aeromexico plane crashes at airport, officials say". ABC News. Retrieved August 1, 2018.
  3. ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af "Informa Final de Accidente, Exp. No. ACCDTAFA034/2018MMDO" [Final Accident Report, Exp. No. ACCDTAFA 034/2018 MMDO] (pdf) (in Spanish). Secretaría de Comunicaciones y Transportes. February 23, 2019. Retrieved March 15, 2019.
  4. ^ a b c d e f g h i j k l m n o p q r s t Hradecky, Simon (February 25, 2019). "Accident: Aeromexico Connect E190 at Durango on Jul 31st 2018, veered off and overran runway after failed takeoff and burst into flames". The Aviation Herald. Retrieved March 15, 2019.
  5. ^ a b Saunders, Thomas (February 26, 2019). "AM2431 Durango Crash: Pilot in Control Unqualified". Airways Magazine. Airways International, Inc. Retrieved March 15, 2019.
  6. ^ a b c "XA-GAL accident description". Aviation Safety Network. Retrieved August 1, 2018.
  7. ^ a b "Mexico plane crash: All 103 people on board survive". BBC News. Retrieved August 1, 2018.
  8. ^ Valadez, Roberto (August 3, 2018). "Por avionazo, 11 pasajeros siguen hospitalizados" [By plane, 11 passengers are still hospitalized]. Milenio (in Spanish). Retrieved March 15, 2019.
  9. ^ a b "Conoce a Carlos Galván, el piloto de Aeroméxico que salvó a 102 personas" [Meet Carlos Galván, the Aeroméxico pilot who saved 102 people]. Mundo Hispánico (in Spanish). Mundo Hispano Digital Network. August 1, 2018. Retrieved March 15, 2019.
  10. ^ a b c d e f g Cantera, Sara (September 7, 2018). "Aeroméxico despide a los tres pilotos del avión accidentado" [Aeroméxico dismisses the three pilots of the crashed plane]. El Universal (in Spanish). Retrieved March 21, 2019.
  11. ^ a b c Neuman, Scott (August 1, 2018). "Jetliner In Mexico Crashes, Catches Fire, But All 103 Aboard Escape". NPR.org. National Public Radio , Inc. Retrieved March 21, 2019.
  12. ^ Soto, Araceli (August 1, 2018). "Daniel Dardon, héroe de Aeroméxico, originario de Metepec, Edomex" [Daniel Dardon, hero of Aeroméxico, originally from Metepec, Edomex]. DigitalMex (in Spanish). Retrieved March 22, 2019.
  13. ^ a b "Aeroméxico plane with 101 aboard crashes in Durango; no deaths reported". NBC News. Retrieved August 1, 2018.
  14. ^ "Investigadores revelan una de las posibles causas del accidente aéreo de Aeroméxico" [Researchers reveal one of the possible causes of the Aeromexico air crash]. infobae (in Spanish). September 8, 2018. Retrieved March 22, 2019.
  15. ^ RR (July 31, 2018). "Se estrella un Embraer de Aeroméxico con 103 personas" [Embraer of Aeroméxico crashes with 103 people]. Reportur.com (in Spanish). Retrieved March 22, 2019.
  16. ^ Valadez, Roberto (August 1, 2018). "Aeroméxico cubrirá todos los gastos por accidente de avión" [Aeromexico will cover all expenses for plane crash]. Milenio (in Spanish). Retrieved March 15, 2019.
  17. ^ "Comunicado #4: AEROMÉXICO CONTINÚA ATENDIENDO A LOS PASAJEROS DEL VUELO AM2431 Y SUS FAMILIARES EN DURANGO" [Press Release #4: AEROMEXICO CONTINUES TO SERVE PASSENGERS OF FLIGHT AM2431 AND HIS FAMILIARS IN DURANGO] (PDF) (in Spanish). AeroMéxico. August 1, 2018. Retrieved March 21, 2019.
  18. ^ a b c d "La investigación del accidente de Aeroméxico en Durango descarta el fallo humano o mecánico" [Aeromexico accident investigation in Durango rules out human or mechanical failure]. El País (in Spanish). September 6, 2018. Retrieved March 23, 2019.
  19. ^ a b Villamil, Jenaro (July 31, 2018). ""Oportuna actuación de tripulación y pasajeros evitó pérdida de vidas humanas": Aeroméxico" ["Timely performance of crew and passengers prevented loss of human life"]. Proceso.com.mx (in Spanish). Retrieved March 21, 2019.
  20. ^ "Comunicado #5: Aeromexico Informa" [Statement #5: Aeromexico Reports] (PDF) (in Spanish). AeroMéxico. August 2, 2018. Retrieved March 21, 2019.
  21. ^ a b Cantera, Sara (September 12, 2018). "Aeroméxico y pilotos chocan por prestación" [Aeroméxico and pilots clash for performance]. El Universal (in Spanish). Retrieved March 26, 2019.
  22. ^ "Circular Obligatoria CO AV-55/18" [Obligatory Circular CO AV-55/18] (PDF). gob.mx (in Spanish). September 10, 2019. Retrieved March 26, 2019.
  23. ^ "Aeroméxico pone nuevas reglas a pilotos y sobrecargos" [Aeroméxico sets new rules for pilots and flight attendants]. Chilango (in Spanish). September 11, 2018. Retrieved March 22, 2019.
  24. ^ Vazquez, Efrain (August 1, 2018). "Most passengers in non-fatal Mexican plane crash were U.S. citizens". Reuters. Retrieved August 2, 2018.
  25. ^ Rodriguez, Francisco (August 2, 2018). "Cajas negras de avión accidentado en perfecto estado, decen autoridades" [Black boxes of crashed plane in perfect condition, say authorities]. El Universal (in Spanish). Retrieved March 21, 2019.
  26. ^ a b "Clima Adverso Causó Accidente Aéreo en Durango, Determinan Autoridades" [Adverse Weather Caused Aerial Accident in Durango, Determine Authorities]. Reporte Indigo (in Spanish). September 5, 2018. Retrieved March 23, 2019.
  27. ^ a b c Valadez, Roberto (February 24, 2019). "Viento y piloto no autorizado, causas de accidente de Aeroméxico en Durango" [Wind and unauthorized pilot, causes of Aeromexico accident in Durango]. Milenio (in Spanish). Retrieved March 26, 2019.