United Arab Airlines Flight 869 (1962)
![]() | This article may be expanded with text translated from the corresponding article in German. (March 2017) Click [show] for important translation instructions.
|
![]() | This article needs additional citations for verification. (July 2020) |
![]() A de Havilland Comet of United Arab Airlines, similar to the crashed aircraft | |
Accident | |
---|---|
Date | July 19, 1962 |
Summary | Controlled flight into terrain |
Site | Khao Yai mountain, Thailand |
Aircraft | |
Aircraft type | de Havilland DH-106 Comet 4C |
Operator | United Arab Airlines |
Registration | SU-AMW |
Flight origin | Hong Kong (HKG) |
Stopover | Bangkok (BKK) |
Destination | Cairo (CAI) |
Passengers | 18 |
Crew | 8 |
Fatalities | 26 |
Survivors | 0 |
United Arab Airlines Flight 869 was an international scheduled passenger flight operated by a de Havilland DH-106 Comet 4C from Hong Kong via Bangkok to Cairo. On July 19, 1962 at 13:30 UTC, the plane departed from Hong Kong for the first leg of the flight with 18 passengers and 8 crew aboard. The flight was uneventful until commencing approach to Bangkok, when the plane crashed in the Khao Yai mountain range 96 km NE of Bangkok at 15:44 UTC. There were no survivors.
The investigation found as a probable cause a sequence of mistakes in the navigation by the pilot-in-command, which "resulted in grave errors of time and distance in his computations".
Aircraft[]
The aircraft was a de Havilland DH-106 Comet 4C with construction number 6464, delivered to United Arab Airlines in 1962. At the time of the accident, it had been in service with the airline for only 3 months.[1]
It was equipped with dual VOR receivers, Doppler and automatic direction finders.[2]
Accident[]
Flight 869 took off from Hong Kong Kai Tak Airport for the first leg of its journey to Cairo.
At 15:08 UTC, the aircraft entered the Bangkok Flight Information Region boundary, and established contact with Bangkok Air Traffic Control at 15:14. Upon initial contact, the flight advised ATC that they had passed the Ubol NDB at 15:13 UTC, and requested to fly direct to the Bangkok VOR. This request was granted, and at 15:17, the crew reported their estimated time of arrival (ETA) at the VOR as 15:47. A further report gave the ETA of their crossing at the 100 mile perimeter from the VOR at 15:30 UTC.
The aircraft reported that they crossed the 100 mile perimeter at 15:29, switching to Bangkok Control. Upon initial contact with Bangkok control at 15:30, the crew requested descent, reporting their position to be 90 miles out from the VOR. Bangkok Control then instructed the crew to descend to 4000 ft while tracking on the 073 radial of the Bangkok VOR. This instruction was acknowledged by the crew. During the descent, the crew was advised of the weather conditions at Bangkok and to contact Bangkok Approach control at 15:39 UTC.
Bangkok Approach Control took responsibility for the aircraft at 15:40 UTC. Upon first contact, the crew gave a new ETA at the VOR as 15:44, and reported that they were descending from 13,000 ft. Approach control cleared the aircraft for an approach to runway 21R after crossing the VOR.
Contact was lost at 15:50. It was estimated the aircraft crashed at 15:44-15:45 UTC.
Investigation[]
It was determined that the aircraft had a ground speed of 455 mph. Using this ground speed, the aircraft was actually 137 miles from the Bangkok VOR instead of the 90 miles during the position report at 15:39.[2]
References[]
- ^ https://rzjets.net/. Retrieved September 22, 2021. Missing or empty
|title=
(help) - ^ a b ICAO Circular 71-AN/63 (PDF). pp. 101–103.
Sources[]
- Aviation accidents and incidents in 1962
- Aviation accidents and incidents in Thailand
- Airliner accidents and incidents involving controlled flight into terrain
- Airliner accidents and incidents caused by pilot error
- Accidents and incidents involving the de Havilland Comet
- EgyptAir accidents and incidents
- 1962 in Egypt
- July 1962 events in Asia
- Aviation accident stubs
- Thailand transport stubs