Airport (less than 10 km from airport)

Flight Type:

Scheduled Revenue Flight

Survivors:

Site:

Schedule:

Tehran - Ahwaz

MSN:

11166

YOM:

1981

Flight number:

EP775

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

Following an uneventful flight from Tehran, the crew initiated the approach to Ahwaz but encountered poor weather conditions with visibility near minimums. During the last segment, the aircraft landed hard on runway 30, bounced and touched down to the right of the runway. The crew decided to make a go-around and completed a circuit before landing again few minutes later. Following a 'normal' landing, all 88 occupants evacuated safely. The aircraft was considered as damaged beyond repair.

Crash of an Airbus A310 in Vienna, Austria

Date & Time: Jul 12, 2000 at 1334 LT

Type of aircraft:

Airbus A310

Operator:

Registration:

D-AHLB

Flight Phase:

Flight Type:

Survivors:

Site:

Schedule:

Hania - Hanover

MSN:

0528

YOM:

1990

Flight number:

HF3378

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

143

Pax fatalities:

Other fatalities:

Total fatalities:

Captain / Total flying hours:

23400

Copilot / Total flying hours:

2850

Aircraft flight hours:

41307

Aircraft flight cycles:

13789

Circumstances:

After takeoff from Chania-Souda Airport, the crew reported technical problems with the right main gear that could not be raised properly in its wheel well. The captain decided to continue to Munich in a gear down configuration but the fuel consumption increased. En route, the crew realized he could not make it to Munich so diverted to Vienna-Schwechat Airport. At a distance of about 12 NM from the airport, at an altitude of 4,000 feet, both engines failed due to fuel exhaustion. One of the engine could be restarted for a short period of time but on short final, the aircraft stalled and struck the ground (a grassy area) about 500 metres short of runway 34. The left main gear broke off, the aircraft slid for some 600 metres then veered to the left and came to rest on its left wing. All 151 occupants were rescued, among them 26 passengers were slightly injured. The aircraft was damaged beyond repair.

Probable cause:

Continuation of the flight with a landing gear problem until the engines failed due to fuel exhaustion.
The following findings were identified:
Crew:
- Failure to comply with the company's rules on fuel reserves, caused by several human factors, with extreme workload and stress being the important factor (loss of situational awareness).
- Determination of the fuel reserves using only the FMS, which, due to its characteristics did not take into account the additional fuel consumption.
- Failure to develop alternative strategies to curb the fuel problem.
- Failure to comply with a fuel warning (low fuel level warning) and decision to continue the flight to Vienna International Airport, although the plane was in the immediate vicinity of Zagreb Airport.
Manufacturer:
- Inadequate and misleading documentation (FMS scheme, altitude, terms) for this specific case, particularly in relation to the restriction of FMS.
Operator:
- Inadequate documentation for "abnormal landing gear up indication" of the abnormal checklist.
- Lack of review of the fuel needs by the Operations Division.
Contributing factors:
- Missing or inadequate preventive measures by manufacturers, approving authority and airlines following the previous publications of ICAO and EU DG VII about problems which, with the introduction of aircraft equipped with modern technologies, occurred and had been identified.
- Anthropo-technical construction deficiencies, which favour a misinterpretation of the FMS EFOB display.

Final Report:

Crash of a Cessna 208 Caravan I in Nairobi

Date & Time: Jul 12, 2000

Type of aircraft:

Cessna 208A Caravan

Operator:

Air Bateleur

Registration:

5Y-JAO

Flight Phase:

Takeoff (climb)

Flight Type:

Survivors:

Site:

MSN:

208-0202

YOM:

1991

Location:

Nairobi-Wilson

Nairobi City District

Country:

Kenya

Region:

Africa

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

At liftoff, the engine failed. The aircraft stalled and crashed along the runway. There were no casualties but the aircraft was damaged beyond repair.

Probable cause:

Engine failure at takeoff for unknown reasons.

Crash of a Curtiss C-46A-60-CS Commando in Villavicencio: 10 killed

Date & Time: Jul 9, 2000 at 0825 LT

Type of aircraft:

Curtiss C-46 Commando

Operator:

Rolando Medina Marmolejo

Registration:

HK-851P

Flight Phase:

Takeoff (climb)

Flight Type:

Survivors:

Site:

Schedule:

Villavicencio – Mitú

MSN:

383

YOM:

1945

Location:

Villavicencio

Crash of a Tupolev TU-154B-2 in Thessaloniki

Date & Time: Jul 4, 2000 at 1657 LT

Type of aircraft:

Tupolev TU-154

Operator:

Registration:

HA-LCR

Flight Phase:

Flight Type:

Scheduled Revenue Flight

Survivors:

Site:

Schedule:

Budapest - Thessaloniki

MSN:

82A543

YOM:

1982

Flight number:

MA262

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Captain / Total flying hours:

7420

Captain / Total hours on type:

7000.00

Copilot / Total flying hours:

566

Copilot / Total hours on type:

566

Aircraft flight hours:

22409

Aircraft flight cycles:

13583

Circumstances:

Originally, flight MA262 from Budapest to Thessaloniki should be performed by a Boeing 737-300 HA-LES but due to technical problems, a Tupolev TU-154B-2 was dispatched. Following an uneventful flight, the crew was cleared for a VOR/DME approach to runway 34 followed by a visual circle to land on runway 28 as the runway 34 was closed to traffic due to construction works. Because a Boeing 757 slowed to vacate the runway after landing, ATC instructed the crew to extend the downwind leg for runway 28. For unknown reasons, the crew failed to comply with this instructions and performed 'S'. On final approach, the tower controller informed the crew that he forgot to lower the undercarriage. The captain increased engine power and initiated a go-around procedure but this decision was too late. The aircraft continued to descend and struck the runway surface in a gear-up configuration at 1657LT. The aircraft suffered substantial damages but the crew managed to go-around and to follow a holding pattern. A safe landing was completed at 1715LT. All 94 occupants evacuated safely while the aircraft was damaged beyond repair.

Probable cause:

Despite repeated instructions of the control tower the crew did not carried out a short turn for landing, resulting in:
- The aircraft was not aligned with the runway in time (unstabilized approach).
- Attention of the cockpit crew was to exclusively dedicated to performing sudden maneuvers at low altitude, in order to align the plane with the runway.
- Failure to lower the undercarriage in accordance with the applicable procedures for this flight phase.
Contributing Factors:
- The apparent inactivation of the audible warning when the undercarriage was not deployed.
- Lack of Cockpit Resources Management.

Final Report:

Crash of a Douglas B-26C-25-DT Invader in Grande Prairie

Date & Time: Jun 29, 2000 at 2219 LT

Type of aircraft:

Douglas A-26 Invader

Operator:

Registration:

CF-EZX

Flight Phase:

Flight Type:

Fire fighting

Survivors:

Site:

Schedule:

Loon River - La Biche Lake - Grand Prairie

MSN:

18807

YOM:

1943

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

The pilot, sole on board, departed Loon River Airport on a fire fighting mission to La Biche Lake under callsign Tanker 3. While returning to Grand Prairie Airport, on final approach to runway 25, both engines failed almost simultaneously. The pilot attempted an emergency landing when the aircraft crashed 3 km short of runway. The pilot was injured and the aircraft was damaged beyond repair.

Probable cause:

Double engine failure on final approach due to a fuel exhaustion.

Crash of a Boeing 737-2R4C in Khartoum

Date & Time: Jun 26, 2000

Type of aircraft:

Boeing 737-200

Operator:

Registration:

7O-ACQ

Flight Phase:

Flight Type:

Cargo

Survivors:

Site:

Schedule:

Sana'a - Khartoum

MSN:

23129

YOM:

1984

Flight number:

IY626

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

Following an uneventful flight from Sana'a, the crew was cleared for an approach to runway 18. Weather conditions were poor with a sandstorm upon arrival. For unknown reasons, the captain decided to perform a straight-in approach to runway 36. After touchdown, The aircraft went out of control, veered off runway and collided with small concrete blocks, causing the nose gear to collapse. All five crew members escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Beechcraft 70 Queen Air in Leonora

Date & Time: Jun 24, 2000 at 1740 LT

Type of aircraft:

Beechcraft 70 Queen Air

Operator:

Alligator Airways

Registration:

VH-MWJ

Flight Phase:

Takeoff (climb)

Flight Type:

Survivors:

Site:

Schedule:

Leonora – Laverton

MSN:

LB-29

YOM:

1970

Location:

Country:

Region:

Crew on board:

Crew fatalities:

Pax on board:

Pax fatalities:

Other fatalities:

Total fatalities:

Circumstances:

The Beechcraft Queen Air and Rockwell Aero Commander were being used by a company to conduct private category passenger-carrying flights to transport its workers from Leonora to Laverton in Western Australia. The Aero Commander had departed and was established in the Leonora circuit area when the Queen Air took off. The pilot and one of the passengers of the Queen Air reported the take-off roll appeared normal until the aircraft crossed the runway intersection, when they felt a bump in the aircraft. The pilot reported hearing a loud bang and noticed that the inboard cowl of the right engine had opened. He also reported that he believed he had insufficient runway remaining to stop safely, so he continued the takeoff. The cowl separated from the aircraft at the time, or just after the pilot rotated the aircraft to the take-off attitude. He reported that although the aircraft had left the ground after the rotation, it then would not climb. The aircraft remained at almost treetop level until the pilot and front-seat passenger noticed the side of a tailings dump immediately in front of the aircraft. The pilot said that he pulled the control column fully back. The aircraft hit the hillside parallel to the slope of the embankment, with little forward speed. The impact destroyed the aircraft. Although the occupants sustained serious injuries, they evacuated the aircraft without external assistance. There was no post-impact fire. The aircraft-mounted emergency locator transmitter (ELT) did not activate.

Probable cause:

The examination of the Queen Air wreckage found no mechanical fault that may have contributed to the accident sequence other than the inboard cowl of the right engine detaching during the takeoff. The cowl latching mechanisms appeared to have been capable of operating normally. The two top hinges failing in overload associated with the lack of cowl latch damage suggested that the cowl was probably improperly secured before takeoff. The cowl appeared to have subsequently opened when it experienced the jolt when the aircraft crossed the runway intersection. The lack of any further cowl damage indicated that it detached cleanly and consequently its dislodgment should not have adversely affected the flying qualities of the aircraft.

Final Report:

Crash of an Ilyushin II-76MD at Privolzhskiy AFB

Date & Time: Jun 20, 2000 at 1750 LT

Type of aircraft:

Ilyushin II-76

Operator:

Registration:

RA-76723

Flight Phase:

Flight Type:

Government

Survivors:

Site: