Region

Crash of a McDonnell Douglas MD-83 in Bandar-e Mahshahr

Date & Time: Jan 27, 2020 at 0736 LT
Type of aircraft:
Operator:
Registration:
EP-CPZ
Survivors:
Yes
Schedule:
Tehran - Bandar-e Mahshahr
MSN:
53464
YOM:
1994
Flight number:
RV6936
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
136
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 13 at Bandar-e Mahshahr Airport, the airplane was unable to stop within the remaining distance and overran. It lost its undercarriage, came across a road and came to rest on its belly. All 144 occupants evacuated safely while the aircraft was damaged beyond repair. The aircraft just completed a regular weekly service (flight RV6936) from Tehran.

Crash of a Boeing 737-8KV in Sabashahr: 176 killed

Date & Time: Jan 8, 2020 at 0618 LT
Type of aircraft:
Operator:
Registration:
UR-PSR
Flight Phase:
Survivors:
No
Schedule:
Tehran - Kiev
MSN:
38124
YOM:
2016
Flight number:
PS752
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
167
Pax fatalities:
Other fatalities:
Total fatalities:
176
Captain / Total flying hours:
11600
Captain / Total hours on type:
5500.00
Copilot / Total flying hours:
7600
Circumstances:
The airplane departed Tehran-Imam Khomeini Airport runway 29R at 0612LT on a regular schedule service (flight PS752) to Kiev-Borispol Airport with 176 people on board, 167 passengers and a crew of nine. Shortly after takeoff, while climbing by night, the crew was cleared to climb to FL260. Weather conditions were considered as good. While climbing to an altitude of 8,000 feet, the airplane ceased to climb and radar and radio contacts were lost. In a confused situation, the airplane entered a right turn then initiated an uncontrolled descent until it crashed and disintegrated in a field, six minutes after takeoff. The crew did not send any distress message and did not report any problems. Debris were found in Sabashahr, about 16 km north of the airport. The aircraft was totally destroyed by impact forces and post crash fire and all 176 occupants were killed. First statement from the Iranian CAO (Civil Aviation Organization) reported technical problems, maybe an uncontained failure of the right engine and a subsequent fire, for sure an unexpected catastrophic situation. Three days after the crash, in the morning of January 11, the Iranian CAO confirmed that the aircraft was unintentionally and accidentally shot down by the Iranian Armed Forces. This happened during a complex, delicate and highly tensioned situation between Iran and the United States, while Iran had just fired several ballistic missiles from Iran on two US military bases located in eastern Iraq. At the time of the accident were three pilots in the cockpit, one captain with 11,600 flying hours, one instructor with 12,000 flying hours and one first officer with 7,600 flying hours. One-hundred forty-six victims held Iranian passport, ten Afghan, five Canadian, four Swede and two Ukrainian. All nine crew members consisting of three cockpit crew and six cabin crew were Ukrainian.
Probable cause:
Unintentionally and accidentally shot down by the Iranian Armed Forces.

Crash of a Boeing 707-3J9C in Fath: 15 killed

Date & Time: Jan 14, 2019 at 0830 LT
Type of aircraft:
Operator:
Registration:
EP-CPP
Flight Type:
Survivors:
Yes
Site:
Schedule:
Bishkek - Payam
MSN:
21128/917
YOM:
1976
Country:
Region:
Crew on board:
16
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
15
Circumstances:
The airplane, owned by the Islamic Republic of Iran Air Force (IRIAF) was completing a cargo flight from Bishkek, Kyrgyzstan, on behalf of Saha Airlines, and was supposed to land at Payam Airport located southwest of Karaj, carrying a load of meat. On approach, the crew encountered marginal weather conditions and the pilot mistakenly landed on runway 31L at Fath Airport instead of runway 30 at Payam Airport which is located 10 km northwest. After touchdown, control was lost and the airplane was unable to stop within the remaining distance (runway 31L is 1,140 meters long), overran and crashed in flames into several houses located past the runway end. The aircraft was destroyed by fire as well as few houses. The flight engineer was evacuated while 15 other occupants were killed.

Crash of a Canadair CL-600-2B16 Challenger 604 near Shahr-e-Kord: 11 killed

Date & Time: Mar 11, 2018 at 1840 LT
Type of aircraft:
Operator:
Registration:
TC-TRB
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Sharjah – Istanbul
MSN:
5494
YOM:
2001
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
11
Captain / Total flying hours:
4880
Captain / Total hours on type:
1600.00
Copilot / Total flying hours:
1132
Copilot / Total hours on type:
114
Aircraft flight hours:
7935
Aircraft flight cycles:
3807
Circumstances:
A Turkish Challenger 604 corporate jet impacted a mountain near Shahr-e Kurd in Iran, killing all 11 on board. The aircraft departed Sharjah, UAE at 13:11 UTC on a flight to Istanbul, Turkey. The aircraft entered Tehran FIR fifteen minutes later and the Tehran ACC controller cleared the flight to climb to FL360 according to its flight plan. About 14:32, the pilot requested FL380, which was approved. Before reaching that altitude, the left and right airspeeds began to diverge by more than 10 knots. The left (captain's) airspeed indicator showed an increase while the right hand (copilot's) airspeed indicator showed a decrease. A caution aural alert notified the flight crew of the difference. Remarks by the flight crew suggested that an 'EFIS COMP MON' caution message appeared on the EICAS. As the aircraft was climbing, the crew reduced thrust to idle. Approximately 63 seconds later, while approaching FL380, the overspeed aural warning (clacker) began to sound, indicating that the indicated Mach had exceeded M 0.85. Based on the Quick Reference Handbook (QRH) of the aircraft, the pilot flying should validate the IAS based on the aircraft flight manual and define the reliable Air Data Computer (ADC) and select the reliable Air Data source. The pilot did not follow this procedure and directly reduced engine power to decrease the IAS after hearing the clacker. The actual airspeed thus reached a stall condition. The copilot tried to begin reading of the 'EFIS COMP MON' abnormal procedure for three times but due to pilot interruption, she could not complete it. Due to decreasing speed, the stall aural warning began to sound, in addition to stick shaker and stick pusher activating repeatedly. The crew then should have referred to another emergency procedure to recover from the stall condition. While the stick pusher acted to pitch down the aircraft to prevent a stall condition, the captain was mistakenly assumed an overspeed situation due to the previous erroneous overspeed warning and pulled on the control column. The aircraft entered a series of pitch and roll oscillations. The autopilot was disengaged by the crew before stall warning, which ended the oscillations. Engine power began to decrease on both sides until both engines flamed out in a stall condition. From that point on FDR data was lost because the electric bus did not continue to receive power from the engine generators. The CVR recording continued for a further approximately 1 minute and 20 seconds on emergency battery power. Stall warnings, stick shaker and stick pusher activations continued until the end of the recording. The aircraft then impacted mountainous terrain. Unstable weather conditions were present along the flight route over Iran, which included moderate up to severe turbulence and icing conditions up to 45000ft. These conditions could have caused ice crystals to block the left-hand pitot tube. It was also reported that the aircraft was parked at Sharjah Airport for three days in dusty weather condition. Initially the pitot covers had not been applied. The formation of dust inside the pitot tube was considered another possibility.
Probable cause:
The accident was caused by insufficient operational prerequisites for the management of erratic airspeed indication failure by the cockpit crew. The following contributing factors were identified:
- The aircraft designer/manufacturer provided insufficient technical and operational guidance about airspeed malfunctions that previously occurred.
- Lack of effective CRM.
Final Report:

Crash of an ATR72-212 on Mt Dena: 66 killed

Date & Time: Feb 18, 2018 at 0931 LT
Type of aircraft:
Operator:
Registration:
EP-ATS
Flight Phase:
Survivors:
No
Site:
Schedule:
Tehran – Yasuj
MSN:
391
YOM:
1993
Flight number:
EP3704
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
60
Pax fatalities:
Other fatalities:
Total fatalities:
66
Captain / Total flying hours:
17926
Captain / Total hours on type:
12519.00
Copilot / Total flying hours:
1880
Copilot / Total hours on type:
197
Aircraft flight hours:
28857
Aircraft flight cycles:
28497
Circumstances:
Iranian ATR72 aircraft registered EP-ATS operated by Iran Aseman Airlines was assigned to perform a domestic scheduled passenger flight from Tehran to Yasuj on 07:55 local time. The aircraft took off from Tehran Mehrabad International Airport (0III) at 04:35 UTC. (08:05 LMT) and the flight was the first flight of the day for aircraft and the crew. The cruise flight was conducted at FL210 on airway W144 and no abnormal situation was reported by the crew and the flight was continued on Tehran ACC frequency till the time the first officer requested latest weather information of the destination by contact to Yasuj tower then requested to leave FL210 to FL170 from Tehran ACC. When the aircraft was descending to FL170 and crew calling YSJ tower the aircraft descending was continued to altitude of 15000 ft. The aircraft was approved to join overhead of the airport and perform “circling NDB approach “to land on RWY 31 at the destination aerodrome. Finally the aircraft collided with a peak lee of DENA Mountains about 8.5 miles at North far from the airport and involved accident on 06:01 UTC. The aircraft was completely destroyed as a result of collision with the mountain at the altitude of approximately 13,300 ft.
Probable cause:
The accident was happened due to many chains of considered causes but the “Human Factor” had main roll for the conclusion of the scenario. The Cockpit Crew action which has caused dangerous conditions for the flight is considered as main cause. Based on provided evidences, the errors of cockpit crew were as follows:
- Continuing to the Yasouj airport for landing against Operation manual of the Company, due to low altitude ceiling of the cloud and related cloud mass. They should divert to alternate airport,
- Descending to unauthorized altitude below minimum of the route and MSA,
- Lack of enough CRM during flight,
- Failure to complete the stall recovery (flap setting, max RPM),
- Inappropriate use of Autopilot after Stall condition,
- Inadequate anticipation for bad weather based on OM (Clouds, Turbulence, and Icing ...),
- Quick action to switch off anti-ice system and AOA,
- Failure to follow the Check lists and standard call out by both pilots.
Contributing Factors:
The contributive factors to this accident include but are not limited to the following:
- The airline was not capable to detect systematic defectives about :
- Effectiveness of crew training about Meteorology, OM, SOP,
- Enough operational supervision on pilot behaviors,
- The lack of SIGMET about Mountain Wave or Severe Mountain wave,
- Unclear procedure for stall recovery in FCOM,
- Lack of warning in aircraft manuals by manufacturer for flight crew awareness about mountain wave.
- Lack of APM System to alert crew about performance degradation.
Other Deficiencies and Short Comes:
In the process of the accident investigation, some detailed deficiencies and short comes were found and should be considered as latent conditions by related authorities:
- AD accomplishment and related monitoring,
- Sanction on aviation industries and effect on Flight safety,
- Non-standard communication between ATC and crew,
- Unclear definition of the Fully Qualified Pilot and qualified copilot in Aircrew regulation.
- Weather forecast (TAF) in the airports based on annex 3 procedure in the Civil Aviation Organization for approving alternative method of compliance for aircraft AD,s
- Search and rescue Coordination with local authorities for aviation accidents,
- Time setting of aircraft flight data recording(FDR) either by technician or pilots.
Final Report:

Crash of a McDonnell Douglas MD-83 in Mashhad

Date & Time: Jan 28, 2016 at 1730 LT
Type of aircraft:
Operator:
Registration:
EP-ZAB
Survivors:
Yes
Schedule:
Isfahan – Mashhad
MSN:
49930/1720
YOM:
1990
Flight number:
IZG4010
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
148
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Isfahan, the crew started the approach to Mashhad Airport in poor weather conditions with low visibility due to snow falls. After touchdown on runway 31R, the aircraft skidded and went out of control. It veered off runway to the left, lost its undercarriage and came to rest 55 meters to the left of the centerline, about 2,200 meters from the runway threshold. All 154 occupants were quickly evacuated and were unhurt while the aircraft was damaged beyond repair. At the time of the accident, it appears the runway was icy and slippery.

Crash of a Rockwell Grand Commander 690 in Zāhedān: 7 killed

Date & Time: Oct 12, 2014 at 1920 LT
Registration:
1405
Flight Type:
Survivors:
No
Site:
Schedule:
Tehran - Zāhedān
MSN:
690-11075
YOM:
1972
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The twin engine aircraft was flying to Zāhedān with a crew of three (two pilots and a flight attendant) and four passengers, among them General Mahmoud Sadeqi, a senior police officer in charge of investigations, who was travelling to Zāhedān to investigate an incident involving an attack on police. While approaching Zāhedān by night, the aircraft hit a mountain located in the Sabzpushan Heights, north of the airport. All seven occupants were killed. A day later, Iranian authorities said the accident was caused by technical flaws, darkness and the pilot’s unfamiliarity with the region.

Crash of a HESA IrAn-140-100 in Tehran: 39 killed

Date & Time: Aug 10, 2014 at 0918 LT
Type of aircraft:
Operator:
Registration:
EP-GPA
Flight Phase:
Survivors:
No
Schedule:
Tehran – Tabas
MSN:
90-05
YOM:
2008
Flight number:
SPN5915
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
39
Aircraft flight hours:
1350
Circumstances:
Shortly after takeoff from runway 29L, while in initial climb, the aircraft banked right, went out of control and crashed in flames in a residential area located 1,6 km northwest of the airport. The aircraft was destroyed by impact forces and post crash fire and 9 passengers were seriously injured while all 39 other occupants were killed. There are conflicting reports about the number of casualties. ATC reported that the crew requested a right turn immediately after takeoff while the standard procedure requires left turn. In a first statement, it was reported that the aircraft suffered a right engine failure shortly after rotation, at a critical stage of the flight. It was also confirmed that the departure was completed with a MTOW above the limit considering the outside temperature at the time of the accident.

Crash of a Dassault Falcon 20E off Kish Island: 4 killed

Date & Time: Mar 3, 2014 at 1846 LT
Type of aircraft:
Registration:
EP-FIC
Flight Type:
Survivors:
No
Schedule:
Kish Island - Kish Island
MSN:
334
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
On behalf of the Civil Aviation Authority, the aircraft was involved in the calibration of the navigation systems of the Kish Island Airport, with two pilots and two technicians on board. After completing several manoeuvre, while flying four km east of the Island, the aircraft crashed into the sea for unknown reason. All four occupants were killed, their bodies were found a day later.

Crash of a Boeing 727-200 in Orumiyeh: 77 killed

Date & Time: Jan 9, 2011 at 1945 LT
Type of aircraft:
Operator:
Registration:
EP-IRP
Survivors:
Yes
Schedule:
Tehran - Orumiyeh
MSN:
20945/1048
YOM:
1974
Flight number:
IR277
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
94
Pax fatalities:
Other fatalities:
Total fatalities:
77
Circumstances:
Departure from Tehran to Orumiyeh was delayed for two hours due to bad weather at destination. Finally, aircraft left Tehran-Mehrabad at 1815LT. On approach to Orumiyeh, visibility was low due to snow and clouds at 1,500, 2,000 and 6,000 feet. Aircraft hit the ground and broke into three pieces eight kilometers short of runway 21. Sixty-six passengers and all eleven crew were killed. Loss of power on both left and right engines (number one and three) is suspected.