Country
Operator Image

Crash of a Short 330-200 in Paris: 1 killed

Date & Time: May 25, 2000 at 0252 LT
Type of aircraft:
Operator:
Registration:
G-SSWN
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Paris - Luton
MSN:
3064
YOM:
1981
Flight number:
SSW200
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2240
Captain / Total hours on type:
1005.00
Copilot / Total flying hours:
4370
Copilot / Total hours on type:
14
Aircraft flight hours:
15215
Aircraft flight cycles:
19504
Circumstances:
The Short was departing Paris-Roissy-CDG Airport on a cargo service to Luton with two pilots on board. The crew were cleared to depart cargo stand N51 and proceed to runway 27 at 02:38. Around the same time Air Liberté Flight 8807 (an MD-83, F-GHED) also taxied to runway 27 for a flight to Madrid. At 02:44 the Charles de Gaulle ground controller asked Streamline 200 if they wished to enter runway 27 at an intermediate taxiway; the crew asked for and were granted to enter Taxiway 16. At 02:50:49 the tower controller cleared the MD-83 for takeoff: "Liberté 8807, autorisé au décollage 27, 230°, 10 à 15 kts.". The controller then immediately told the Shorts to line up and wait: "Stream Line two hundred line up runway 27 and wait, number two". As the MD-83 was travelling down the runway, the Shorts started to taxi onto the runway. At a speed of about 155 knots the left wing of MD-83 slashed through the cockpit of the Shorts plane; the MD-83 abandoned takeoff.
Probable cause:
The following findings were identified:
- Firstly, by the LOC controller’s erroneous perception of the position of the aircraft, this being reinforced by the context and the working methods, which led him to clear the Shorts to line up,
- Secondly, by the inadequacy of systematic verification procedures in ATC which made it impossible for the error to be corrected,
- Finally, by the Shorts’ crew not dispelling any doubts they had as to the position of the 'number one' aircraft before entering the runway.
Contributory factors include:
- Light pollution in the area of runway 27, which made a direct view difficult for the LOC controller,
- Difficulty for the LOC controller in accessing radar information: the ASTRE image was difficult to read and the AVISO image not displayed at his control position,
- The use of two languages for radio communications, which meant that the Shorts crew were not conscious that the MD 83 was going to take off,
- The angle between access taxiway 16 and the runway which made it impossible for the Shorts crew to perform a visual check before entering the runway,
- The lack of coordination between the SOL and LOC controllers when managing the Shorts, exacerbated by the presence of a third party whose role was not defined,
- A feedback system which was recent and still underdeveloped.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Dounreay

Date & Time: May 12, 1987 at 1546 LT
Operator:
Registration:
G-BASU
Flight Phase:
Survivors:
Yes
Schedule:
East Midlands – Dounreay – Lossiemouth
MSN:
31-7305023
YOM:
1973
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5950
Captain / Total hours on type:
150.00
Circumstances:
The twin engine airplane was completing a charter flight from East Midlands to Dounreay in the morning and from Dounreay to Lossiemouth in the afternoon, carrying seven passengers and a crew of two. During the takeoff roll, the airplane deviated twice to the right but the crew was able to correct. At a speed just below minimum rotate speed (101 mph), the aircraft yawed to the right, the right engine power fluctuated and a 'bang' was heard from the right side. The commander decided to abort the takeoff procedure but the remaining distance was insufficient. He veered off runway then the aircraft struck a fence, lost its undercarriage and came to rest. There was no fire. All nine occupants escaped uninjured.
Probable cause:
Examination and testing of the Fuel Boost system showed the following caused for the Fuel Boost Inoperative light illuminating:
- Failure of the fuel boost pump,
- Failure of the fuel boost pressure warning switch,
- Failure of the fuel boost inoperative warning light electrical circuit,
- Lack of fuel at the input to the fuel boost pump.
Final Report: