Crash of a GAF Nomad N.22B off Zamboanga

Date & Time: Dec 28, 1993
Type of aircraft:
Operator:
Registration:
21
Flight Phase:
Survivors:
Yes
Schedule:
Zamboanga - Catobato City
MSN:
21
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Zamboanga City Airport on a survey flight for a missing vessel. En route, the crew encountered an unexpected situation and was forced to ditch the aircraft in the Igat Bay off Zamboanga. All six occupants were rescued while the aircraft sank and was lost.

Crash of a De Havilland DHC-6 Twin Otter 300 off Dakar: 3 killed

Date & Time: Dec 9, 1993 at 1839 LT
Operator:
Registration:
6V-ADE
Survivors:
No
Schedule:
Saint-Louis - Dakar
MSN:
393
YOM:
1973
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Following an uneventful flight from Saint Louis, the crew was cleared to descend to Dakar-Yoff Airport and was instructed to maintain 3,000 feet over YF VOR. At the same time, a NAMC YS-11A-117 operated by Gambia Airways departed Dakar-Yoff Airport on a regular schedule flight to Banjul. Registered C5-GAA, the aircraft was carrying 34 passengers and a crew of four. Its pilots were instructed to climb via radial 140 and maintain the altitude of 2,000 feet while over YF VOR. When both aircraft reached the YF VOR, they collided. While the crew of the NAMC was able to return to Dakar and land safely despite the left wing was partially torn off, the Twin Otter entered an uncontrolled descent and crashed in the sea few km offshore. All three occupants were killed.
Probable cause:
It was determined that both crew failed to respect their assigned altitude, causing both aircraft to collide. At the time of the accident, the Twin Otter was about 100-300 feet too low and the NAMC was about 700-900 feet too high.

Crash of a Britten-Norman BN-2A-27 Islander near Tuktoyaktuk: 7 killed

Date & Time: Dec 3, 1993 at 1713 LT
Type of aircraft:
Registration:
C-GMOP
Flight Phase:
Survivors:
No
Schedule:
Tuktoyaktuk - Inuvik
MSN:
398
YOM:
1974
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
3224
Captain / Total hours on type:
848.00
Aircraft flight hours:
9391
Circumstances:
On 03 December 1993, a Britten-Norman BN2A-20 Islander, registration C-GMOP, owned and operated by Arctic Wings and Rotors, departed Tuktoyaktuk, Northwest Territories, on a night
visual flight rules (VFR) flight to the Inuvik townsite airstrip. On board were the pilot and six passengers. The pilot took off from runway 09 at 1706:34 mountain standard time (MST) , and had turned the aircraft to a southerly direction when the right engine (Textron Lycoming IO540-K1B5) lost all power. At 1710:40, the pilot reported to Tuktoyaktuk Flight Service Station (FSS) that he had an engine problem and was trying to get back to the airport. At 1711:44, he reported that he was "presently heading back to the airport at this time." At 1711:58, he reported "showing six miles back from the airport at this time." The FSS specialist asked if he was declaring an emergency, and the pilot's response was indecisive. During the last radio transmission, there were indications of stress in the pilot's voice; however, there was no further mention of the specific nature of the problem. The pilot did not report his altitude during the conversations with the FSS. The transmission lasted approximately 15 seconds and ended at 1713:03. When the aircraft did not return to the airport, an air and ground search was initiated. The aircraft was located on an ice-covered lake approximately eight miles southeast of the airport. The aircraft struck the ice in a steep nose-down attitude. The engines and front of the aircraft penetrated the approximately two-foot-thick layer of ice. The remainder of the fuselage, wings, and empennage remained on the ice surface. The seven occupants were fatally injured. The accident occurred during the hours of darkness at approximately 1713 MST, at latitude 69°20'N, longitude 132°56'W, at an elevation of approximately 50 feet above sea level (asl).
Probable cause:
A magneto impulse coupling, worn beyond the prescribed limits, resulted in the failure of the right engine. Following the engine failure, the pilot mistrimmed the rudder and was unable to maintain control of the aircraft.
Final Report:

Crash of a De Havilland DHC-3 Otter off Thorne Bay

Date & Time: Nov 10, 1993
Type of aircraft:
Registration:
N98AT
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Thorne Bay - Ketchikan
MSN:
181
YOM:
1956
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane was returning to its base in Ketchikan following maintenance in Thorne Bay. Shortly after takeoff, while climbing, the engine lost power, forcing the pilot to attempt an emergency landing. While landing on water, a control wire snapped, causing the airplane to nose down in the water, coming to rest upside down. All three occupants were rescued by coastguard 20 minutes later and the aircraft sank.
Probable cause:
Loss of engine power on climb out for unknown reasons.

Crash of a Harbin Yunsunji Y-12-II in Jomsom

Date & Time: Nov 8, 1993
Type of aircraft:
Operator:
Registration:
9N-ACS
Survivors:
Yes
Schedule:
Pokhara - Jomsom
MSN:
0044
YOM:
1991
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 24, the aircraft was unable to stop within the remaining distance. It overran, went down an embankment and came to rest in the Gandaki River with its right wing torn off. All 19 occupants were rescued, among them both pilots and three passengers were injured.
Probable cause:
For unknown reasons, the crew landed 240 metres past the runway 24 threshold (runway 24 is 600 metres long).

