EgyptAir Flight 804

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
EgyptAir Flight 804
File:EgyptAir Airbus A320 (SU-GCC) on finals at Ataturk Airport.jpg
The aircraft involved, pictured in 2011
Occurrence summary
Date 19 May 2016 (2016-05-19)
Summary Crashed, under investigation
Site Mediterranean Sea
Lua error in package.lua at line 80: module 'strict' not found.[lower-alpha 1][1]
Passengers 56
Crew 10
Fatalities 66 (all)
Aircraft type Airbus A320-232
Operator EgyptAir
Registration SU-GCC
Flight origin Charles de Gaulle Airport, Paris, France
Destination Cairo International Airport, Cairo, Egypt

EgyptAir Flight 804 (MS804/MSR804)[lower-alpha 2] was a scheduled international passenger flight from Paris Charles de Gaulle Airport to Cairo International Airport, operated by EgyptAir, which crashed into the Mediterranean Sea on 19 May 2016 at 02:33 Egypt Standard Time (UTC+2).

No mayday call was received by air traffic control, although signals that smoke had been detected in one of the aircraft's lavatories and in the avionics bay were automatically transmitted by ACARS shortly before the aircraft disappeared from radar. The cause of the disaster is under investigation.

There were 66 people on board: 56 passengers, 7 aircrew, and 3 security personnel. A multinational search and recovery operation is under way. Debris from the aircraft was found in the Mediterranean approximately 290 km (180 mi) north of Alexandria, Egypt. The search for the main wreckage is still in progress.

Aircraft

The aircraft involved was an Airbus A320-232,[lower-alpha 3] registration SU-GCC, MSN 2088.[2] It made its first flight on 25 July 2003, and was delivered to EgyptAir on 3 November 2003.[3] The aircraft's optical smoke detectors have been deemed more reliable than older models on Airbus aircraft, as they produced fewer false warnings, but were sensitive to dust and some aerosols.[4]

The flight was the aircraft's fifth that day, having flown from Asmara International Airport, Eritrea, to Cairo; then from Cairo to Tunis–Carthage International Airport, Tunisia, and back. The final completed flight of the aircraft before the crash was Flight MS803 to Paris.[5]

Flight

Flight route in green. The red star indicates where SU-GCC's ADS-B signal was lost, and the yellow line indicates MS804's remaining intended flightpath.
Flight speed (orange) and altitude (blue) from 20:30 to 00:30.

The aircraft departed for Cairo International Airport from Charles de Gaulle Airport on 18 May at 23:09 (all times refer to UTC+2, used in France and Egypt at the time).[6][7] It disappeared from radar while flying at flight level 370 (about 37,000 ft (11,300 m) in altitude) in clear weather, 280 km (170 mi; 150 nmi) north of the Egyptian coast,[8] and about the same distance from Kastellorizo, over the eastern Mediterranean on 19 May at 02:30.[9][10][11] The aircraft was lost 3 hours 25 minutes into the flight.[12]

The aircraft was due to land at 03:05. It was originally reported that a distress signal from emergency devices was detected by the Egyptian military at 04:26, two hours after the last radar contact; officials later retracted this statement.[13]

On the day of the crash, Panos Kammenos, the Greek defence minister, noted the aircraft changed heading 90 degrees to the left, then turned 360 degrees to the right while it dropped from Flight Level 370 to 15,000 feet (4,600 m).[14][15] This information was rejected on 23 May by an Egyptian official from the National Air Navigation Services Company, who stated that there was no change in altitude and no unusual movement before the aircraft disappeared from radar.[16] It is possible Egyptian radars were unable to track the aircraft as accurately as Greek radars due to their distance from the aircraft.[17]

Passengers and crew

Passengers

Fifty-six passengers from thirteen different countries were on board.[18] Three passengers were reported to be children, including two infants.[23] The passenger count was initially confused by the multiple citizenship status of some people on board.[22]

Crew

The crew of ten consisted of two pilots, five flight attendants, and three security personnel.[24] According to EgyptAir, captain Mohammed Shoukair had 6,275 hours of flying experience, including 2,101 hours on the A320, while first officer Ahmed Assem had 2,766 hours.[14][25]

Search and recovery efforts

Initial efforts

