Flying Tiger Line Flight 66
Template:Short description Script error: No such module "Unsubst".
Script error: No such module "Infobox".Script error: No such module "Check for unknown parameters". Flying Tiger Line Flight 66 was a scheduled international cargo flight from Singapore Changi Airport to Hong Kong's Kai Tak Airport via a stopover at Kuala Lumpur International Airport, Malaysia. On February 19, 1989, the FedEx-owned Boeing 747-249F-SCD crashed while on its final approach. The aircraft impacted a hillside Script error: No such module "convert". above sea level and Script error: No such module "convert". from Kuala Lumpur, resulting in all four occupants being killed.[1]
Aircraft and crew
The aircraft, registered as N807FT, made its first flight on 1 November 1979, before being delivered new to Flying Tiger Line on 11 December 1979. Its manufacturer serial number was 21828 and its construction number was 408. At the time of the accident, it had flown over 9,000 flight cycles and 34,000 airframe hours.[2][3]
The crew consisted of Captain Francis "Frank" Halpin (59), First Officer John "Jack" Robinson (54), and Flight Engineer Ronald Penton (70). Leonard Sulewski (53), an aircraft mechanic, was also on board.[4][5][6]
Accident
The aircraft was assigned a non-directional beacon (NDB) approach to Runway 33 at Sultan Abdul Aziz Shah Airport, Kuala Lumpur, after having flown 30 minutes from Singapore Changi Airport.[7] In descent, the flight was cleared to "Kayell" with a Morse code of "KL" of which four separate points on the ground were commonly called by Malaysian ATC, albeit with different frequencies. Two separate radio beacons were identically coded "KL", as well as the VOR abbreviation (Kuala Lumpur shortened to "KL") and the airport was also sometimes referred to as "KL" by local ATC (instead of the full "Kuala Lumpur"). The crew was unsure to which point they were cleared, and the cockpit voice recorder (CVR) revealed that the crew argued about which radios should be set to which frequencies and which approach was actually going to be conducted. (Even in the last few moments of the flight, the captain referenced the ILS approach for runway 33, which was named as inoperable on the flight release and the ATIS; additionally the crew was told by ATC that the ILS approach was not available.)
Air traffic control (ATC) radioed to the flight, "Tiger 66, descend two four zero zero (about Script error: No such module "convert".), cleared for NDB approach runway 33." Captain Halpin, who interpreted it as "descend to four zero zero" replied with, "Okay, four zero zero" (meaning Script error: No such module "convert".) above sea level, which was Script error: No such module "convert". too low). The CVR[8] also revealed several communication errors made by the flight crew prior to this miscommunication and a general casual nature of the captain, who was the pilot-not-flying on this particular leg of the trip.
During the final approach, numerous clear warnings were given by the on-board ground proximity warning system, which were all ignored entirely by the crew, and the aircraft hit a hillside Script error: No such module "convert". above sea level, killing all four crew on board—two pilots, a flight engineer, and an aircraft mechanic. The subsequent fire burned for two days.[8]
Causes
Script error: No such module "Unsubst". The first officer (FO) had complained that he did not have an approach plate in front of him and had not seen the approach. From a pilot's perspective, this alone would be considered the cause of the crash because the approach plate (chart) provides the pilot with the courses and minimum altitudes necessary to execute the approach without hitting terrain. The chart would have indicated the minimum descent altitude of Script error: No such module "convert"., preventing the accident.
Additionally, the FO, who was the pilot flying at the time, expressed concern about conducting the NDB approach and indicated a preference for the ILS for runway 15. The FO was not assertive, though, and no further action was taken. The captain dismissed his concern, saying he was familiar with the airport and the approaches.
A contributing factor to this accident was the non-ICAO phraseology used by Kuala Lumpur ATC and the captain of the aircraft. This breakdown of communication contributed to the crew misinterpreting the instructions given. This particular controlled-flight-into-terrain accident, however, ultimately resulted from a crew failure to adhere to the instrument approach procedure, poor crew resource management, and poor situational awareness.[7]
Procedure changes
The incident further stressed the need for increased awareness and training of crew resource-management techniques and standard operating procedures. This accident is used as an example of "what not to do" by flight-training organizations. The FAA video production[8] using the original CVR recording and transcript is still used to study the events and how to improve current techniques.Script error: No such module "Unsubst".
See also
Script error: No such module "Portal".
References
<templatestyles src="Reflist/styles.css" />
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ a b Accident description at the Aviation Safety Network. Retrieved on 2008-06-28.
- ↑ a b c Script error: No such module "citation/CS1".
Script error: No such module "Check for unknown parameters".
- Aviation Week & Space Technology 27.02.89 (24)
- Flight Int. 17-12.01.1990 (p. 44)
- ICAO Adrep Summary
Script error: No such module "Navbox".Script error: No such module "check for unknown parameters".
Template:Aviation accidents and incidents in Malaysia
- Pages with script errors
- 1989 in Malaysia
- Airliner accidents and incidents involving controlled flight into terrain
- Airliner accidents and incidents caused by pilot error
- Aviation accidents and incidents caused by air traffic controller error
- Aviation accidents and incidents in 1989
- Aviation accidents and incidents in Malaysia
- Flying Tiger Line accidents and incidents
- Accidents and incidents involving the Boeing 747
- February 1989 in Asia