Crash of a Boeing 747-2B3F in Chennai

Date & Time: Mar 6, 1999 at 0029 LT
Type of aircraft:
Operator:
Registration:
F-GPAN
Flight Type:
Survivors:
Yes
Schedule:
Paris – Karachi – Bangalore – Chennai
MSN:
21515
YOM:
1978
Flight number:
AF6745
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
72968
Aircraft flight cycles:
17608
Circumstances:
The aircraft was completing a cargo flight from Paris to Chennai with intermediate stops in Karachi and Bangalore, carrying five crew members and a load of various goods including three cars, 20 tons of cigarettes, chemicals and clothing for a total weight of 66 tons. The aircraft was cleared for a runway 07 ILS approach, but the approach was abandoned due to indications that the undercarriage was not down and locked. The flight crew concluded that all gear were down and locked despite a red GEAR light on the forward instrument panel. The crew had failed to recognize that the green GEAR DOWN light for the nose gear was not illuminated and assumed that the red GEAR light on the forward instrument panel was a false indication. The gear was recycled, but an alternate extension was not attempted. The pilot positioned the airplane for another approach. The aircraft touched down with the nose gear retracted. The nose struck the runway. The plane skidded and came to rest at 7000 feet down the runway (which is 13050 feet long). As the pilot informed the ATC of the mishap, he noticed smoke in the cockpit. Even as the smoke was being extinguished, flames erupted in the front portion of the aircraft. One of the crewmembers came down through a rope ladder from the cockpit, the other four were brought down through the rear of the aircraft using the fire engine step ladders. The fire services were not able to extinguish the fire and the plane burned out completely.

Crash of a Boeing 737-228 in Biarritz

Date & Time: Mar 4, 1999 at 2010 LT
Type of aircraft:
Operator:
Registration:
F-GBYA
Survivors:
Yes
Schedule:
Paris - Biarritz
MSN:
23000
YOM:
1982
Flight number:
AF7638
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
91
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Air France Flight 7638, a Boeing 737-228, operated on a domestic flight from Paris-Charles de Gaulle Airport to Biarritz. The co-pilot on the flight was Pilot Flying (PF). While en route, about an hour before arrival, the flight crew listened out the ATIS frequency. The latest report mentioned a visibility of 10 km, a headwind of 15 to 30 kt and rain. When descending towards Biarritz the crew obtained an avoidance heading to bypass a thunderstorm cell. The flight was subsequently cleared for an ILS DME Cat I for runway 27. In the four minutes before landing, the visibility was 1500 metres in a squall, wind 6 kt with gusts to 3 kt, its direction changing from 250° to 290°, with variations up to 330°. The Vref is 129 kt and the Vapp 149 kt. The controller cleared the flight for landing and indicated a wind of 250° at 16 kt, gusts to 30 kt and heavy rain. The first officer disconnected the autopilot and autothrottle at an altitude of approximately 1200 ft, while established on the ILS. As the aircraft descended through 1100 feet, the captain was able to see the runway ahead. On short final, the controller reported a wind of 280° at 15 to 30 kt. The aircraft gradually deviated to the left of the centre line. The captain said: "a little to the left". The aircraft then gradually returned to align with the runway centreline. The PF banked the aircraft to the left as it slightly overshot the runway centreline. The aircraft passed the threshold approximately 4 m to the right of the centreline, parallel to it, with its wings horizontal. The PF started the flare with a slight bank to the left. The thrust reduction occurred a few seconds later. The left main gear touched the runway first at an indicated airspeed of 148 kt, while the aircraft was 12 m to the left of the runway centreline. The aircraft moved 7 m to the left, rolling on the only left main gear for about two seconds. The PF used the control column and the rudder pedals to steer the airplane to the right. The right main gear touched the runway while the left wheels were about 3 m from the edge of the runway. The PF corrected the trajectory using the rudders, without using the full amplitude. The aircraft exited the runway on the left at a speed of 133 kt. The nose gear struck the concrete support of a light and broke. The right gear was damaged and the aircraft rolled approximately 400 m off the runway and came to rest near the runway, 1150 m from the threshold.
Probable cause:
The pilot flying experienced wind rotation below decision altitude without being aware of the crosswind corrections to be made during the flare. He did not have the necessary availability to analyse the reasons for the destabilisation in the short final. Without communication within the crew, the PF acted alone, with few external markers and found himself overloaded during touchdown. The slope of the runway also limited the forward visibility of the pilots.

Crash of a Lockheed L-188AF Electra in Shannon

Date & Time: Mar 1, 1999 at 0846 LT
Type of aircraft:
Operator:
Registration:
N285F
Flight Type:
Survivors:
Yes
Schedule:
Cologne - Dublin - Shannon
MSN:
1107
YOM:
1959
Flight number:
EXS6526
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5000
Captain / Total hours on type:
3200.00
Copilot / Total flying hours:
3000
Copilot / Total hours on type:
760
Aircraft flight hours:
65000
Circumstances:
The aircraft (Flight 6526) departed Cologne at 0300 hours and routed directly to Dublin, where, after more than one hours delay due to the late arrival of a freight truck, the aircraft departed for Shannon Airport at 0816 hours. The crew consisted of the First Officer who was the handling pilot on both of these sectors, the Captain who was the non-handling pilot and the Flight Engineer. The take off gross weight was estimated at 83,701 lbs, well below the limiting 116,000 lbs take off weight (MTOW), and the centre of gravity was within limits. The landing weight was estimated at 80,345 lbs, again below the maximum landing weight of 98,102 lbs. The total freight on board was 14,000 lbs, less than half the 33,000 lbs maximum amount permissible. The aircraft reached it's designated altitude of FL120. The crew were handed over to Shannon Approach and given descent clearance. Shannon Approach instructed the crew to keep the speed up (due to an another aircraft behind them) and the aircraft was vectored on an approach to RWY 24. Due to the weather forecast for Shannon the crew decided to conduct the landing with 78% flaps set, rather than the standard 100% flap normally set for landing. During the approach the Captain called 1000 ft above the touchdown zone (TDZ), then 500 ft and every 100 ft thereafter to the Decision Altitude (DA). At an altitude of 700 ft the Ground Proximity Warning (GPWS) horn sounded. The Flight Engineer proceeded to inhibit the GPWS system. Slowing the aircraft to Vma (Maximum Manoeuvering Airspeed) the crew did not carry out the "before landing" checks. Whilst over the RWY threshold the gear warning horn sounded and five seconds later the crew heard a scraping sound and felt severe aircraft vibrations. Realising that the gear was not down the Captain called for a go-around. The First Officer continued to fly the aircraft and was cleared to 3000 ft by ATC. However, during the climb out the aircraft flew into cloud (Instrument Meteorological Conditions) at about 500/600 feet, and simultaneously the propeller assembly and part of No. 3 engine fell to the ground. Electrical power was lost and the only serviceable flight instruments available to the crew was the standby artificial horizon and wet compass. The First Officer relinquished control of the aircraft to the Captain who had great difficulty in maintaining directional control and it took the combined efforts of both pilots to control the excessive yaw through the rudder pedals. In addition, there was insufficient power available to climb to 3000 ft. In fact, less than 2000 ft was attained, as the aircraft commenced a slow difficult turn in a North Easterly direction and towards the high ground west of Limerick city. It was only by further manipulation of the throttles and feathering No. 4 engine that sufficient directional control was recovered, enough to respond to the instructions of the ATC Radar operator. The aircraft was now flying with only No.1 engine fully operative and No. 2 engine producing only half power and much vibration. The Radar operator vectored the aircraft to approach RWY 24 which became visible to the crew. They selected "gear down" and while only 2 of the 3 green landing lights illuminated, the Captain elected to proceed with the landing, with the flaps again set at 78%. This landing was successful, with all the landing gear deploying correctly. The aircraft was evacuated while the airport crash crews stood by.
Probable cause:
The primary responsibility for the safe conduct of a flight rests with the cockpit crew and, in this regard, they have the Aircraft Flight Manual (AFM), company Standard Operating Procedures (SOP's) and other technical manuals at their disposal in the cockpit. In particular, the company lays down the SOP's to be followed by each and every cockpit crew member in the interests of standardisation and flight safety. The implementation of these measures and procedures is carried out by the cockpit crew and they are aided in this process by artificial mechanical/electrical warning systems and audio alerts. In the L188 in question the two audio alert systems consist of a Ground Proximity Warning System (GPWS) and the landing gear warning horn. The GPWS system sounded at about 700' AGL and this should have been sufficient to warn the crew that the landing gear handle was not down and consequently that the undercarriage was not in the landing configuration. The Flight Engineer, however, reached up and inhibited the GPWS. He said he did this because he understood the aircraft to have 78% flap set for landing and that this was why the GPWS warning sounded. He obviously confused this warning with a warning which he would have got below 200 feet radio height when the flaps are set at less than 100% for landing. The fact that this particular aircraft had no FLAP OVERRIDE switch, as the other two similar aircraft in the fleet had, would probably have added to this confusion. Whether the engineer was instructed to inhibit the GPWS by other crew members is not clear from the CVR. In the debrief following the accident the other crew members agreed that the engineer would have been correct in inhibiting the GPWS as they were landing with 78% flaps configuration. They, therefore, also misinterpreted the GPWS warning. Having failed to carry out the landing checks and with the undercarriage not down, the normal undercarriage warning horn should have sounded when the throttles were retarded for landing. However, it is possible to silence this warning in the 78% flap configuration, which would not have been possible if the flaps were set in the normal (100%) configuration for landing. It appears that as the throttles were being retarded the Flight Engineer pressed the warning horn button to prevent the alarm from sounding. Whether he was so instructed is not clear as parts of the CVR tape were difficult to interpret due to its poor quality. During the final stage of landing the throttles were advanced again thus negating the warning cancellation. As the aircraft rounded out for landing the warning horn was again free to sound, and it did, as the throttles were retarded. However, at this stage, there was too little time to lower the undercarriage and five seconds later the propellers stuck the runway surface.
The following findings were identified:
- The aircraft had a valid standard Airworthiness Certificate issued by the United States Department of Transportation, Federal Aviation Administration and had been maintained in accordance with an approved schedule.
- No evidence was found of any technical problems on the aircraft, or its systems, that could have had any bearing on the accident. In addition, the aircraft records show that the aircraft was dispatched on the accident flight with no deferred maintenance items.
- The crew were properly licensed, in accordance with US Federal Aviation Administration Regulations, to undertake this flight.
- The Captain stated that he had slight flu symptoms over the two days prior to the flight but that did not disbar him from undertaking the flight.
- The flight crew consisted of the Captain, First Officer and Flight Engineer. The First Officer was the handling pilot on this flight.
- No emergency call was made to ATC by the Captain or First Officer. The Shannon Radar controller provided invaluable voice and directional assistance to the crew as they struggled to maintain control of their seriously damaged aircraft and this was subsequently acknowledged by the crew.
- The subsequent actions of the crew in landing the aircraft safely from the second approach were commendable.
- The ILS for RWY 24 was fully serviceable.
- Crew fatigue is not considered a factor in this accident as they had sufficient time off duty in the days immediately prior to the flight and their overall flying duties are of average industry standards.
- Debris from the disintegrating No. 3 engine fell to earth on the western side of RWY 24, within the boundaries of Shannon Airport. Fortunately, there was no damage to property or people.
- The selection of 78% flap setting for the landing was in accord with the Operators SOP's for the prevailing landing conditions. However in selecting 78% flap setting the crew were of the mistaken opinion that the GPWS warning horn should be silenced even though the aircraft was not in the landing configuration.
- The Flight Engineer silenced the landing gear warning horn during the approach phase while the engine power levers were being retarded. It is only when these levers were slightly advanced, just before the round-out stage, that the landing warning horn system was again primed and subsequently sounded.
- The normal landing checks were not carried out by the flight crew. Not one crew member realised that the undercarriage gear was not down and locked.
- The crew stated that this was an inexplicable oversight on their part.
Final Report:

Crash of a Beechcraft King Air 100 in Muskoka

Date & Time: Feb 27, 1999 at 0920 LT
Type of aircraft:
Registration:
C-GBTS
Flight Type:
Survivors:
Yes
Schedule:
Kitchener - Muskoka
MSN:
BE-73
YOM:
1979
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Muskoka Airport, while on a cargo flight from Kitchener-Waterloo Airport, the twin engine aircraft descended too low in a slight nose down attitude when it collided with trees and crashed on the ground. Both occupants were seriously injured and the aircraft was damaged beyond repair. At the time of the accident, ceiling was at 1,000 feet with 10 km visibility and wind from 140 at 2 knots.

Crash of a Dornier DO328-110 in Genoa: 4 killed

Date & Time: Feb 25, 1999 at 1230 LT
Type of aircraft:
Operator:
Registration:
D-CPRR
Survivors:
Yes
Schedule:
Cagliari - Genoa
MSN:
3054
YOM:
1995
Flight number:
AZ1553
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
27
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
Upon landing at Genoa-Cristoforo Colombo Airport runway 29, the aircraft encountered crosswinds gusting up to 15-18 knots. It landed on one gear only, bounced and landed firmly too far down the runway. The crew started the braking procedure but the aircraft was unable to stop within the remaining distance, overran and came to rest in the sea. A stewardess and three passengers were killed while 18 other occupants were injured, some seriously. Nine people escaped uninjured. The aircraft was destroyed.

Crash of a Tupolev TU-154M in Wenzhou: 61 killed

Date & Time: Feb 24, 1999 at 1634 LT
Type of aircraft:
Operator:
Registration:
B-2622
Survivors:
No
Schedule:
Chengdu - Wenzhou
MSN:
90A846
YOM:
1990
Flight number:
SZ4509
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
61
Aircraft flight hours:
14135
Aircraft flight cycles:
7748
Circumstances:
Following an uneventful flight from Chengdu, the crew was cleared to descend to Wenzhou Airport. While passing 9,000 metres on descent, the crew encountered technical difficulties with the control column that was too far forward. At 1629LT, the crew was cleared to descend from 1,200 to 700 metres when the aircraft entered a nose-down attitude. Flaps were selected down (first stage) when the AOA alarm sounded in the cockpit. The aircraft entered an uncontrolled descent and crashed in an open field. It disintegrated on impact and all 61 occupants were killed. Several farmers were injured by debris.
Probable cause:
A self-locking nut, other than castle nut with cotter pin as specified, had been installed at the bolt for connection between pull rod and bellcranck in the elevator control system. The nut screwed off, resulting in bolt loss, which led to the loss of pitch control.

Crash of a Piper PA-31-310 Navajo B in La Serena

Date & Time: Feb 23, 1999
Type of aircraft:
Registration:
CC-CRV
Survivors:
Yes
MSN:
31-733
YOM:
1971
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to La Serena-La Florida Airport, both engines failed simultaneously. The pilot attempted an emergency landing when the aircraft stalled and crashed short of runway. All four occupants were injured and the aircraft was destroyed. The aircraft was completing a charter flight for the El Indio Mining Company.
Probable cause:
Double engine failure on approach due to fuel exhaustion.

Crash of a Hawker-Siddeley HS-748-206 Andover CC2 in Foxtrot

Date & Time: Feb 14, 1999
Operator:
Registration:
9L-LBG
Flight Type:
Survivors:
Yes
Schedule:
Lokichogio - Foxtrot
MSN:
1566
YOM:
1965
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing an on-demand cargo flight from Lokichogio to the Foxtrot Airstrip, carrying supplies for SPLA troops. After landing, the aircraft suffered an asymmetrical thrust due to the failure of the left thrust reverser. The aircraft veered to the right and came to rest. Both pilots escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Loss of control on landing following the failure of the left thrust reverser.

Crash of a Beechcraft 1900C-1 in Saint Mary's

Date & Time: Feb 11, 1999 at 2345 LT
Type of aircraft:
Operator:
Registration:
N31240
Flight Type:
Survivors:
Yes
Schedule:
Anchorage – Saint Mary’s
MSN:
UC-28
YOM:
1988
Flight number:
AER91
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12326
Captain / Total hours on type:
1587.00
Aircraft flight hours:
19588
Circumstances:
The airline transport pilot was cleared for the localizer approach. The airplane impacted the ground 3.2 nautical miles from the runway threshold. The minimum descent altitude (MDA) for the approach was 560 feet msl, which is 263 feet above touchdown. Night, instrument meteorological conditions prevailed at the time of the accident. The surrounding terrain was flat, snow-covered, and featureless. The reported weather was 200 feet overcast, 1 1/2 miles visibility in snow, and winds of 12 knots, gusting to 32 knots. The pilot reported he was established on the final approach course, descending to the MDA, and then woke up in the snow. He said he did not remember any problems with the airplane. No pre accident mechanical anomalies were discovered with the airplane during the investigation. The airport has high intensity runway lights, sequenced flashing lead-in lights, and visual approach slope indicator lights. All airport lights and navigation aids were functioning. The airplane was not equipped with an autopilot. Captains have the option of requesting a copilot, but, the captain's pay is reduced by a portion equal to one-half the copilot's pay. The pilot had returned from the previous nights trip at 0725. He had three rest periods, four hours, two hours, and five hours 15 minutes, since his previous nights flight. Each rest period was interrupted by contact with the company. The company indicated that it is the pilot's responsibility to tell the company if duty times are being exceeded. 14 CFR 135.267 states, in part: '(d) Each assignment ... must provide for at least 10 consecutive hours of rest during the 24 hours that precedes the planned completion of the assignment.'
Probable cause:
The pilot's descent below the minimum descent altitude on the instrument approach. Factors were pilot fatigue resulting from the pilot's rest period being interrupted by scheduling discussions and the night weather conditions of low ceilings and whiteout.
Final Report:

Crash of an Antonov AN-26 in Luzamba: 2 killed

Date & Time: Feb 4, 1999
Type of aircraft:
Operator:
Registration:
EL-ANZ
Survivors:
Yes
Schedule:
Luanda - Luzamba
MSN:
139 06
YOM:
1984
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
30
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Following a visual approach, the aircraft landed too far down the runway which is 1,500 metres long. Unable to stop within the remaining distance, the aircraft overran and came to rest in a ravine, bursting into flames. 25 people escaped uninjured while nine others were injured and two passengers were killed.
Probable cause:
Wrong approach configuration on part of the crew who was apparently intoxicated at the time of the accident.