Crash of a Partenavia P.68B Victor in Schönhagen: 2 killed

Date & Time: Sep 20, 1996
Type of aircraft:
Registration:
D-GISA
Flight Type:
Survivors:
No
MSN:
105
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On final approach to Schönhagen Airport, the twin engine aircraft collided with trees and crashed in a wooded area short of runway. Both occupants were killed.

Crash of a Short SC.7 Skyvan 3 Variant 200 in Pittsburgh

Date & Time: Sep 16, 1996 at 2200 LT
Type of aircraft:
Operator:
Registration:
N10DA
Flight Type:
Survivors:
Yes
Schedule:
Clarksburg - Pittsburgh
MSN:
1873
YOM:
1969
Flight number:
SBX1215
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11000
Captain / Total hours on type:
1100.00
Aircraft flight hours:
18553
Circumstances:
The pilot had flown this route in make and model airplane for nearly 4 years. He calculated 900 pounds of fuel were required for the flight, and saw 956 pounds on the fuel totalizer. The pilot was told by the ground controller of weather delays to his destination that ranged up to 2.5 hours. En route he was issued holding instructions with an EFC of 50 minutes later. After released from holding, 52 minutes after takeoff, the pilot was told that he was being vectored for a 35 mile final approach. The pilot then told the controller that he was fuel critical and the controller vectored him ahead of other airplanes. Ten minutes later, 84 minutes after takeoff, the controller asked his fuel status, and the pilot responded 'pretty low, seems like I'm losing oil pressure.' The pilot then advised the controller, 85 minutes after takeoff, that he shut down the right engine. He then declared an emergency and advised that he was not going to make the airport. Examination of the wreckage revealed the fuel tanks were intact, the fuel caps were secured, and the amount of fuel recovered from both tanks was 1.5 gallons, which was less than the specified unusable quantity. Company records showed that similar flights took about 48 minutes, and the airplane's average fuel flow was 580 pounds per hour.
Probable cause:
The pilot's improper in-flight decision to continue to his destination when known en route delays were encountered which resulted in fuel exhaustion.
Final Report:

Crash of an Embraer EMB-110P1 Bandeirante near Joinville: 2 killed

Date & Time: Sep 13, 1996 at 2226 LT
Operator:
Registration:
PT-WAV
Flight Type:
Survivors:
No
Site:
Schedule:
Porto Alegre - Joinville
MSN:
110-048
YOM:
1975
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7794
Captain / Total hours on type:
594.00
Copilot / Total flying hours:
1592
Copilot / Total hours on type:
872
Circumstances:
The crew departed Porto Alegre on a night cargo flight to Joinville. The JNV NDB beacon and the next PP NDB were selected by the crew to start the descent to Joinville Airport, with a minimum safe altitude fixed at 770 feet. After the aircraft passed over JNV beacon, the ADF system was unable to find the PP NDB as it was inoperative so the aircraft initiated a turn heading 051° towards the PP beacon located near São Paulo-Congonhas Airport. The crew did not notice the change of heading and continued the descent when few minutes later, the aircraft struck a hill and crashed. Both pilots were killed.
Probable cause:
The following findings were reported:
- Possible crew fatigue that diminished their performances,
- Possible psychological and organizational diminution,
- Possible inadequate supervision of the operator in flight planning, and non-compliance with procedures in force,
- Following a lack of crew resources management, the crew failed to follow the standard descent procedures,
- Poor approach planning on part of the crew,
- It is possible that the crew did not observe sufficient rest time,
- It is also possible that there was an intentional disobedience by the crew of ATC rules and operational standards, in relation to the use of the GPS equipment during the descent, even though this was not approved for such procedure.
Final Report:

Ground fire of a Douglas DC-10-10CF in Newburgh

Date & Time: Sep 5, 1996 at 0554 LT
Type of aircraft:
Operator:
Registration:
N68055
Flight Type:
Survivors:
Yes
Schedule:
Memphis - Boston
MSN:
47809
YOM:
1975
Flight number:
FDX1406
Crew on board:
3
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12344
Captain / Total hours on type:
2504.00
Copilot / Total flying hours:
6535
Copilot / Total hours on type:
1101
Aircraft flight hours:
38271
Aircraft flight cycles:
17818
Circumstances:
The airplane was at FL 330 when the flightcrew determined that there was smoke in the cabin cargo compartment. An emergency was declared and the flight diverted to Newburgh/Stewart International Airport and landed. The airplane was destroyed by fire after landing. The fire had burned for about 4 hours after after smoke was first detected. Investigation revealed that the deepest and most severe heat and fire damage occurred in and around container 06R, which contained a DNA synthesizer containing flammable liquids. More of 06R's structure was consumed than of any other container, and it was the only container that exhibited severe floor damage. Further, 06R was the only container to exhibit heat damage on its bottom surface, and the area below container 06R showed the most extensive evidence of scorching of the composite flooring material. However, there was insufficient reliable evidence to reach a conclusion as to where the fire originated. The presence of flammable chemicals in the DNA synthesizer was wholly unintended and unknown to the preparer of the package and shipper. The captain did not adequately manage his crew resources when he failed to call for checklists or to monitor and facilitate the accomplishment of required checklist items. The Department of Transportation hazardous materials regulations do not adequately address the need for hazardous materials information on file at a carrier to be quickly retrievable in a format useful to emergency responders.
Probable cause:
An in-flight cargo fire of undetermined origin.
Final Report:

Crash of a Tupolev TU-154M in Longyearbyen: 141 killed

Date & Time: Aug 29, 1996 at 1022 LT
Type of aircraft:
Operator:
Registration:
RA-85621
Survivors:
No
Site:
Schedule:
Moscow - Longyearbyen
MSN:
86A742
YOM:
1986
Flight number:
VKO2801
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
130
Pax fatalities:
Other fatalities:
Total fatalities:
141
Captain / Total flying hours:
6232
Captain / Total hours on type:
1940.00
Copilot / Total flying hours:
19538
Copilot / Total hours on type:
10177
Circumstances:
Vnukovo Airlines flight VKO2801 departed Moscow-Vnukovo Airport at 04:44 UTC bound for Longyearbyen Airport on the Norwegian archipelago of Svalbard. It was a chartered flight with workers and their families to coal mining towns on Svalbard. The flight was uneventful until the start of the descent. Before radio contact with Longyear Information, the crew went through the detailed landing procedure for runway 10. At 09:56, the crew were cleared to start the descent. A little later, the crew received additional information consisting of runway in use 28, wind 230 degrees at 16 knots, visibility more than 10 km, rain showers, clouds: few at 1500 feet, scattered at 2000 feet and broken at 4000 feet, temperature +5°C, dewpoint -0°C and QNH 1005 hPa. (Later changed to 1006 hPa). The crew tried to request runway 10 for landing twice, but the request was not understood as such by Longyear Information due to language difficulties. When the flight was overhead the ADV beacon, at 10:15 hrs, the crew reported their position to Longyear Information and entered the base turn with a bank angle of 22 degrees. At 10:16 hrs, the aircraft came out of this turn on magnetic heading 160 degrees. During the right turn to the base turn, a malfunction occurred in the electric trimming mechanism, which was corrected by the crew. At 10:17, the crew started the turn to bring the aircraft out on the magnetic inbound course 300 degrees, as prescribed by the approach chart. The distance from the airport at this moment was 14 NM (25.9 km), as prescribed by the approach chart, but the lateral deviation from the outbound magnetic course 155 degrees from ADV was 2 NM (3.7 km) to the left. At 10:18, after the radio altimeter aural warning had been activated twice, the co-pilot took the controls and, after 6 seconds, turned the autopilot pitch channel off by 'overriding' it. From then on until the impact, the flight continued in autopilot mode in the roll channel, and in manual mode in the pitch channel. The aircraft passed through the localizer centerline and when the turn had been completed, the aircraft rolled out on a magnetic heading of 290 degrees. At this time, there was a discussion within the crew as to whether or not the final turn had been made at the correct time. The discussion led to the roll out of the turn to final approach and a corrective turn to the right to magnetic heading 306 degrees. At this point, the aircraft was 14.7 NM (27.4 km) from the airport, 2.8 km to the right of the approach centerline, maintaining an altitude of 5000 feet (1520 m ) and the crew increased the flap setting to 28 degrees. The airspeed was reduced to approx. 330 km/hr (180 kts). Instead of intercepting the centerline, the crew continued the flight on the right side, more or less paralleling the localizer course with minor heading changes. At 10:20 the flight made a corrective turn, resulting in a track close to 300 degrees. At this point, the lateral deviation from the approach centerline was 3.7 km to the right. During this corrective turn, the aircraft started descending. At 10:21, the crew made yet another corrective turn to the right. At 10:22:05, the aircraft started turning towards the left. The distance to the airport was 8 NM (14.8 km). On this part of the final approach, the aircraft apparently entered an area of strong turbulence created by the proximity to the mountains. The GPWS then activated 9 seconds before impact. The crew reacted to this by applying power and initiating a pitch-up. At 10:22:23, 7.7 NM (14.2 km) from the airport at an altitude of 2975 feet (907 m), the aircraft collided with the top of the mountain Operafjellet 3.7 km to the right of the approach centerline. All 141 occupants were killed, most of them employees of a local carbon mine and their family members.
Probable cause:
The following findings were reported:
1) There is no Russian procedure for offset localizer approaches modifying the required rule to set the landing course on the HSI.
2) The course selected on both HSIs was 283° even though the approach course is 300°. This setting does not affect the indication of the CDI. However, the CDI was pointing to 283° on the dial, which is 17° to the left of the approach course, giving a visual impression of wind drift to the left and therefore giving a possible reason for a heading correction to the right.
3) The navigator in a stressed and overloaded working situation most probably followed the rule setting the landing course 283° on the GPS in OBS mode instead of the approach course 300°.
4) The crew was not fully aware of the status of an AFIS officer in comparison with the authority of a Russian air traffic controller with the result that the crew accepted safety information from the AFIS officer as orders.
5) The crew had limited knowledge of the English language with the consequence that they had problems communicating their intentions to the AFIS officer.
6) The navigator was overloaded with tasks leaving little time for rechecking his work, thereby setting the scene for making mistakes.
7) The pilots did not monitor the work of the navigator sufficiently.
8) Leaving the communication with AFIS to the navigator during the approach was not according to the normative documents.
9) Due to the workload of the navigator, the decision of the co-pilot to transfer the responsibility of controlling the aircraft laterally to him, was inappropriate.
10) The crew resource management of the PIC was not satisfactory.
11) When the crew had made the decision to carry out the approach to runway 28, a new approach briefing was not accomplished.
12) The crew made the proper correction for the wind drift, but did not try to intercept the outbound track from ADV with the consequence that they overshot the approach centerline turning inbound.
13) Seemingly confusing indications on the HSIs in the base turn caused the crew to become uncertain of the aircraft position in relation to the LLZ 28 centerline. In this situation, the crew showed a lack of situational awareness.
14) The two pilots did not have the approach chart in front of them at all times during the approach making it difficult for them to maintain situational awareness.
15) The crew did not know of the possibility to check the position of the aircraft in relation to the localizer centerline by the VDF service available.
16) On final approach the crew probably put too much emphasis on the indications displayed on the GPS.
17) The crew started descent in a mountainous area without firm and positive control of the lateral navigation demonstrated by the disagreement within the crew as to whether to correct to the left or right.
18) In spite of the uncertainty within the crew as to whether they were approaching correctly or not, they continued instead of abandoning the approach and climbing to a safe altitude to solve the problem.
Final Report:

Crash of a Boeing 707-366C in Istanbul

Date & Time: Aug 21, 1996 at 1700 LT
Type of aircraft:
Operator:
Registration:
SU-AVX
Survivors:
Yes
Schedule:
Cairo - Istanbul
MSN:
20760
YOM:
1973
Flight number:
MS837
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
120
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Istanbul-Atatürk Airport, the crew encountered marginal weather conditions with rain falls. The visibility was estimated to be 8 km but on short final, the crew lost visual contact with the runway for few seconds while the aircraft encountered local strong showers. After touchdown on a wet runway 24, the aircraft was unable to stop within the remaining distance and overran. It lost its undercarriage, went through a fence, crossed a road and collided with various obstacles before coming to rest, broken in two. All 131 occupants were evacuated, among them 19 passengers were slightly injured.

Crash of an Ilyushin II-76TD in Belgrade: 12 killed

Date & Time: Aug 19, 1996 at 0316 LT
Type of aircraft:
Operator:
Registration:
RA-76513
Flight Type:
Survivors:
No
Schedule:
Yekaterinburg - Belgrade - Valetta
MSN:
00834 14451
YOM:
1988
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
12
Circumstances:
The aircraft was completing a cargo flight from Yekaterinburg to Africa via Belgrade and Luqa, Malta, carrying two passengers, 10 crew members and a load of aircraft tires and squibs. Following a night takeoff from Belgrade-Surčin Airport, the crew informed ATC about technical problems and reported the loss of all electrical power. Following a holding pattern for about 2,5 hours, the crew attempted to land but the visibility was low due to poor weather conditions. On short final, without any headlights, the aircraft struck the ground and crashed 800 metres short of runway, bursting into flames. All 12 occupants were killed.
Probable cause:
It was determined that prior to takeoff from Belgrade-Surčin Airport, while preparing the flight, the crew forgot to switch on the VU-6A AC/DC converter after start-up of the engines, causing the 27 volts electrical system to be constantly fed from the batteries. When batteries ran flat, all the avionic and boosters were left without power.

Crash of a Learjet 25B in Northolt

Date & Time: Aug 13, 1996 at 0957 LT
Type of aircraft:
Operator:
Registration:
EC-CKR
Survivors:
Yes
Schedule:
Palma de Mallorca - Northolt
MSN:
25-184
YOM:
1974
Flight number:
MAQ123
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5200
Captain / Total hours on type:
1900.00
Copilot / Total flying hours:
5340
Copilot / Total hours on type:
1700
Aircraft flight hours:
4396
Circumstances:
Learjet 25B EC-CKR arrived near Northolt following a flight from Palma de Mallorca. Due to the presence of priority traffic which was due to depart Northolt at that time, the flight was extended down wind to a distance of 10 nm before the crew received vectors and descent instructions for the final approach to runway 25. At 3.5nm short of the runway the pilot was asked to confirm that his landing gear was down and locked as is normal procedure at Northolt. After some rephrasing of this question, the landing gear was confirmed down, however during this exchange the aircraft was seen to deviate above the glidepath. At 2.5 nm, landing clearance was confirmed and the aircraft was advised of the surface wind and the fact that there was a 4 kt tailwind. The aircraft was also advised that it was above the glide path. At the decision altitude which was at approximately half a mile from the runway the aircraft was still above the glidepath although seen to be correcting to it. On arrival at the runway the aircraft was observed to land some distance beyond the normal touchdown point. Towards the end of the landing roll it veered to the right and then swerved to the left and overran the end of the runway. It collided with three lighting stanchions and continued in a south-westerly direction towards the airfield boundary which is marked by a high chain-link fence. After bursting through the boundary fence the aircraft ran onto the A40 trunk road and was almost immediately in collision with a Ford Transit van on the east bound carriageway, and seriously injuring its driver. The aircraft came to rest in the left hand lane of the road with the van embedded in the right side of the fuselage immediately forward of the right wing.
Probable cause:
The following causal factors were identified:
(1) The commander landed the aircraft at a speed of 158 (+/- 10 kt) and at a point on the runway such that there was approximately 3,125 feet (952 metres) of landing run remaining;
(2) The commander did not deploy the spoilers after touchdown;
(3) The first officer did not observe that the spoilers had not been deployed after touchdown;
(4) At a speed of 158 (+/- 10 kt) with spoilers retracted and given the aircraft weight and atmospheric conditions prevailing, there was insufficient landing distance remaining from the point of touchdown within which to bring the aircraft to a standstill;
(5) The commander allowed himself to become overloaded during the approach and landing. The safeguards derived from a two crew operation were diminished by the first officer’s lack of involvement with the final approach.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 300 in Markham Bay: 2 killed

Date & Time: Aug 12, 1996 at 1347 LT
Operator:
Registration:
C-GNDN
Flight Type:
Survivors:
No
Schedule:
Iqaluit - Markham Bay - Lake Harbour
MSN:
427
YOM:
1974
Flight number:
7F064
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3813
Captain / Total hours on type:
2028.00
Copilot / Total flying hours:
2724
Copilot / Total hours on type:
1000
Circumstances:
First Air 064, a DHC-6 Twin Otter (Serial No. 427), took off from Iqaluit, Northwest Territories (NWT), at 1258 Coordinated Universal Time (UTC) on a charter flight to Markham Bay, Lake Harbour, and back to Iqaluit. The aircraft was carrying six barrels of Jet B fuel to be delivered to Markham Bay, an off-strip landing site. At 1300, just after he took off, the captain told the Iqaluit Flight Service Station (FSS) specialist that the estimated time of arrival (ETA) for Markham Bay would be 1335. At approximately 1345, the crew informed First Air dispatch that they were landing at Markham Bay. After touching down, the pilot attempted an overshoot. During the attempt, the aircraft struck the ground about 200 metres past the end of the landing area, got airborne again, cleared a ridge, then crashed onto a rocky beach. A helicopter located the airplane 629 metres from the beginning of the landing area, partially submerged in water. The two pilots, the only occupants, received fatal injuries in the crash.
Probable cause:
For unknown reasons, a decision was made to overshoot even though insufficient runway remained for acceleration, take-off, and climb. Likely contributing directly to the decision to overshoot was the difficulty in controlling the aircraft on touchdown.
Final Report:

Crash of a Dassault Falcon 10 in Offenburg: 4 killed

Date & Time: Aug 8, 1996 at 0940 LT
Type of aircraft:
Operator:
Registration:
D-CBUR
Survivors:
No
Schedule:
Munich - Offenburg
MSN:
98
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Aircraft flight hours:
5797
Circumstances:
On approach to Offenburg Airport runway 02, the crew encountered limited visibility due to low clouds. Under VFR mode in IMC conditions, the crew failed to realize his altitude was too low when the aircraft collided with trees and crashed in a hilly terrain located about 7,2 km southeast of runway 02 threshold, near Friesenheim. The aircraft was destroyed by impact forces and a post crash fire and all four occupants were killed.
Probable cause:
Controlled flight into terrain after the crew continued the approach under VFR mode in IMC conditions until the aircraft impacted terrain.