Crash of a Boeing 747-409 in Hong Kong

Date & Time: Nov 4, 1993 at 1136 LT
Type of aircraft:
Operator:
Registration:
B-165
Survivors:
Yes
Schedule:
Taipei - Hong Kong
MSN:
24313
YOM:
1993
Flight number:
CI605
Country:
Region:
Crew on board:
22
Crew fatalities:
Pax on board:
274
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12469
Captain / Total hours on type:
3559.00
Copilot / Total flying hours:
5705
Copilot / Total hours on type:
908
Aircraft flight hours:
1969
Aircraft flight cycles:
359
Circumstances:
China Airlines' scheduled passenger flight CAL605 departed Taipei (TPE), Taiwan at 02:20 for the 75-minute flight to Hong Kong-Kai Tak (HKG). The departure and cruise phases were uneventful. During the cruise the commander briefed the co-pilot on the approach to Hong Kong using the airline's own approach briefing proforma as a checklist for the topics to cover. The briefing included the runway-in-use, navigation aids, decision height, crosswind limit and missed approach procedure. He paid particular attention to the crosswind and stated that, should they encounter any problem during the approach, they would go-around and execute the standard missed approach procedure. The commander did not discuss with the co-pilot the autobrake setting, the reverse thrust power setting or their actions in the event of a windshear warning from the Ground Proximity Warning System (GPWS). Weather reports indicated strong gusty wind conditions, rain and windshear. On establishing radio contact with Hong Kong Approach Control at 03:17, the crew were given radar control service to intercept the IGS approach to runway 13 which is offset from the extended runway centreline by 47°. After intercepting the IGS localiser beam, the pilots changed frequency to Hong Kong Tower and were informed by the AMC that the visibility had decreased to 5 kilometres in rain and the mean wind speed had increased to 22 kt. Two minutes before clearing CAL605 to land, the air traffic controller advised the crew that the wind was 070/25 kt and to expect windshear turning short final. During the approach the pilots completed the landing checklist for a flaps 30 landing with the autobrakes controller selected to position '2' and the spoilers armed. The reference airspeed (Vref) at the landing weight was 141 kt; to that speed the commander added half the reported surface wind to give a target airspeed for the final approach of 153 kt. Rain and significant turbulence were encountered on the IGS approach and both pilots activated their windscreen wipers. At 1,500 feet altitude the commander noted that the wind speed computed by the Flight Management Computer (FMC) was about 50 kt. At 1,100 feet he disconnected the autopilots and commenced manual control of the flightpath. A few seconds later at 1,000 feet he disconnected the autothrottle system because he was dissatisfied with its speed holding performance. From that time onwards he controlled the thrust levers with his right hand and the control wheel with his left hand. Shortly afterwards the commander had difficulty in reading the reference airspeed on his electronic Primary Flying Display (PFD) because of an obscure anomaly, but this was rectified by the co-pilot who re-entered the reference airspeed of 141 kt into the FMC. Shortly before the aircraft started the visual right turn onto short final, the commander saw an amber 'WINDSHEAR' warning on his PFD. A few seconds later, just after the start of the finals turn, the ground proximity warning system (GPWS) gave an aural warning of "GLIDESLOPE" which would normally indicate that the aircraft was significantly below the IGS glidepath. One second later the aural warning changed to "WINDSHEAR" and the word was repeated twice. At the same time both pilots saw the word 'WINDSHEAR' displayed in red letters on their PFDs. Abeam the Checkerboard the commander was aware of uncommanded yawing and pitch oscillations. He continued the finals turn without speaking whilst the co-pilot called deviations from the target airspeed in terms of plus and minus figures related to 153 kt. At the conclusion of the turn both pilots were aware that the aircraft had descended below the optimum flight path indicated by the optical Precision Approach Path Indicator (PAPI) system. The air traffic controller watched the final approach and landing of the aircraft. It appeared to be on or close to the normal glidepath as it passed abeam the tower and then touched down gently on the runway just beyond the fixed distance marks (which were 300 metres beyond the threshold) but within the normal touchdown zone. The controller was unable to see the aircraft in detail after touchdown because of water spray thrown up by it but he watched its progress on the Surface Movement Radar and noted that it was fast as it passed the penultimate exit at A11. At that time he also observed a marked increase in the spray of water from the aircraft and it began to decelerate more effectively. The commander stated that the touchdown was gentle and in a near wings level attitude. Neither pilot checked that the speed brake lever, which was 'ARMED' during the approach, had moved to the 'UP' position on touchdown. A few seconds after touchdown, when the nose wheel had been lowered onto the runway, the co-pilot took hold of the control column with both hands in order to apply roll control to oppose the crosswind from the left. The aircraft then began an undesired roll to the left. Immediately the commander instructed the co-pilot to reduce the amount of applied into-wind roll control. At the same time he physically assisted the co-pilot to correct the aircraft's roll attitude. Shortly after successful corrective action the aircraft again rolled to the left and the commander intervened once more by reducing the amount of left roll control wheel rotation. During the period of unwanted rolling, which lasted about seven seconds, the aircraft remained on the runway with at least the left body and wing landing gears in contact with the surface. After satisfactory aerodynamic control was regained, the co-pilot noticed a message on the Engine Indicating and Crew Alerting System (EICAS) display showing that the autobrake system had disarmed. He informed the commander that they had lost autobrakes and then reminded him that reverse thrust was not selected. At almost the same moment the commander selected reverse thrust on all engines and applied firm wheel braking using his foot pedals. As the aircraft passed abeam the high speed exit taxiway (A11), the commander saw the end of the runway approaching. At that point both he and the co-pilot perceived that the distance remaining in which to stop the aircraft might be insufficient. At about the same time the co-pilot also began to press hard on his foot pedals. As the aircraft approached the end of the paved surface the commander turned the aircraft to the left using both rudder pedal and nose wheel steering tiller inputs. The aircraft ran off the end of the runway to the left of the centreline. The nose and right wing dropped over the sea wall and the aircraft entered the sea creating a very large plume of water which was observed from the control tower, some 3.5 km to the northwest. The controller immediately activated the crash alarm and the Airport Fire Contingent, which had been on standby because of the strong winds, responded very rapidly in their fire vehicles and fire boats. Other vessels in the vicinity also provided prompt assistance. After the aircraft had settled in the water, the commander operated the engine fuel cut-off switches and the co-pilot operated all the fire handles. The commander attempted to speak to the cabin crew using the interphone system but it was not working. The senior cabin crew member arrived on the flight deck as the commander was leaving his seat to proceed aft. The instruction to initiate evacuation through the main deck doors was then issued by the commander and supervised by the senior cabin crew member from the main deck. Ten passengers were injured, one seriously.
Probable cause:
The accident was the consequence of the combination of the following factors:
- The commander deviated from the normal landing roll procedure in that he inadvertently advanced the thrust levers when he should have selected reverse thrust.
- The commander diminished the co-pilot's ability to monitor rollout progress and proper autobrake operation by instructing him to perform a non-standard duty and by keeping him ill-informed about his own intentions.
- The copilot lacked the necessary skill and experience to control the aircraft during the landing rollout in strong, gusty crosswind conditions.
- The absence of a clearly defined crosswind landing technique in China Airline's Operations Manual deprived the pilots of adequate guidance on operations in difficult weather conditions.
Final Report:

Crash of a Beriev BE-12NKh off Yuzhno-Kurilsk

Date & Time: Oct 31, 1993
Type of aircraft:
Registration:
82 yellow
Survivors:
Yes
Schedule:
Yuzhno-Sakhalinsk - Yuzhno-Kurilsk
MSN:
9 6 017 02
YOM:
1969
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Yuzhno-Kurilsk, the crew realized that the sea was relatively rough with waves of 1,5 meter. Despite the situation, the crew decided to land in the bay. After touchdown, the right float was torn off and the aircraft rolled to the right and came to rest 120 metres offshore, partially submerged. All 20 occupants were rescued while a rescuer died from hypothermia. The aircraft partially sank as the fuselage was cut in several places after suffering chocks with water.

Crash of an Embraer C-95A Bandeirante off Angra dos Reis: 3 killed

Date & Time: Oct 26, 1993
Type of aircraft:
Operator:
Registration:
2290
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Porto Alegre - Rio de Janeiro
MSN:
110-172
YOM:
1978
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
While cruising along the coast, the twin engine airplane went out of control and crashed in the sea off Angra dos Reis. All three crew members were killed.

Crash of a Piper PA-31-310 Navajo off Hilo

Date & Time: Oct 13, 1993 at 1414 LT
Type of aircraft:
Registration:
N7079J
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Christmas Island - Hilo
MSN:
31-663
YOM:
1970
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3500
Captain / Total hours on type:
100.00
Aircraft flight hours:
4356
Circumstances:
During an oceanic ferry flight, the right engine developed magneto problems which resulted in only residual power being available. The pic increased the power on the remaining left engine, but it soon overheated. The pic elected to ditch the airplane into the pacific ocean. Both crewmembers were successfully rescued.
Probable cause:
Failure of the right engine's magnetos for undetermined reasons and the resulting overtemperature of the remaining left engine.
Final Report:

Crash of a Tupolev TU-134A off Sukhumi: 27 killed

Date & Time: Sep 21, 1993 at 1625 LT
Type of aircraft:
Operator:
Registration:
4L-65893
Survivors:
No
Schedule:
Sochi - Sukhumi
MSN:
53 40120
YOM:
1975
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
27
Circumstances:
The aircraft was completing a charter flight from Sochi to Sukhumi, carrying foreign and Russian journalists. On final approach to Babushara Airport, at a height of 300 metres, the aircraft was hit by a surface-to-air Strela missile and crashed in the bay of Sukhumi about 4 km offshore. All 27 occupants were killed.
Probable cause:
Shot down by a Strela missile fired by Abkhazi separatists based on a patrol boat.