The French BEA issues a report in complete disagreement with Egyptian counterpart about the crash of an Egyptair A320 off the Egyptian coast


The French BEA has released its report on the crash of an Egyptair Airbus A320 registered SU-GCC off the Egyptian coast on 19 May 2016. The aircraft was operating flight MS804 from Paris CDG to Cairo. The BEA conclusions (“fire in the cockpit”) differ strongly from the conclusions drawn by the Egyptian investigators (“explosion of a bomb”). Usually, such discrepancies are discussed between closed doors in order to come to a common conclusion. This was not the case for this accident.

Hereunder we publish the BEA report. Don’t expect the Egyptian report to be published any time soon: it is protected by the secret of judicial instruction…


Following the accident on 19 May 2016 over the Mediterranean Sea involving an Airbus A320 registered SU-GCC operated by EgyptAir, a safety investigation was immediately opened. In compliance with the international texts in force, as the accident occurred in international waters, Egypt, as the State of Registry and State of the Operator of the aeroplane, is in charge of carrying out this investigation. The BEA appointed an Accredited Representative to represent France as the State of Design of the aeroplane, assisted by technical advisers from the aircraft manufacturer, Airbus. The NTSB (1) also appointed an Accredited Representative to represent the United States as the State of Manufacture of the engine.

France contributed to the safety investigation from the very outset. Initially, the BEA’s work consisted in acting as advisor to its Egyptian counterpart and then in participating in sea search operations for the aircraft wreckage. At the same time, the three States collaborated in collecting and analysing the first elements available – in particular the ACARS (2) messages.

Once the wreckage had been found, the debris was inspected and the flight recorders were located, retrieved and immediately sent to Cairo in order to start the initial work to recover and read the data. These operations, collectively decided on and carried out by the Egyptian, American and French specialists, did not succeed in reading the recorded data due to the severe damage to the data media. Advanced repair work was then necessary and the BEA was asked to carry it out in its laboratory in France.

The work on the flight recorders was carried out under the authority of the Egyptian Investigator In Charge, on the BEA premises, and at the beginning of July 2016 the data from the two flight recorders was extracted, read and decoded.

During this work, the Egyptian authorities published the following elements about the

  • The flight recorders stopped operating while the aircraft was in cruise at an altitude of
    37,000 feet;
  • The aircraft systems sent ACARS messages indicating the presence of smoke in toilets and the avionics bay;
  • The data from the data recorder confirms these messages;
  • The playback of the cockpit voice recorder reveals, in particular, that the crew
    mentioned the existence of a fire on board;
  • Several pieces of debris were retrieved from the accident site. Some of these had signs of having been subject to high temperatures, and traces of soot.

Once the data from the flight recorders had been retrieved, the Egyptian authorities
continued their work in Egypt.

In addition, the BEA had collected the following elements:

  • A signal from an emergency locator transmitter was sent at 00:37 (source CNES (3) ) i.e. around eight minutes after the transmission of the last ACARS message;
  • Data from a Greek primary radar (sent by the Greek authorities to the BEA) shows that the aeroplane had descended in a turn until collision with the surface of the water.

Based on these elements, the BEA considers that the most likely hypothesis is that a fire
broke out in the cockpit while the aeroplane was flying at its cruise altitude and that the fire spread rapidly resulting in the loss of control of the aeroplane.

For its part, the BEA’s Egyptian counterpart announced in December 2016, the discovery
of traces of explosive on human remains. It stated that, in accordance with Egyptian legislation, this finding led it to transfer the file to the Egyptian Attorney General who would from now on be responsible for carrying out the investigation.

The BEA’s proposals concerning further work on the debris and recorded data were not,
as far as the BEA knows, followed up. The technical elements of the investigation already
collected by Egypt, including those provided by the BEA, are protected by the Egyptian judicial investigation.

In an effort to continue the safety investigation mission, the BEA asked to meet the
Egyptian Attorney General. This took place at the end of May 2018. In this meeting, the Egyptian authorities explained that as it had been determined that there had been a malicious act, the investigation now fell within the sole jurisdiction of the judicial authorities.

The BEA’s Egyptian counterpart did not publish the final report which would have allowed
the BEA to set out its differences of opinion as authorized by the international provisions.
The BEA considers that it is necessary to have this final report in order to have the
possibility of understanding the cause of the accident and to provide the aviation community with the safety lessons which could prevent future accidents.

As mentioned above, the BEA considers that the most likely hypothesis is the rapid spread
of a fire and would like investigations into this hypothesis to be continued in the interests of
aviation safety.

The BEA is ready to continue its collaboration with its Egyptian counterpart should the
latter restart the safety investigation into this accident.

(1) National Transportation Safety Board: the BEA’s counterpart in the United States.
(2) ACARS: system for sending messages between the aeroplane and the operator,
allowing, in particular, the transmission of information for maintenance operations.
(3) Centre National d’Etudes Spatiales (National Centre for Space Studies).


Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.