Crash of a Gulfstream GV in West Palm Beach

Date & Time: Feb 14, 2002 at 0649 LT
Type of aircraft:
Operator:
Registration:
N777TY
Flight Type:
Survivors:
Yes
Schedule:
West Palm Beach - Teterboro
MSN:
508
YOM:
1996
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13280
Captain / Total hours on type:
1227.00
Copilot / Total flying hours:
18477
Copilot / Total hours on type:
450
Aircraft flight hours:
1945
Circumstances:
After a normal taxi and takeoff, the airplane's landing gear would not retract after liftoff. After unsuccessfully attempting to raise the landing gear manually, the flight crew elected to return to the airport. During the landing flare, the ground spoilers deployed when the throttles were brought to idle. The airplane descended rapidly and landed hard, and the right main landing gear collapsed. The investigation determined that a mechanic had wedged wooden sticks into the airplane's weight-on-wheels (WOW) switches to force them into the ground mode while the airplane was on jacks during maintenance. The mechanic said that he used the sticks to disable the WOW switches to gain access to the maintenance data acquisition unit, which was necessary to troubleshoot an overspeed alert discrepancy. After the maintenance was performed, the sticks were not removed, and the airplane was returned to service. No notation about the disabled WOW switches was entered in the work logs. Postaccident ground testing of the accident airplane's cockpit crew alerting system and examination of flight data recorder (FDR) data determined that the system was functioning properly and that it produced a blue WOW fault message, an amber WOW fault message, and a red GND SPOILER warning message when the accident flight conditions were recreated. The messages produced were consistent with FDR and cockpit voice recorder (CVR) information. Ground spoilers will deploy when the throttles are brought to idle if the spoilers are armed and the WOW switches are in the ground mode. The G-V Quick Reference Handbook (QRH) cautions flight crews not to move thrust reverser levers and to switch the GND SPOILER armed to off following an amber WOW FAULT message. A red GND SPOILER message calls for the flight crew to disarm the ground spoilers and pull the circuit breakers to make sure the spoilers are not rearmed inadvertently. Based on CVR information, there was no indication that the flight crew followed checklist procedures contained in the G-V's QRH that referenced WOW faults or GND SPOILER faults. Preflight checklist procedures also called for the flight crew to conduct a visual inspection of the WOW switches.
Probable cause:
The flight crew's failure to follow preflight inspection/checklist procedures, which resulted in their failure to detect wooden sticks in the landing gear weight-on-wheel switches and their failure in flight to respond to crew alert messages to disarm the ground spoilers, which deployed when the crew moved the throttles to idle during the landing flare, causing the airplane to land hard. Contributing to the accident was maintenance personnel's failure to remove the sticks from the weight-on-wheels switches after maintenance was completed.
Final Report:

Crash of a Tupolev TU-154M near Khorramabad: 119 killed

Date & Time: Feb 12, 2002 at 0755 LT
Type of aircraft:
Operator:
Registration:
EP-MBS
Survivors:
No
Site:
Schedule:
Tehran - Khorramabad
MSN:
91A871
YOM:
1991
Flight number:
IRB956
Country:
Region:
Crew on board:
12
Crew fatalities:
Pax on board:
107
Pax fatalities:
Other fatalities:
Total fatalities:
119
Aircraft flight hours:
12701
Aircraft flight cycles:
5516
Circumstances:
Following an uneventful flight from Tehran, the crew started the descent to Khorramabad Airport runway 11 in bad weather conditions. In poor visibility, the crew failed to realize he was off course when the aircraft struck the slope of a mountain located few km northeast from the city of Sarab-e Dowreh, about 25 km northwest from the runway 11 threshold. The wreckage was found few hours later on a snow covered rock wall. The aircraft disintegrated on impact and all 119 occupants were killed, among them four Spanish citizens.
Probable cause:
Controlled flight into terrain after the crew failed to follow the approach procedures and the company SOP's. This caused the aircraft to deviate from the approach path by 3 nm to the north when it struck the mountain that was shrouded in clouds. The lack of visibility due to poor weather conditions was a contributing factor.

Crash of a Mitsubishi MU-300 Diamond in Cleveland