The Egyptian Civil Aviation Ministry confirmed that search and rescue teams were deployed to look for the missing aircraft. Search efforts are being carried out in coordination with Greek authorities. A spokesman for the Egyptian Civil Aviation Agency stated that the aircraft most likely crashed into the sea.[26] Greece sent a Lockheed C-130 Hercules, an Embraer EMB-145-H early warning aircraft and an Elli-class frigate to the area to participate in search and rescue efforts.[27] France is also sending ships and aircraft to assist with the search and rescue operation.[28][29] The United Kingdom sent the Royal Fleet Auxiliary ship RFA Lyme Bay to assist with search and rescue efforts.[30] The United States is providing a United States Navy Lockheed P-3C Orion to assist in the search for the aircraft.[31]

On 19 May, a Dassault Falcon 50 maritime patrol aircraft from the French Navy's squadron 24F was deployed in the area where the Egyptian Airbus was presumed to have crashed.[29]

Search area

On 20 May, the Egyptian Navy and Air Force discovered debris, body parts, passengers' belongings, luggage, and aircraft seats at the crash site, 290 km (180 mi; 160 nmi) off the coast of Alexandria, Egypt. Two fields of debris were spotted from the air between 20 May at dusk and 23 May at dawn; one of them was 3 nmi (3.5 mi; 5.6 km) in radius.[32] At this time, the searched area measured nearly 14,000 km2 (5,400 sq mi),[32] with the sea being 2,440 to 3,050 metres (8,000 to 10,000 ft) deep there.[33]

External image
image icon Slick detected by the ESA near site of disappearance

The European Space Agency announced on 20 May that it had possibly detected a 2 km-long fuel slick at Lua error in package.lua at line 80: module 'strict' not found., about 40 kilometres (25 mi) southeast of the last known location of Flight 804, on imagery captured by its Sentinel-1A satellite at 16:00 UTC on 19 May.[34]

On 26 May, it was reported that signals from the aircraft's emergency locator transmitter had been detected by satellite, which narrowed the area where the main wreckage is likely located on the ocean floor to within a five-kilometre (3.1-mile) radius. An emergency locator transmitter usually activates at impact to send a distress signal; the signals are not the signals from the flight recorders (black boxes).[35][36]

The U.S. National Oceanic and Atmospheric Administration confirmed that the emergency locator transmitter signal was received by satellites minutes after the airliner disappeared from radar.[37] A "distress signal" received 2 hours after the disappearance of the aircraft, possibly originating from the emergency locator transmitter, had been reported already on 19 May; this report was denied by EgyptAir.[38][39]

Flight recorders

On 22 May, an Egyptian remotely operated underwater vehicle (ROV) owned by the country's Oil Ministry was deployed to join the search for the missing plane. President Abdel Fattah el-Sisi stated that the ROV can operate at a depth of 3,000 metres (9,840 ft).[40][41][42] According to Egypt's chief investigator with the Civil Aviation Ministry, Ayman al-Moqadem, the ROV cannot detect signals from flight recorders (black boxes).[43]

A French Navy D'Estienne d'Orves-class aviso ship, the Enseigne de vaisseau Jacoubet, equipped with sonar that can pick up the underwater "pings" emitted by the underwater locator beacons of the flight recorders, arrived at the possible crash site on 23 May.[32][44] The French ship can deploy another ROV that can dive up to 1,000 metres (3,300 ft) and is able to detect signals from black boxes.[45]

On 26 May, Italian and French companies, including Deep Ocean Search and Alseamar, capable of executing deep-sea searches were asked by Egypt to help locate the flight recorders.[46]

Another French vessel – the naval oceanographic research ship Laplace – left the Corsican port of Porto-Vecchio for the search area on 27 May, according to the Bureau of Investigations and Analysis. The ship can deploy three towed hydrophone arrays made by Alseamar and designed to detect the beacons from a distance of up to nearly 4 km (2.5 miles). The ship was to begin searching for the flight recorder's signals within several days of arriving at the possible crash site.[47][48]

The John Lethbridge,[49] a vessel belonging to the Mauritius-based company Deep Ocean Search equipped with a remotely operated underwater vehicle that can detect signals in depths of up to 6,000 metres (20,000 ft), and map the seabed, was contracted by Egyptian authorities.[50][51] Capable of retrieving the black boxes from the seabed, it left the Irish Sea on 28 May and is expected to arrive at the area in 12 days (i.e. 9 June), after stopping in Alexandria to board Egyptian and French investigators.[52]

On 1 June, the Egyptian Civil Aviation Ministry reported that "pings" from an underwater locator beacon of one of the flight recorders had been detected by the Laplace.[49][53] This was confirmed by the French Bureau of Investigations and Analysis, whose spokesperson declared the establishment of a "priority search area".[53]

Early responses

The Egyptian Civil Aviation Ministry stated on 19 May that Flight 804 was probably attacked.[12][54] Two US officials believed the aircraft was downed by a bomb,[55] and a senior official said that monitoring equipment focused on the area at the time detected evidence of an explosion on board the aircraft; other officials from multiple US agencies said they had seen no evidence of an explosion in satellite imagery and another two intelligence officials stated there is nothing yet to indicate foul play.[56]

Investigation

According to Greek military radar data, Flight 804 veered off course shortly after entering the Egyptian flight information region. At Flight Level 370 (about 37,000 ft (11,300 m) in altitude), the aircraft made a 90-degree left turn, followed by a 360-degree right turn, and then began to descend sharply. Radar contact was lost at an altitude of about 10,000 ft (3,000 m).[57][58] This information was later denied on 23 May by an Egyptian official from the National Air Navigation Services Company, who stated there was no change in altitude and no unusual movement before the aircraft disappeared from radar.[16]

Greece's Ministry of National Defence is investigating the report of a merchant ship captain who, on 18 May, claimed to have seen a "fire in the sky" 240 km (150 mi; 130 nmi) south of the island of Karpathos.[14]

Shortly after the disappearance, the French government began to investigate whether there had been a security breach at Paris Charles de Gaulle Airport.[59]

<templatestyles src="Template:Quote_box/styles.css" />

ACARS messages
  • 00:26Z 3044 ANTI ICE R WINDOW
  • 00:26Z 561200 R SLIDING WINDOW SENSOR
  • 00:26Z 2600 SMOKE LAVATORY SMOKE
  • 00:27Z 2600 AVIONICS SMOKE
  • 00:28Z 561100 R FIXED WINDOW SENSOR
  • 00:29Z 2200 AUTO FLT FCU 2 FAULT
  • 00:29Z 2700 F/CTL SEC 3 FAULT
All times are UTC (also known as Zulu time).

Seven messages produced by the Aircraft Communications Addressing and Reporting System (ACARS) had been received from the aircraft between 02:26 and 02:29;[28] contact was lost four minutes later at 02:33.[28][60] The data, confirmed by France's Bureau of Investigations and Analysis,[61] indicates that smoke may have been detected in the front of the airliner—in the front lavatory and the avionics bay beneath the cockpit.[60][62] Smoke detectors of the type installed on the aircraft can also be triggered by the condensation of water vapour, producing fog, in the event of a sudden loss of pressure inside the cabin. The three windows mentioned in the data are cockpit windows.[63] The flight control unit (FCU) is a cockpit-fitted unit that the pilot uses to enter instructions into the on-board flight computer. The spoiler elevator computer number 3 (SEC 3) is one of the three computers that controls the spoilers and elevator actuators.[64] Two pilots—one interviewed by The Daily Telegraph, the other writing for The Australian—interpreted the data as possible evidence of a bomb.[65][66] Aviation expert David Learmount of Flight International suggested that an electrical fire could have started in the aircraft's avionics compartment[67] and that the aircrew may have been too distracted to raise the alarm with air traffic control.[68]

On 22 May, the French television station M6 reported that, contrary to official statements, one of the pilots told Cairo air traffic control about smoke in the cabin, and decided to make an emergency descent.[69] Later that day, the report was dismissed as false by the Egyptian Civil Aviation Ministry.[70]

On 24 May, a forensics official from Egypt's investigative team said that the remains of the victims indicate an explosion on board.[71] The head of forensics denied the claim.[72]

See also

Notes

  1. Last known location
  2. Abbreviated forms of the flight name combine the airline's IATA airline code (MS) or ICAO airline code (MSR) with the flight number.
  3. The aircraft was an Airbus A320-200 model, also known as the A320ceo to distinguish it from the newer A320neo; the infix -32 specifies it was fitted with IAE V2527-A5 engines.
  4. Two passengers had dual EgyptianCanadian citizenship,[20] one of them was travelling on their Egyptian passport.[21]
  5. The passenger had dual BritishAustralian citizenship.[22]

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 28.2 Lua error in package.lua at line 80: module 'strict' not found.
  29. 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 32.2 Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. 53.0 53.1 Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.

External links