Tarom – Airbus A310-324 (YR-LCC) flight ROT371

by | Mar 24, 2018 | Aviation Accident | 2 comments

The Tarom flight ROT371 accident was notified to the Civil Aviation Inspectorate by Romanian Air Traffic Services.

The accident occurred on 31 March, 1995, when the Airbus A310-324, registered YR-LCC, was scheduled as Tarom flight ROT371 with destination Brussels, took off from Bucharest-Otopeni airport at 06:06:44 UTC.

After approximately 2 minutes of flight, the aircraft crashed within the area of Balotesti village, near Bucharest-Otopeni airport.

The flight was flown by the First Officer as PF (Pilot Flying), while the Commander was PM (Pilot Monitoring) : no briefing for takeoff was carried out (Captain said : “standard briefing, right side flying“.)

Tarom flight ROT371

Tarom flight ROT371

The Tarom flight ROT371 accident can be divided into few phases :

Phase I :
DFDR recorded data indicate a normal evolution of flight, from takeoff up to 1800 ft altitude that corresponds to “Climb power” thrust setting.

Phase II :
In this phase the thrust asymmetry starts to develops at a rate of approximately 1° TRA/sec.

It is presumed that during this phase , because of the delay to carry out the order to retract flaps, the co-pilot of Tarom flight ROT371 starts to doubt the Captain state and at 06:08.02 asks “what’s wrong with you ?”

During this phase CVR recorded a noise which seems to indicate human pain.
In that moment aircraft had banking 22 degrees : reaching shortly after 28 degrees.

Phase III :
It si the phase during which co-pilot seems preoccupied to determine the Captain state, sharing his attention between flying the aircraft and determining the Captain’s state.

Phase IV :
this is the phase when the co-pilot seems to be convinced of Captain’s incapacitation.
He requests autopilot engagement : autopilot was engaged for one second or less and then disengaged itself. During the following two seconds DFDR data indicate a modification of the control surfaces deflection.

During this period the banking of Tarom flight ROT371 increased to 57,42 degrees.

Phase V:
The phase in which the aircraft dramatically changes its attitude. The Pilot’s maneuver and the control surfaces position cannot be explained on the basis of the data and elements available.

Tarom flight ROT371 dived with a maximum speed of 324 kts and impacted terrain with a pitch of 50 degrees with a magnetic heading of 060°.

The investigation commission consider the following causal factors:

  • Thrust asymmetry
  • Possible pilot incapacitation (the Captain);
  • Insufficient corrective action from the Copilot in order to cover the consequences of the first factors.

Safety Recommendations have been made as a result of this investigation

  • After the accident, Al issued two mandatory SBs that were enforced a French DGAC Directive, concerning remedy measures to be taken by all operators for elimination of all probable causes of this malfunction


Download Report

Tarom – Airbus A310-324 (YR-LCC) flight ROT371

Event date: 19950331
Airline / Operator:TAROM
Model: A310-324
Registration: YR-LCC
msn: 450
Location: Bucharest, Romania

You may like to review this event, with a similar cause:

Jordan Aviation – Airbus – A320-211 (JY-JAR) flight LTE376

While landing on Runway 14 at Leeds Bradford Airport the aircraft touched down just beyond the end of the marked touchdown zone with low autobrake selected. Manual wheel braking commenced shortly after mainwheel touchdown. At a groundspeed of around 70 kt the brakes...


  1. Airton Vieira

    We perceive a lack of training, a lack of FMC, and there is always human error.

    • LNK

      the pilots were very trained and had lots of hours…

      The plane was flying into clouds leaving the first officier without vision to speak of, his captain retracted the flaps, but failed to retract the slats and got a heart attack right after, while the same time there was a thrust anomaly and the left engine went into idle…

      Exactly what training and FMC can prepare you to such an impossble event?


Submit a Comment

Your email address will not be published. Required fields are marked *