Date & Time: Feb 10, 2002 at 2302 LT
Type of aircraft:
Operator:
Registration:
N541CW
Flight Type:
Survivors:
Yes
Schedule:
Chicago - Cleveland
MSN:
004
YOM:
1980
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12478
Captain / Total hours on type:
2000.00
Copilot / Total flying hours:
3899
Copilot / Total hours on type:
326
Aircraft flight hours:
7457
Circumstances:
As the airplane was descending to the airport, the pilot-in-command (PIC) calculated that the required distance to land on a dry runway would be 2,720 feet. The second-in-command (SIC) stated to the PIC, "all right if I touch down and there's no brakes I'm going around." The ILS Runway 23 approach was in use, and the braking action was reported "poor" by a Hawker Jet, which had landed prior to the accident flight. All runway surfaces were covered with a thin layer of snow. The airplane touched down with about 2,233 feet of runway remaining, of the 5,101-foot long runway. The airplane departed the end of the runway, and proceeded into an overrun grassy area, where the nose landing gear assembly collapsed. The tower controller advised the flightcrew prior to landing that the wind conditions were from 330 degrees at 18 knots. According to the airplane's Pilot's Operating Manual, the estimated landing distance on a dry runway, for the conditions at the time of the accident, was about 2,750 feet. No charts were available in the FAA approved Airplane Flight Manual, to compute a landing distance incorporating a contaminated runway. Review of 14 CFR Part 25.1, which prescribed airworthiness standards for the issue of type certificates, and changes to those certificates, for transport category airplanes, revealed, "For landplanes and amphibians, the landing distance on land must be determined on a level, smooth, dry, hard-surfaced runway." There were no requirements for the applicant to determine landing distances on a wet or contaminated runway. The latest weather recorded at the airport, included winds from 330 degrees at 12 knots, gusts to 22 knots; visibility 3/4 statute mile, light snow; and overcast clouds at 300 feet.
Probable cause:
The pilot's failure to obtain the proper touch down point on the runway, and the pilot-in-commands failure to initiate a go-round. Factors in the accident were the tailwind condition, the snow-covered runway.
Final Report:

Crash of a Piper PA-31T Cheyenne II in Hobbs

Date & Time: Feb 4, 2002 at 1907 LT
Type of aircraft:
Registration:
N794CA
Flight Type:
Survivors:
Yes
Schedule:
Las Vegas - Hobbs
MSN:
31-8120018
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2893
Captain / Total hours on type:
765.00
Aircraft flight hours:
4900
Circumstances:
At the conclusion of a dark night IMC cross-country flight, the pilot was being vectored onto the ILS approach. After stabilizing, the approach "was normal." At decision altitude, the pilot indicated that he could see the approach lights and the runway, but was not in a position to land so he executed a missed approach. After being vectored around for another approach, he stated that he was on the localizer but was "high" on the glide slope. After giving "a little" nose down pitch, he became distracted when the autopilot became "accidentally disengaged." The pilot stated that he "inadvertently descended through the glide slope and impacted the ground short of the runway." He further stated that the "first indication" that he was low was when the aircraft "struck the ground." The aircraft was destroyed on impact. A facility check conducted by the FAA of the ILS found all parameters within normal specifications.
Probable cause:
The pilot's failure to maintain the proper glidepath during the instrument approach. Contributing factors were the dark night light conditions and the pilot's diverted attention.
Final Report:

Crash of a Technoavia SM-92G Turbo Finist in Thiene

Date & Time: Feb 3, 2002 at 1630 LT
Registration:
HA-YDG
Survivors:
Yes
Site:
Schedule:
Thiene - Thiene
MSN:
00-004
YOM:
1995
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
500
Captain / Total hours on type:
40.00
Circumstances:
The single engine airplane departed Thiene Airstrip at 1540LT for a local flight, carrying nine skydivers, one observer and one pilot. At the altitude of 13,500 feet, seven skydivers jumped while three others decided to stay in the cabin because the visibility was poor due to foggy conditions. While returning to his departure point, the pilot encountered poor visibility and completed two unsuccessful approach. He eventually decided to divert to Asiago Airport located 24 km from his position but this decision was taken too late. While circling around the airport, the engine failed and the aircraft stalled, struck the roof of a house and crashed in Rozzampia, less than one km east of the airfield. All four occupants were injured and the aircraft was damaged beyond repair.
Probable cause:
The following contributing factors were identified:
- Weather conditions were marginal with thick fog reducing the visibility to 100 metres,
- Poor flight planning as the pilot failed to refuel the airplane prior to departure and ignored the instability of the weather conditions,
- The pilot's decision to divert to Asiago Airfield was taken too late,
- Poor coordination with the people in place at the Thiene Aerodrome,
- The pilot's inexperience.
Final Report:

Crash of a Piper PA-42-720 Cheyenne II-XL in Ames

Date & Time: Jan 30, 2002 at 1810 LT
Type of aircraft:
Operator:
Registration:
N66MT
Survivors:
Yes
Schedule:
Broomfield – Ames
MSN:
42-8166060
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot said he was on the glide slope for an ILS approach. The pilot said, "The autopilot was coupled on to the approach. The autopilot also coupled on to the Glide slope. Approximately 2-1/2 to 3 miles out, we visually had approach lights and runway lights. I then disconnected the autopilot and yaw damper, and hand flew a visual approach using the glide slope indicator as a cross check for a correct glide path to the airport. Continuing visually on the approach, I checked the GS (glide slope) and it indicated we were slightly above glide path, but was corrected, and seconds later hit a pole going through electrical wires, coming to rest short of the approach lights and to the right." An examination of the airplane revealed no anomalies. An examination of the ILS approach to the runway showed the facility operated satisfactorily.
Probable cause:
The pilot's failure to maintain the proper glide path during the final portion of the approach. Factors relating to this accident were the low altitude and the utility pole.
Final Report:

Crash of a PZL-Mielec AN-28 in Kavak

Date & Time: Jan 29, 2002 at 1130 LT
Type of aircraft:
Registration:
YV-1043CP
Flight Type:
Survivors:
Yes
Schedule:
Santa Elena de Uairén - Kavak
MSN:
1AJ009-11
YOM:
1991
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
15
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown on dirt runway 06/24 at Kavak Airstrip, the right main gear collapsed. The aircraft went out of control, veered off runway to the right and came to rest. All 17 occupants escaped uninjured while the aircraft was damaged beyond repair. The runway conditions was poor at the time of the accident.
Probable cause:
Failure of the right main gear due to the presence of fatigue cracks. The poor runway conditions was a contributing factor.

Crash of an Antonov AN-12 in Luena: 5 killed

Date & Time: Jan 27, 2002
Type of aircraft:
Operator:
Registration:
T-304
Flight Type:
Survivors:
Yes
Schedule:
Luanda - Luena
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
34
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
While approaching runway 11/29 in heavy rain falls, the four engine aircraft crashed two km short of runway. Two crew members and three passengers were killed. The aircraft was completing a flight from Luanda to Luena on behalf of the Government of the State of Moxico.

Crash of a Fokker F27 Friendship 400M in Guayaramerín

Date & Time: Jan 22, 2002
Type of aircraft:
Operator:
Registration:
FAB-94
Flight Type:
Survivors:
Yes
MSN:
10600
YOM:
1980
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
40
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While descending to Guayaramerín Airport, about seven minutes prior to ETA, the pilot informed ATC about the failure of the left engine and was able to continue the approach. After touchdown, the aircraft failed to stop within the remaining distance. It overran, lost its undercarriage and right wing and came to rest. All 44 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
Failure of the left engine on approach for unknown reasons.

Crash of a Pilatus PC-6/B2-H4 Turbo Porter in Bugalaga

Date & Time: Jan 18, 2002 at 1000 LT
Operator:
Registration:
PK-YPC
Flight Type:
Survivors:
Yes
Schedule:
Nabire - Bugalaga
MSN:
726
YOM:
1971
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
8500
Circumstances:
Upon landing on runway 06, the single engine aircraft bounced twice then veered off runway and came to rest in bushes. Both pilots escaped unhurt while the aircraft was damaged beyond repair.
Probable cause:
The crew completed the landing roll with a tailwind component and the runway was in poor conditions at the time of the accident, which remained a contributing factor.