Crash of a HESA IrAn 140-100 in Arak

Date & Time: Aug 12, 2005 at 1840 LT
Type of aircraft:
Operator:
Registration:
EP-SFD
Survivors:
Yes
Schedule:
Tehran – Khorramabad
MSN:
90-01
YOM:
2003
Location:
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
En route from Tehran to Khorramabad, while in cruising altitude, the right engine failed. The crew was cleared by ATC to divert to Arak Airport. After landing, the aircraft went out of control, veered off runway and came to rest. All 27 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Failure of the right engine for unknown reasons.

Crash of an Antonov AN-26 near Al Mukalla: 1 killed

Date & Time: Aug 9, 2005 at 1700 LT
Type of aircraft:
Operator:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Aden – Al Mukalla
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
44
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The aircraft departed Aden on a flight to Al Mukalla with 44 soldiers and five crew members on board. While descending to Al Mukalla Airport, both engines stopped. The crew made an emergency landing in a desert area located about 30 km east of Al Mukalla Airport. Twenty people escaped unhurt while 28 others were injured, seven seriously. Unfortunately, the captain was killed.
Probable cause:
It is believed that both engines failed following a fuel exhaustion.

Crash of an Antonov AN-12BP in Luena

Date & Time: Aug 8, 2005 at 0650 LT
Type of aircraft:
Operator:
Registration:
T-300
Flight Type:
Survivors:
Yes
MSN:
4 34 21 08
YOM:
1964
Location:
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing at Luena Airport, the four engine aircraft went out of control, veered off runway and came to rest. All occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Cessna 421C Golden Eagle III in Palwaukee

Date & Time: Aug 5, 2005 at 1225 LT
Registration:
N421KC
Flight Type:
Survivors:
Yes
Schedule:
Palwaukee - Mackinac Island
MSN:
421C-0028
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
728
Captain / Total hours on type:
28.00
Aircraft flight hours:
6835
Circumstances:
The twin-engine airplane sustained substantial damage when it impacted the top of a single story industrial building and then impacted a landscape embankment and trees during an attempted single-engine go-around. The pilot reported that the left engine failed during initial climb. He feathered the left propeller and returned to the airport to execute an emergency landing. The pilot reported that he had "excessive speed" on final approach and "overshot the runway." When the airplane was at mid-field, the pilot elected to do a go-around. He did not raise the landing gear and the flaps remained about 15-degrees down. The airplane lost altitude and impacted the terrain about .5 miles from the airport. A witness reported seeing the airplane attempt to land on the runway twice during the same approach, but ballooned both times before executing the go-around. The Pilot's Operating Handbook (POH) "Rate-of-Climb One Engine Inoperative" chart indicated that about a 450-foot rate-of-climb was possible during the single-engine go-around if the airplane was in a clean configuration. The chart also indicated that a 350-foot penalty would be subtracted from the rate-of-climb if the landing gear were in the DOWN position, and additionally, a 200-foot penalty would be subtracted from the rate-of-climb if the flaps were in the 15-degree DOWN position. Inspection of the left engine revealed that the starter adapter shaft gear had failed. Inspection of the engine maintenance logbooks revealed that the Teledyne Continental Motors Service Bulletin CSB94-4, and subsequent revisions including the Mandatory Service Bulletin MSB94- 4F, issued on July 5, 2005, had not been complied with since the last engine overhaul on July 17, 1998. The service bulletin required a visual inspection of the starter adapter every 400 hours. The engine logbook indicated that the engine had accumulated about 1,270 hours since the last overhaul. The service bulletin contained a WARNING that stated, "Compliance with this bulletin is required to prevent possible failure of the starter adapter shaft gear and/or crankshaft gear which can result in metal contamination and/or engine failure."
Probable cause:
The pilot's improper in-flight decision to execute a go-around without raising the landing gear and raising the flaps to the full UP position, resulting in low airspeed and the airplane stalling. Contributing factors to the accident included the pilot's failure to comply with the manufacturer's mandatory service bulletin and the failure of the starter adapter shaft gear which resulted in the loss of power to the left engine, and the collision with the building.
Final Report:

Crash of a Mitsubishi MU-2B-60 Marquise in Parker: 1 killed

Date & Time: Aug 4, 2005 at 0206 LT
Type of aircraft:
Operator:
Registration:
N454MA
Flight Type:
Survivors:
No
Schedule:
Salt Lake City - Denver
MSN:
1535
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4800
Captain / Total hours on type:
1200.00
Aircraft flight hours:
12575
Circumstances:
The commercial pilot was executing a precision instrument approach at night in instrument meteorological conditions when the airplane collided with terrain about four miles short of the runway. A review of air traffic control communications and radar data revealed the pilot was vectored onto the final approach course but never got established on the glide slope. Instead, he made a controlled descent below the glide slope as he proceeded toward the airport. When the airplane was five miles from the airport, a tower controller received an aural low altitude alert generated by the Minimum Safe Altitude Warning (MSAW) system. The tower controller immediately notified the pilot of his low altitude, but the airplane collided with terrain within seconds. Examination of the instrument approach system and onboard flight navigation equipment revealed no pre-mishap anomalies. A review of the MSAW adaptation parameters revealed that the tower controller would only have received an aural alarm for aircraft operating within 5 nm of the airport. However, the frequency change from the approach controller to the tower controller occurred when the airplane was about 10.7 miles from the airport, leaving a 5.7 mile segment where both controllers could receive visual alerts, but only the approach controller received an aural alarm. A tower controller does not utilize a radar display as a primary resource for managing air traffic. In 2004, the FAA changed a policy, which eliminated an approach controller's responsibility to inform a tower controller of a low altitude alert if the tower had MSAW capability. The approach controller thought the MSAW alarm parameter was set 10 miles from the airport, and not the 5 miles that existed at the time of the accident. Subsequent investigation revealed, that The FAA had improperly informed controllers to ensure they understood the alarm parameters for control towers in their area of responsibility. This led the approach controller to conclude that the airplane was no longer her responsibility once she handed it over to the tower controller. Plus, the tone of the approach controller's aural MSAW alarm was not sufficient in properly alerting her of the low altitude alert.
Probable cause:
The pilot’s failure to fly a stabilized instrument approach at night which resulted in controlled flight into terrain. Contributing factors were; the dark night, low clouds, the inadequate design and function of the airport facility’s Minimum Safe Altitude Warning System (MSAW), and the FAA’s inadequate procedure for updating information to ATC controllers.
Final Report:

Crash of an Airbus A340-313X in Toronto

Date & Time: Aug 2, 2005 at 1602 LT
Type of aircraft:
Operator:
Registration:
F-GLZQ
Survivors:
Yes
Schedule:
Paris - Toronto
MSN:
289
YOM:
1999
Flight number:
AF358
Country:
Crew on board:
12
Crew fatalities:
Pax on board:
297
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15411
Captain / Total hours on type:
1788.00
Copilot / Total flying hours:
4834
Copilot / Total hours on type:
2502
Aircraft flight hours:
28426
Aircraft flight cycles:
3711
Circumstances:
The Air France Airbus A340-313 aircraft (registration F-GLZQ, serial number 0289) departed Paris, France, at 1153 Coordinated Universal Time (UTC) as Air France Flight 358 on a scheduled flight to Toronto, Ontario, with 297 passengers and 12 crew members on board. Before departure, the flight crew members obtained their arrival weather forecast, which included the possibility of thunderstorms. While approaching Toronto, the flight crew members were advised of weather-related delays. On final approach, they were advised that the crew of an aircraft landing ahead of them had reported poor braking action, and Air France Flight 358’s aircraft weather radar was displaying heavy precipitation encroaching on the runway from the northwest. At about 200 feet above the runway threshold, while on the instrument landing system approach to Runway 24L with autopilot and autothrust disconnected, the aircraft deviated above the glideslope and the groundspeed began to increase. The aircraft crossed the runway threshold about 40 feet above the glideslope. During the flare, the aircraft travelled through an area of heavy rain, and visual contact with the runway environment was significantly reduced. There were numerous lightning strikes occurring, particularly at the far end of the runway. The aircraft touched down about 3800 feet down the runway, reverse thrust was selected about 12.8 seconds after landing, and full reverse was selected 16.4 seconds after touchdown. The aircraft was not able to stop on the 9000-foot runway and departed the far end at a ground speed of about 80 knots. The aircraft stopped in a ravine at 2002 UTC (1602 eastern daylight time) and caught fire. All passengers and crew members were able to evacuate the aircraft before the fire reached the escape routes. A total of 2 crew members and 10 passengers were seriously injured during the crash and the ensuing
evacuation.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The crew conducted an approach and landing in the midst of a severe and rapidly changing thunderstorm. There were no procedures within Air France related to distance required from thunderstorms during approaches and landing, nor were these required by regulations.
2. After the autopilot and autothrust systems were disengaged, the pilot flying (PF) increased the thrust in reaction to a decrease in the airspeed and a perception that the aircraft was sinking. The power increase contributed to an increase in aircraft energy and the aircraft deviated above the glide path.
3. At about 300 feet above ground level (agl), the surface wind began to shift from a headwind component to a 10-knot tailwind component, increasing the aircraft’s groundspeed and effectively changing the flight path. The aircraft crossed the runway threshold about 40 feet above the normal threshold crossing height.
4. Approaching the threshold, the aircraft entered an intense downpour, and the forward visibility became severely reduced.
5. When the aircraft was near the threshold, the crew members became committed to the landing and believed their go-around option no longer existed.
6. The touchdown was long because the aircraft floated due to its excess speed over the threshold and because the intense rain and lightning made visual contact with the runway very difficult.
7. The aircraft touched down about 3800 feet from the threshold of Runway 24L, which left about 5100 feet of runway available to stop. The aircraft overran the end of Runway 24L at about 80 knots and was destroyed by fire when it entered the ravine.
8. Selection of the thrust reversers was delayed as was the subsequent application of full reverse thrust.
9. The pilot not flying (PNF) did not make the standard callouts concerning the spoilers and thrust reversers during the landing roll. This further contributed to the delay in the PF selecting the thrust reversers.
10. Because the runway was contaminated by water, the strength of the crosswind at touchdown exceeded the landing limits of the aircraft.
11. There were no landing distances indicated on the operational flight plan for a contaminated runway condition at the Toronto/Lester B. Pearson International Airport (CYYZ).
12. Despite aviation routine weather reports (METARs) calling for thunderstorms at CYYZ at the expected time of landing, the crew did not calculate the landing distance required for Runway 24L. Consequently, they were not aware of the margin of error available for the landing runway nor that it was eliminated once the tailwind was experienced.
13. Although the area up to 150 m beyond the end of Runway 24L was compliant with Aerodrome Standards and Recommended Practices (TP 312E), the topography of the terrain beyond this point, along the extended runway centreline, contributed to aircraft damage and to the injuries to crew and passengers.
14. The downpour diluted the firefighting foam agent and reduced its efficiency in dousing the fuel-fed fire, which eventually destroyed most of the aircraft.
Findings as to Risk :
1. In the absence of clear guidelines with respect to the conduct of approaches into convective weather, there is a greater likelihood that crews will continue to conduct approaches into such conditions, increasing the risk of an approach and landing accident.
2. A policy where only the captain can make the decision to conduct a missed approach can increase the likelihood that an unsafe condition will not be recognized early and, therefore, increase the time it might otherwise take to initiate a missed approach.
3. Although it could not be determined whether the use of the rain repellent system would have improved the forward visibility in the downpour, the crew did not have adequate information about the capabilities and operation of the rain repellent system and did not consider using it.
4. The information available to flight crews on initial approach in convective weather does not optimally assist them in developing a clear idea of the weather that may be encountered later in the approach.
5. During approaches in convective weather, crews may falsely rely on air traffic control (ATC) to provide them with suggestions and directions as to whether to land or not.
6. Some pilots have the impression that ATC will close the airport if weather conditions make landings unsafe; ATC has no such mandate.
7. Wind information from ground-based measuring systems (anemometers) is critical to the safe landing of aircraft. Redundancy of the system should prevent a single-point failure from causing a total loss of relevant wind information.
8. The emergency power for both the public address (PA) and EVAC alert systems are located in the avionics bay. A less vulnerable system and/or location would reduce the risk of these systems failing during a survivable crash.
9. Brace commands were not given by the cabin crew during this unexpected emergency condition. Although it could not be determined if some of the passengers were injured as a result, research shows that the risk of injury is reduced if passengers brace properly.
10. Safety information cards given to passengers travelling in the flight decks of Air France Airbus A340-313 aircraft do not include illustrations depicting emergency exit windows, descent ropes or the evacuation panel in the flight deck doors.
11. There are no clear visual cues to indicate that some dual-lane slides actually have two lanes. As a result, these slides were used mostly as single-lane slides. This likely slowed the evacuation, but this fact was not seen as a contributing factor to the injuries suffered by the passengers.
12. Although all passengers managed to evacuate, the evacuation was impeded because nearly 50 per cent of the passengers retrieved carry-on baggage.
Other Findings:
1. There is no indication that the captain’s medical condition or fatigue played a role in this occurrence.
2. The crew did not request long aerodrome forecast (TAF) information while en route. This did not affect the outcome of this occurrence because the CYYZ forecast did not change appreciably from information the flight crew members received before departure, and they received updated METARs for CYYZ and Niagara Falls International Airport (KIAG).
3. The possibility of a diversion required the flight crew to check the weather for various potential alternates and to complete fuel calculations. Although these activities consumed considerable time and energy, there is no indication that they were unusual for this type of operation or that they overtaxed the flight crew.
4. The decision to continue with the approach was consistent with normal industry practice, in that the crew could continue with the intent to land while maintaining the option to discontinue the approach if they assessed that the conditions were becoming unsafe.
5. There is no indication that more sophisticated ATC weather radar information, had it been available and communicated to the crew, would have altered their decision to continue to land.
6. It could not be determined why door L2 opened before the aircraft came to a stop.
7. There is no indication that the aircraft was struck by lightning.
8. There is no information to indicate that the aircraft encountered windshear during its approach and landing.
9. The flight crew seats are certified to a lower standard than the cabin seats, which may have been a factor in the injuries incurred by the captain.
Final Report:

Crash of a Casa-Nurtanio CN-235M-10 (IPTN) in Lhokseumawe: 3 killed

Date & Time: Jul 21, 2005 at 1138 LT
Operator:
Registration:
A-2301
Flight Type:
Survivors:
Yes
Schedule:
Banda Aceh - Lhokseumawe
MSN:
N016
YOM:
1991
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
20
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Upon landing, the aircraft went out of control, veered off runway to the left and came to rest, broken in two. Three passengers, two Lieutenant and one Major, were killed while 20 other occupants were injured. The aircraft was destroyed. It was reported that one of the engine lost power at flare, causing the aircraft to land hard and to become uncontrollable.

Crash of a Yakovlev Yak-40 in Caticlan

Date & Time: Jul 19, 2005 at 0958 LT
Type of aircraft:
Operator:
Registration:
RP-C2803
Survivors:
Yes
Schedule:
Manila - Caticlan
MSN:
9 43 05 37
YOM:
1975
Flight number:
ISL210
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
20
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Caticlan-Malay Airport, the three engine aircraft was too low and struck the ground short of runway 06. A tyre burst as it struck the raised lip of the runway. When removing the airplane from the runway the undercarriage collapsed. The aircraft came to rest after a course of few dozen metres. All 23 occupants escaped uninjured and the aircraft was damaged beyond repair. Caticlan Airport has a concrete runway of 950 metres long.
Probable cause:

Crash of a Learjet 35A in Eagle

Date & Time: Jul 15, 2005 at 0930 LT
Type of aircraft:
Operator:
Registration:
N620JM
Flight Type:
Survivors:
Yes
Schedule:
Aspen – Eagle
MSN:
35-207
YOM:
1979
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
29612
Captain / Total hours on type:
8967.00
Copilot / Total flying hours:
9433
Copilot / Total hours on type:
75
Aircraft flight hours:
8234
Circumstances:
A witness saw the airplane approach from the east. She said that the airplane came in "pretty fast" and touched down "approximately half way down the runway." The witness said, "The nose was down. He hit the ground and within 3 seconds he was off the runway and gone. Then all you saw was smoke." The witness said when the airplane hit "the front end shook. It wobbled like a kid on a tricycle. When it shook, it kind of looked like it [the airplane] bounced. Then it was gone." The control tower operator said he heard the captain say something over the radio, which caused him to look in the direction of the airplane. The tower operator saw the airplane off the runway, the main landing gear came off behind the airplane, and the airplane caught fire. The tower operator said he saw four people get out of the airplane. The airplane came to rest in a shallow ravine approximately 331 feet north of the runway. An examination of the airplane showed impact damage to the nose gear and nose gear wheel well. An examination of the airplane's systems revealed no anomalies.
Probable cause:
The pilot's improper flare resulting in the hard landing and the fractured nose gear attachment, and the subsequent loss of control. Factors contributing to the accident were the high airspeed on approach, the pilot's improper in-flight planning/decision, and the pilot's inability to maintain directional control after the gear failure.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Mount Hotham: 3 killed

Date & Time: Jul 8, 2005 at 1725 LT
Operator:
Registration:
VH-OAO
Survivors:
No
Schedule:
Melbourne - Mount Hotham
MSN:
31-8252021
YOM:
1982
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
4770
Captain / Total hours on type:
1269.00
Aircraft flight hours:
9137
Circumstances:
On 8 July 2005, the pilot of a Piper PA-31-350 Navajo Chieftain, registered VH-OAO, submitted a visual flight rules (VFR) flight plan for a charter flight from Essendon Airport to Mount Hotham, Victoria. On board the aircraft were the pilot and two passengers. At the time, the weather conditions in the area of Mount Hotham were extreme. While taxiing at Essendon, the pilot requested and was granted an amended airways clearance to Wangaratta, due to the adverse weather conditions at Mount Hotham. The aircraft departed Essendon at 1629 Eastern Standard Time. At 1647 the pilot changed his destination to Mount Hotham. At 1648, the pilot contacted Flightwatch and requested that the operator telephone the Mount Hotham Airport and advise an anticipated arrival time of approximately 1719. The airport manager, who was also an accredited meteorological observer, told the Flightwatch operator that in the existing weather conditions the aircraft would be unable to land. At 1714, the pilot reported to air traffic control that the aircraft was overhead Mount Hotham and requested a change of flight category from VFR to instrument flight rules (IFR) in order to conduct a Runway 29 Area Navigation, Global Navigation Satellite System (RWY 29 RNAV GNSS) approach via the initial approach fix HOTEA. At 1725 the pilot broadcast on the Mount Hotham Mandatory Broadcast Zone frequency that the aircraft was on final approach for RWY 29 and requested that the runway lights be switched on. No further transmissions were received from the aircraft. The wreckage of the aircraft was located by helicopter at 1030 on 11 July. The aircraft had flown into trees in a level attitude, slightly banked to the right. Initial impact with the ridge was at about 200 ft below the elevation of the Mount Hotham aerodrome. The aircraft had broken into several large sections and an intense fire had consumed most of the cabin. The occupants were fatally injured.
Probable cause:
Findings:
• There were no indications prior to, or during the flight, of problems with any aircraft systems that may have contributed to the circumstances of the occurrence.
• The pilot continued flight into forecast and known icing conditions in an aircraft not approved for flight in icing conditions.
• The global navigation satellite constellation was operating normally.
• The pilot did not comply with the requirements of the published instrument approach procedure.
• The pilot was known, by his Chief Pilot and others, to adopt non-standard approach procedures to establish his aircraft clear of cloud when adverse weather conditions existed at Mount Hotham.
• The pilot may have been experiencing self-imposed and external pressures to attempt a landing at Mount Hotham.
• Terrain features would have been difficult to identify due to a heavy layer of snow, poor visibility, low cloud, continuing heavy snowfall, drizzle, sleet and approaching end of daylight.
• The pilot’s attitude, operational and compliance practices had been of concern to some Airservices’ staff.
• The operator’s operational and compliance history was recorded by CASA as being of concern, and as a result CASA staff continued to monitor the operator. However, formal surveillance of the operator in the preceding two years had not identified any significant operational issues.
Significant factors:
• The weather conditions at the time of the occurrence were extreme.
• The extreme weather conditions were conducive to visual illusions associated with a flat light phenomenon.
• The pilot did not comply with the requirements of flight under either the instrument flight rules (IFR) or the visual flight rules (VFR).
• The pilot did not comply with the requirements of the published instrument approach procedure and flew the aircraft at an altitude that did not ensure terrain clearance.
• The aircraft accident was consistent with controlled flight into terrain.
Final Report: