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 Cessna 208B Grand Caravan in Globe

Date & Time: Jul 22, 2005 at 0830 LT
Type of aircraft:
Registration:
N717BT
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Phoenix – Globe – Safford
MSN:
208B-0863
YOM:
2000
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5545
Captain / Total hours on type:
203.00
Aircraft flight hours:
4461
Circumstances:
The airplane impacted a road and scrub brush during a forced landing, which was preceded by a total loss of engine power. According to the pilot, he heard a loud "thunk" during takeoff climb and noted a loss of engine power. He manipulated the power lever from the full forward position to the full aft position ("stop-to-stop") and noted he had no power. Post-accident examination of the Pratt & Whitney Canada PT6A -114A engine revealed that the compressor turbine (CT) vane's outer rim liberated a section of metal that damaged the turbine blades downstream. The area of liberated material from the CT vane outer rim was examined by the manufacturer's metallurgists. The fracture surface of the outer rim showed evidence of fatigue with signs of oxidation in some areas indicating the crack had been in existence for some time. The liberated material impact damaged the CT blades and resulted in a loss of power. Review of the operator's records revealed that the engine was approved for an extension beyond the normally recommended 3,600-hour overhaul period, to 5,100 hours. The engine had accumulated 4,461.3 hours at the time of the accident. In addition, the turbine section (hot section) had a recommended overhaul period of 1,800 hours; however, the operator instead elected to utilize an engine trend monitoring program in accordance with a manufacturer issued service bulletin. Many errors were noted with the operator's manually recorded data utilized for the trend monitoring. However, it is not likely that the engine trend data, even had it been correctly recorded and monitored, would have depicted the fatigue cracking in the CT vane outer rim. As a result, the manufacturer issued a service information letter (SIL) PT6A116 in January 27, 2003 (following a similar investigation), which reminded operators to conduct borescope inspections of the CT vane during routine fuel nozzle maintenance, as the manufacturer's maintenance manual recommended. Review of the maintenance record entries for the accident engine revealed no evidence that a borescope inspection had been conducted in conjunction with the fuel nozzle checks.
Probable cause:
The fatigue failure of the compressor turbine stator vane, the liberation of vane material into the compressor turbine, and the total loss of engine power. Also causal was the operator's failure to inspect the compressor turbine vane during fuel nozzle checks.
Final Report:

Crash of a Rockwell Grand Commander 680FL in North Las Vegas

Date & Time: Jul 21, 2005 at 1707 LT
Operator:
Registration:
N7UP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
North Las Vegas - North Las Vegas
MSN:
680-1349-29
YOM:
1963
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5285
Captain / Total hours on type:
75.00
Aircraft flight hours:
8942
Circumstances:
The airplane descended into the ground during takeoff-initial climb on a local fire reconnaissance flight. Witnesses reported that airplane became airborne, but was not climbing, and it continued down the runway in a nose-up attitude in ground effect until impacting terrain about 600 feet southeast from the departure end of the runway. The ambient temperature was about 107 degrees Fahrenheit, and the density altitude was calculated at 5,878 feet mean sea level. On scene examination found the flaps in the 30-degree position, which also corresponded to the flap actuator position. The cockpit indicator for the flaps also showed a 30-degree extension. A subsequent bench test of the combined flap/gear selector valve was conducted. During the initial inspection, both the gear selector and the flap selector valves were bent, but otherwise operational. The "stop-pin" on the flap selector lever was missing. There was no leakage of fluid during this test. Examination of both engines revealed no abnormalities, which would prevent normal operations. The aircraft flight manual specifies that the flaps should be set at 1/4 down (10 degrees) for normal takeoff.
Probable cause:
The pilot's excessive selection of flaps prior to takeoff, which resulted in a failure to obtain/maintain an appropriate climb airspeed, and an inadvertent stall/mush during takeoff-initial climb. A factor contributing to the accident was a high density altitude.
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:

Crash of a Piper PA-46-310P Malibu in Grand Rapids: 1 killed

Date & Time: Jul 4, 2005 at 1758 LT
Registration:
N4386G
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Grand Rapids – Minneapolis
MSN:
46-8508037
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2200
Aircraft flight hours:
1856
Circumstances:
The airplane was destroyed on impact with terrain during a forced landing following an observed in-flight loss of engine power after takeoff. A witness observed the takeoff and stated that the airplane took off from the end of runway 34. About halfway down the runway the airplane emitted a sound like a rapid misfire, a pop, and then no more audible engine sounds. The airplane was about 300 to 400 feet above ground level at that point. He said that the airplane turned right then turned left to a bank where the wing was straight down. The airplane's wings then leveled, the airplane descended, and it impacted terrain. He stated that the time from the sounds to the impact was about two to three seconds. An on-scene examination revealed no airframe pre-impact anomalies. An engine examination revealed a cracked crankshaft propeller flange. The engine without the turbochargers and with the original crankshaft was test run up to 2,100 RPM. A propeller and governor inspection revealed no anomalies. Examination of the turbocharger system's exhaust bypass valve assembly revealed its butterfly valve was stuck (bound) in the extended closed position. The engine's cracked crankshaft was removed and a serviceable crankshaft was installed. The engine was test run again with a serviceable exhaust bypass valve assembly. The engine produced rated power. The original exhaust bypass valve assembly was reinstalled. The exhaust bypass valve assembly's wastegate bound again during an engine run and a loss of engine power was observed. Sectioning of the bypass valve assembly revealed a bent wastegate shaft. The valve assembly lever arm was bent and exhibited pre-impact tool marks consistent with pliers loosening a bound wastegate shaft. The airplane's pilot operating handbook and Federal Aviation Administration (FAA) approved airplane flight manual (POH), in part, stated, "ENGINE POWER LOSS DURING TAKEOFF If sufficient runway remains for a normal landing, leave gear down and land straight ahead." The engine manufacturer's maintenance and operator's manual stated that the wastegate is required to be checked for operation and condition during 100 hour inspections. The manual did not specify a procedure for maintenance personnel on how to check the wastegate's operation and its acceptable condition. National Transportation Safety Board Recommendation A-94-081, issued to the FAA in 1994, stated, "Require the amendment of pilot operating handbooks and airplane flight manuals applicable to aircraft equipped with engine turbochargers by including in the 'Emergency Procedures' section information regarding turbocharger failure. The information should include procedures to minimize potential hazards relating to fire in flight and/or loss of engine power." The airplane's POH latest revision was dated October 14, 2002 and review of the emergency procedures section showed that the POH did not contain information, procedures, or amplified procedures on turbocharger failures. The airplane accumulated 8.7 hours of operation since the last annual inspection.
Probable cause:
An observed loss of engine power due to the bound/jammed turbocharger wastegate during takeoff, the pilot not maintaining airplane control, and the stall he inadvertently encountered. A factor was the maintenance personnel not replacing the turbocharger wastegate bypass valve assembly during the last annual inspection 8.7 hours of operation prior to the accident. An additional factor was the manufacturer's insufficiently defined inspection conditions for the bypass valve's proper operation.
Final Report:

Crash of a Douglas DC-10-30ER in Chittagong

Date & Time: Jul 1, 2005 at 0853 LT
Type of aircraft:
Operator:
Registration:
S2-ADN
Survivors:
Yes
Schedule:
Dubai - Chittagong - Dhaka
MSN:
46542
YOM:
1979
Flight number:
BG048
Country:
Region:
Crew on board:
15
Crew fatalities:
Pax on board:
201
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Dubai on a flight to Dhaka with an intermediate stop in Chittagong, carrying 201 passengers and a crew of 15. Weather conditions at Chittagong Airport were poor with a visibility of 1,800 metres in rain, 5-7 oktas cloud at 700 feet, 3-4 oktas cloud at 1,300 feet, 0-2 oktas cloud at 2,600 feet, overcast at 8,000 feet with CB's, temporary visibility of 2 km and wind from 180 at 6 knots. On final approach, the aircraft was unstable but the captain decided to continue the descent. After touchdown on runway 23, the aircraft deviated from the centerline to the right, causing the right main gear to veer off runway. While contacting soft ground, it was torn off, causing the engine n°3 to be partially sheared off. The aircraft slid for few dozen metres before coming to rest in a grassy area along the runway. All 216 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Wrong approach configuration on part of the crew who failed to follow the SOP's and his failure to initiate a go-around while the aircraft was unstable on short final.

Crash of a Piper PA-31P Pressurized Navajo in Fort Payne

Date & Time: Jun 30, 2005 at 0816 LT
Type of aircraft:
Operator:
Registration:
N4200N
Flight Phase:
Survivors:
Yes
Schedule:
Fort Payne – Gulfport
MSN:
31P-7530006
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1486
Captain / Total hours on type:
79.00
Aircraft flight hours:
4022
Circumstances:
Shortly after liftoff, about 20 feet above the ground, the pilot noticed a drop in the right engine manifold pressure. As the airplane began a right roll, efforts by the pilot to arrest the roll failed. When the pilot decided to put the airplane back on the ground, the right wing collided with the ground, the airplane cart wheeled and came to rest on its belly and burst into flames. Examination of the wreckage site revealed the aircraft located approximately 200 feet on the northwest side of the runway 22 centerline. The left fuel tank was ruptured and the left side of the airplane was fire damaged. Both occupants were slightly injured and the aircraft was damaged beyond repair.
Probable cause:
The loss of engine power due to the failure of the aft clamp connecting the turbocharger compressor outlet to the intercooler ducting which resulted in reduced aircraft performance during takeoff.
Final Report: