2015 Seville Airbus A400M crash

Jump to navigation Jump to search
2015 Seville A400M crash
A400M-1969.jpg
The second prototype of the Airbus A400M Atlas
Accident
Date9 May 2015 (2015-05-09)
SummaryMultiple engine failure during test flight
SiteLa Rinconada, Spain
37°22′00″N 5°59′40″W / 37.3667°N 5.9944°W / 37.3667; -5.9944Coordinates: 37°22′00″N 5°59′40″W / 37.3667°N 5.9944°W / 37.3667; -5.9944
Aircraft
Aircraft typeAirbus A400M Atlas
OperatorAirbus Defence and Space
Call signCASA423
RegistrationEC-403
Flight originSeville Airport, Spain
Occupants6
Crew6
Fatalities4
Injuries2
Survivors2

On 9 May 2015, an Airbus A400M Atlas cargo plane on a test flight crashed at La Rinconada, Spain, less than 5 kilometres (3.1 mi) from Seville Airport at around 1:00 pm local time, killing 4 of the 6 crew.[1][2][3][4]

Aircraft[edit]

The aircraft, serial number MSN023, was on its first pre-delivery test flight and was scheduled to be the third A400M to be delivered to the Turkish Air Force.[1][2] The delivery was scheduled for June 2015.[5] The aircraft, number MSN23,[6] was being flown by an Airbus Defence and Space test crew[4][7][8] and used the callsign CASA423.[9] As of May 2015, Airbus had delivered just 12 of the 174 ordered and the programme had been plagued by persistent quality issues, both in the final assembly facility in Spain, and in Germany.[10]

Flight[edit]

The pilots had reported that the plane had a technical fault and asked permission to land, but hit an electricity pylon while attempting an emergency landing.[11] Tracking data from the Flightradar24 website indicated the plane had veered to the left before coming down and that it had reached a maximum altitude of 1,725 feet (526 m) before descending at a constant speed of about 160 knots (300 km/h; 180 mph).[12]

The six aircraft crew were Spanish employees of Airbus Defence and Space. Four of them were killed and the remaining two were seriously injured. Three local men helped the two survivors, a mechanic and an engineer, escape from the wreckage.[13]

Aftermath[edit]

San Pablo Airport was closed following the accident.[7] The Royal Air Force "temporarily paused" flying its two Atlas cargo planes as a result of this accident.[14] The German, Malaysian, and Turkish air forces suspended operations of their fleets of A400Ms following the accident.[15][16] The French Defence Minister, Jean-Yves Le Drian, said on 10 May 2015 that "only flights of extreme importance for operations will be allowed."[10] One of Britain's A400Ms is reportedly stuck in New Mexico awaiting the lifting of the British defense ministry's self-imposed flight pause.[17] Spain has withdrawn Airbus' permit to conduct flight tests of the A400M in Spain pending the results of the investigation.[18] In a letter to employees on 11 May 2015, Airbus chairman Tom Enders said, "We want to show our clients and air forces that we are fully confident in this excellent transport plane." Testing of the A400 resumed the next day, with Fernando Alonso, head of Airbus Military, on board the test flight acting as a flight engineer. The flight was not affected by Spain's halt on test flights because the Airbus owned prototype test plane, MSN4, is not scheduled for delivery.[18][19]

About twenty A400Ms are currently[when?] on the Seville assembly line in different stages of production, each of which will have to undergo testing before they can be delivered to clients. Airbus said on 12 May 2015, "It is too early to know what impact [Spain's] decision will have on the supply chain."[18][19] A400M MSN4 will be used to complete the development of new capabilities through the Standard Operating Clearances process; SOC1.5 will finalise aerial delivery, cargo-handling systems, self-defense systems, and air-to-air refueling using wing-mounted pods.[20]

On 14 May 2015, the Spanish Defense Ministry confirmed that Spain's military air crash investigation agency, CITAAM, had taken charge of the investigation of the crash. The Spanish government had initially charged a civilian team, made up of experts from the transport and defense ministries, with the task, but the civilian team "took the decision to withdraw because they understood that the plane has specific characteristics due to its military configuration which they were unfamiliar with," according to a Defense Ministry spokesman.[13]

On 19 May 2015, Airbus Defense and Space requested all operators of its A400M airlifter to conduct one-time specific checks on electronic control units (ECUs) fitted to the TP400 turboprop engines on the aircraft.[21] The company also has introduced additional detailed checks, to be carried out in the event of subsequent engine or ECU replacement. Airbus said these checks were necessary to "avoid potential risks in any future flights," and added that the alert had resulted from its internal analysis and was issued as "part of the continued airworthiness activities, independently from the ongoing official investigation into the accident."[17]

On 21 May 2015 it emerged that the secretaries of state of the A400M member countries had established a Program Monitoring Team (PMT) to analyze and judge Airbus plans to bring the A400M project back on track and to schedule visits to the final-assembly line in Seville, Spain, and other A400M-production facilities. The first conclusions on program recovery made by the PMT include the observation that Airbus still does not have an integrated approach to production, development and retrofits, but treats these as separate programs.[22]

On 11 June 2015, Spain's Ministry of Defense announced that Airbus could restart test flights for A400M prototypes in Spain. The Ministry confirmed that its specialist aerospace unit had met with Airbus to discuss flight permits, and that further permits relating to the plane program could be granted in the coming days.[23] The UK Royal Air Force lifted its suspension on A400M flights on 16 June 2015, followed the next day by the Turkish Air Force. "Having undertaken and completed a series of thorough checks on the UK's A400M aircraft and how it is operated, the RAF is now satisfied that the additional processes and procedures introduced means it is now safe for the RAF to resume flying," the UK Ministry of Defence said.[24] The first German Air Force A400M to fly post crash took off from Wunstorf air base on July 14, 2015. Pilot Lt.Col. Christian Schott, part of Wunstorf's 10-strong operational testing and evaluation team, said, "the problems that led to the crash in Seville can be been [sic] ruled out for our A400M...our aircraft has been thoroughly checked."[25]

The first production-standard aircraft to leave the Seville final assembly line (FAL), since the grounding was enacted by the Spanish authorities on 9 May, was delivered to the French Air Force on the same day that the suspension of flight was lifted on 19 June. This aircraft, MSN019, is the seventh to be delivered to France and the 13th to be delivered in all. The FAL has also completed the build of four aircraft for the United Kingdom, which will now undergo pre-delivery checks and trials before being flown to Royal Air Force (RAF) Brize Norton in Oxfordshire.[26]

Investigation[edit]

The Spanish government confirmed on 10 May 2015 that the plane's flight data recorder and cockpit voice recorder had been recovered.[27] Despite being examined by a joint team from the Spanish ministries of development and defense, the Spanish authorities subsequently passed the recorders to the French military air accident investigation agency BEAD to extract and analyze the data. On 13 May 2015 it emerged that technical issues were slowing retrieval of the crash data; General Bruno Caïtucoli, head of BEAD, reported that "there are technical issues in reading the system, and it is a question of compatibility between systems, so we are still trying to extract data. The extracting system we are using belongs to the French defense procurement agency DGA," Caïtucoli said, noting that the problem appeared to be a compatibility issue between the recorders and the DGA's data reading system, rather than an issue with the condition of the recorders themselves.[28]

Several reports suggested that as many as three of the aircraft's four engines failed during the A400M's departure from Seville.[29] Airbus initially focused on whether the crash was caused by new management software for the engine-fuel supply, designed to trim the fuel tanks to permit the aircraft to fly certain military maneuvers. There appeared to have been a trimming issue, leading to strong banking that was not recoverable and that the fuel supply was re-established, but not quickly enough for recovery to safe flight.[17]

Airbus Chief Strategy Officer Marwan Lahoud confirmed on 29 May that incorrectly installed engine control software caused the fatal crash. "The black boxes attest to that there are no structural defects [with the aircraft], but we have a serious quality problem in the final assembly."[30] Two days earlier, Airbus CEO Tom Enders criticized Spanish agencies for withholding the flight recorder data. "We would like to see the data and compare it with our hypothesis and proceed quickly to understand the causes of accident, so our aircraft can get back into the air," he told shareholders at the company's annual general meeting in Amsterdam on May 27.[31][32]

Senior Airbus executive, Fabrice Bregier, said on 30 May 2015 that there was "either a weakness in the test procedure of planes before they fly, or a problem that results from the implementation of these procedures."[33] On 3 June 2015 Airbus announced that investigators had confirmed "that engines one, two and three experienced power frozen [sic] after lift-off and did not respond to the crew's attempts to control the power setting in the normal way. Preliminary analyses have shown that all other aircraft systems performed normally and did not identify any other abnormalities throughout the flight."[33] The key scenario being examined by investigators is that the torque calibration parameter data was accidentally wiped on three engines as the engine software was being installed at Airbus facilities, which would prevent the FADECs from operating. Under the A400M's design, the first warning pilots would receive of the engine data problem would be when the plane was 120 meters (400 feet) in the air; on the ground, there is no cockpit alert.[34]

References[edit]

  1. ^ a b Gayle, Damien; Feeney, David. "Spanish air force cargo plane crashes near Seville airport". The Guardian. Retrieved 9 May 2015.
  2. ^ a b "UPDATE NR1 – Accident A400M in Seville". airbusdefenceandspace.com. Archived from the original on 2015-05-11. Retrieved 2015-05-09.
  3. ^ "Airbus military plane crashes near Spain's Seville airport". BBC News Online. Retrieved 9 May 2015.
  4. ^ a b Teresa López Pavón (9 May 2015). "Cuatro muertos tras estrellarse un avión militar A-400M en pruebas junto al aeropuerto de Sevilla". El Mundo. Retrieved 9 May 2015.
  5. ^ "Spanish air force cargo plane on test flight crashes near Seville airport". The Guardian. Retrieved 10 May 2015.
  6. ^ Osborne, Tony (9 May 2015). "Airbus A400M Crashes During Test Flight". Aviation Week & Space Technology. Archived from the original on 1 April 2018. Retrieved 26 October 2018.
  7. ^ a b "At least three dead after military plane crash in Spain". Irish Times. Retrieved 9 May 2015.
  8. ^ "Seville airport closed after military transport plane crashes" The Independent, 9 May 2015.
  9. ^ "CASA423 – Private – Aircraft info and flight history – Flightradar24". flightradar24.com.
  10. ^ a b "Spanish minister defends European aviation after Airbus crash". The Financial Times. Retrieved 11 May 2015.
  11. ^ "Airbus A400M military transporter crashes on test flight, killing four". Reuters. Retrieved 9 May 2015.
  12. ^ "Airbus A400M Transport Plane Crashes in Spain". Wall Street Journal. Retrieved 9 May 2015.
  13. ^ a b "Spanish Air Force Takes Over Airbus A400M Crash Probe". Defense News. Retrieved 15 May 2015.
  14. ^ "Military Plane Crashes During Seville Test Flight". Sky News. 9 May 2015. Retrieved 9 May 2015.
  15. ^ "Germany grounds Airbus A400M after Spain crash". Reuters.
  16. ^ "Black Boxes of Crashed A400M Plane Found, Aircraft Grounded". Retrieved 2015-05-10.
  17. ^ a b c "Software Cut Off Fuel Supply In Stricken A400M". Aviation Week. Retrieved 19 May 2015.
  18. ^ a b c "Spain withdraws permit for Airbus A400M test flights". www.apnewsarchive.com. Retrieved 2015-05-12.
  19. ^ a b "Airbus Holds First A400M Test Flight Since Crash". Defense News. Retrieved 12 May 2015.
  20. ^ "A400M Crash Adds To Airlifter Program's Woes". Aviation Week. Retrieved 14 May 2015.
  21. ^ "Airbus urges extra tests on A400M". Financial Times. Retrieved 20 May 2015.
  22. ^ "A400M Countries Form Monitoring Team, Germany Warns Of Airlift Gap". Aviation Week. 21 May 2015.
  23. ^ "Airbus can restart A400M test flights in Spain after crash: Defense Ministry". Reuters. 11 June 2015.
  24. ^ "Airbus hoping to resume A400M deliveries". Financial Times. 17 June 2015.
  25. ^ "German A400M Airborne Again". Aviation Week. 14 July 2015.
  26. ^ "Airbus resumes A400M customer deliveries". IHS Jane's 360. 22 June 2015.
  27. ^ "Heroic Spanish farmer dragged survivors out of Seville plane crash". The Daily Telegraph. Retrieved 11 May 2015.
  28. ^ "Tech Issues Slow Retrieval Of A400M Crash Data". Aviation Week. Retrieved 13 May 2015.
  29. ^ "A400M Crash Adds To Airlifter Program's Woes". Aviation Week. Retrieved 15 May 2015.
  30. ^ Chirgwin, Richard (2015-05-31). "Airbus confirms software brought down A400M transport plane". The Register. Retrieved 2016-02-20.
  31. ^ "Incorrectly Installed Engine Software Caused A400M Crash, Airbus Official Says". Aviation Week. 27 May 2015.
  32. ^ Leo Kelion (10 June 2015). "Fatal A400M crash linked to data-wipe mistake". BBC. Retrieved 10 June 2015.
  33. ^ a b "Airbus Says 3 of 4 Engines Failed in Spain A400M Crash". Defense News. 27 May 2015.
  34. ^ "A400M probe focuses on impact of accidental data wipe". Reuters. Retrieved 9 June 2015.

External links[edit]