Accident Dassault Mirage 2000N 374/125-BS, 28 Sep 2017
ASN logo
ASN Wikibase Occurrence # 200009
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Type:Silhouette image of generic MIR2 model; specific model in this crash may look slightly different    
Dassault Mirage 2000N
Owner/operator:EC 2/4 (La Fayette) l'Armée de l'air
Registration: 374/125-BS
MSN: 389
Fatalities:Fatalities: 0 / Occupants: 2
Other fatalities:0
Aircraft damage: Written off (damaged beyond repair)
Location:Hassan Djamouss Airport, N’Djamena -   Chad
Phase: Take off
Departure airport:N'Djamena Airport (NDJ/FTTJ)
Destination airport:Dakar (GOOY)
Investigating agency: BEAD
Confidence Rating: Accident investigation report completed and information captured
The french fighter jet hit the wall of the airport during takeoff under unknown reasons. There was a post fire impact.
The two occupants ejected safely. The navigator (NOSA) was injured to one leg.

3.2 Causes of the event
The causes of the accident are as follows :
- the obstruction of the anemometric system of the total pressure T3 related to a long immobilization of the aircraft having allowed the installation of foreign bodies ;
- an inappropriate interpretation of the maintenance documentation and the absence of specific instructions when the aircraft are operating in dusty environments and particularly equipped with spiders or insects;
- a migration of practices in the procedure for checking instruments during the takeoff run, which does not allow the consistency of speed information to be checked;
- the weak synergy within the crew due to its composition;
- the housing conditions of the crew, which led to a state of fatigue that affected their ability to analyze;
- over-motivation to carry out the mission, linked to the two previous departures cancelled two days earlier, which led to a bias in the analysis of the crew and late decision making;
- the lack of reference points linked to the absence of a distance-to-go sign and the limited number of take-offs made in this direction on this runway, which deprived the crew of a means of alerting them to the excessive distance covered;

- the absence of mechanization of the crew in the simulator on this type of failure, which is impossible to simulate today, which has delayed the decision making process;
- an erroneous awareness of the situation associated with a focus on Jx which delayed the decision to abort takeoff;
- an incomplete analysis and communication of a precursor event, linked to the unit's cyclical organization, which prevented effective awareness of the speed consistency verification procedure;
- an atypical NOSA aeronautical curriculum, which favored a drift in the application of procedures.


Accident investigation:
Investigating agency: BEAD
Status: Investigation completed
Download report: Final report



Revision history:

28-Sep-2017 14:02 Iceman 29 Added
28-Sep-2017 14:07 Iceman 29 Updated [Operator, Source, Embed code, Narrative]
29-Sep-2017 12:37 Iceman 29 Updated [Destination airport, Photo, ]
02-Oct-2017 19:53 Martijn Updated [Registration, Source]
28-Sep-2018 06:29 JF Updated [Registration, Location, Source]
25-Dec-2018 21:17 Nepa Updated [Operator, Operator]
23-Dec-2019 17:20 Nepa Updated [Operator, Departure airport, Destination airport, Operator]
19-Oct-2020 19:01 KagurazakaHanayo Updated [Cn, Destination airport, Source, Narrative]
19-Oct-2020 19:02 harro Updated [Narrative, Accident report]
01-Apr-2022 19:52 BEAVERSPOTTER Updated [Cn, Country]
22-Jun-2022 00:49 Ron Averes Updated [Country]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2023 Flight Safety Foundation

701 N. Fairfax St., Ste. 250
Alexandria, Virginia 22314