Region
Crash of a Beechcraft 99 Airliner near Liège: 2 killed
Date & Time:
Jun 30, 1999 at 0443 LT
Registration:
D-IBEX
Survivors:
No
Schedule:
Luton - Frankfurt
MSN:
U-45
YOM:
1968
Flight number:
EXT114
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total hours on type:
8200.00
Copilot / Total hours on type:
590
Aircraft flight hours:
34946
Circumstances:
En route from Luton to Frankfurt, while on a night cargo service (flight EXT114), at an altitude of 11,000 feet, the right engine failed and was shut down by the crew. Four minutes later, the left engine failed as well. The crew sent a Pan call and was cleared to divert to Liege-Bierset Airport. Vectored for an approach to runway 23L, the airplane passed FL040 when it entered an uncontrolled descent and crashed in a wooded area located in Seraing, in the south suburb of Liege, 8,3 km southeast of Liege Airport. The aircraft was destroyed by impact forces and both pilots were killed.
Probable cause:
Following the deterioration of the right engine’s turbine blade, one of them broke off, causing significant damage to the turbine and downstream components, which led to the engine shutting down. At that point, in violation of company regulations, the captain decided to continue the flight on one engine while maintaining altitude and a relatively high speed, which required maximum or near-maximum power from the left engine. About four minutes after the right engine shut down, the left engine also failed, following the failure of a compressor turbine blade; the exact cause could not be determined with certainty, but the stress imposed on it at high RPM and temperature certainly contributed to this failure. The crew did not transmit a Mayday call to Air Traffic Control, but did transmit a Pan call on the frequency. The crew did not set the distress code 7700 on their transponder. The controller interpreted this message as a medical issue, which did not strike him as urgent. When the aircraft was transferred to approach control, the problem reported was a medical issue. Immediately, the controller instructed the crew to proceed with a landing procedure to runway 23L at Liege Airport, which was much longer than bringing the aircraft directly in a cross-traffic procedure to runway 05R. When the crew switched frequencies to approach control, the approach controller continued the procedure for runway 23L. The problem reported to him was medical, and, in his mind, there was no reason to clear the crew for a short approach to runway 05R. It was only when the aircraft approached FL040 it was supposed to maintain and the crew told him it was impossible due to a lack of engine power that the approach controller realized the urgency of the situation and directed the aircraft toward the runway at a 90° procedure. At that moment, the aircraft was at such an altitude and distance from the runway that it was impossible for it to reach the runway. At no point did the crew appear to have taken any initiative to attempt to resolve their problem.
The following contributing factors were identified:
- The absence of the seal on the inner guide vane drum of the right engine led to abnormal wear of the guide vanes and subsequently the fracture of a turbine blade, resulting in the engine shutdown.
- At that point, the crew decided to continue the flight, thereby violating the Standard Operating Procedures. An immediate diversion would have subjected the left engine to less stress.
- Approximately four minutes after the right engine shut down, a blade in the left engine’s compressor turbine broke, causing that engine to shut down.
- The crew did not clearly inform ATC about their situation. Sending a Mayday call was fully justified.
- The air traffic controller interpreted the Pan Call as a medical emergency and therefore initiated a standard landing procedure at Liege Airport instead of a cross-traffic emergency procedure. Had the latter been initiated in time and executed correctly, it would have allowed the aircraft to reach the runway.
- The time of day when the events occurred and the lighting conditions contributed to impairing the performance of the crew and the controllers.
- The lack of initiative on part of the crew.
The following contributing factors were identified:
- The absence of the seal on the inner guide vane drum of the right engine led to abnormal wear of the guide vanes and subsequently the fracture of a turbine blade, resulting in the engine shutdown.
- At that point, the crew decided to continue the flight, thereby violating the Standard Operating Procedures. An immediate diversion would have subjected the left engine to less stress.
- Approximately four minutes after the right engine shut down, a blade in the left engine’s compressor turbine broke, causing that engine to shut down.
- The crew did not clearly inform ATC about their situation. Sending a Mayday call was fully justified.
- The air traffic controller interpreted the Pan Call as a medical emergency and therefore initiated a standard landing procedure at Liege Airport instead of a cross-traffic emergency procedure. Had the latter been initiated in time and executed correctly, it would have allowed the aircraft to reach the runway.
- The time of day when the events occurred and the lighting conditions contributed to impairing the performance of the crew and the controllers.
- The lack of initiative on part of the crew.
Final Report:
Crash of a Boeing 707-355C in Ostend
Date & Time:
Nov 14, 1998 at 0544 LT
Registration:
5N-VRG
Survivors:
Yes
Schedule:
Ostend - Lagos
MSN:
19664
YOM:
1968
Flight number:
VGO302
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
67790
Aircraft flight cycles:
15984
Circumstances:
The aircraft departed Ostend Airport at 0328LT on a cargo flight to Lagos, carrying five crew members and a load of 35 tons of electronics. About 20 minutes into the flight, while cruising at an altitude of 24,000 feet over the border between Brussels and Paris ARTCC, the crew informed ATC about severe turbulences. Few seconds later, he reported the loss of the engine n°3 that separated and elected to return to Ostend. After being cleared, the crew started a circuit and while descending to Ostend Airport, the hydraulic systems failed. The crew completed a holding pattern to burn fuel and was later cleared to land on runway 26. After touchdown, the aircraft was unable to stop within the remaining distance, overran, lost its undercarriage, slid for few dozen metres and eventually came to rest near the localizer antenna. All five crew members escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
Laboratory analyses revealed the presence of a fatigue crack on the inner mid spar fitting of the engine n°3. The crack has been present for a reasonable time. The Airworthiness Directive 93-11-02 asks the replacement of the fittings by improved model at least for July 97. The fittings of engine n°3 were from the old design. Due to the non application of AD 93-11-02, the aircraft was in a non-airworthy condition.
Final Report:
Crash of a Pilatus PC-6/B1-H2 Turbo Porter in Spa
Date & Time:
Jul 30, 1995 at 1736 LT
Registration:
PH-MEN
Survivors:
No
Schedule:
Spa - Spa
MSN:
707
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The single engine airplane departed Spa-La Sauvenière Aerodrome with eight skydivers and one pilot on board. After all passengers bailed out, the pilot returned to base. On final approach to runway 05, the airplane collided with a private Cessna 172 registered OO-SIW. With three passengers and one pilot on board, the Cessna was also completing an approach to runway 05. Following the collision, both airplanes went out of control and crashed near the airfield. The Cessna 172 was damaged beyond repair and the PC-6 was destroyed by a post crash fire. All four people on board the Cessna were injured while the pilot of the PC-6 was killed.
Probable cause:
The Cessna was on final approach to runway 05 when it was struck on the right side by the PC-6, whose pilot was performing a non standard approach.
Final Report: