Sterling Airways Flight 296

On 14 March 1972, Sterling Airways Flight 296 crashed into a mountain ridge on approach to Dubai near Kalba, United Arab Emirates. Flight 296 was a charter flight from Colombo to Copenhagen with stops in Bombay, Dubai, and Ankara. All 112 passengers and crew on board died in the crash which was attributed to pilot error. The flight was operated by a Sud Aviation Caravelle, registration OY-STL.[1] To date, it is the deadliest air disaster to involve a Caravelle and the deadliest air disaster in the history of the United Arab Emirates.[2]

Sterling Airways Flight 296
A Sterling Airways Caravelle 10B3 similar to the accident aircraft
Occurrence
Date14 March 1972
SummaryControlled flight into terrain, pilot error
SiteNear Kalba, United Arab Emirates
Aircraft
Aircraft typeSud Aviation SE-210 Caravelle 10B3
OperatorSterling Airways
RegistrationOY-STL
Flight originColombo International Airport, Colombo, Ceylon
1st stopoverChhatrapati Shivaji International Airport, Bombay, India
2nd stopoverDubai Airport, Dubai, United Arab Emirates
Last stopoverEsenboğa International Airport, Ankara, Turkey
DestinationCopenhagen Airport, Copenhagen, Denmark
Occupants112
Passengers106
Crew6
Fatalities112
Survivors0

Aircraft

The aircraft involved was Sud Aviation SE-210 Caravelle 10B3 (serial number 267) that was built in May 1970 and had its maiden flight on 10 May the same year. The aircraft was delivered to Sterling Airways on May 19 and subsequently received its airworthiness certificate and registration OY-STL on 22 May. OY-STL was in a long-haul flight configuration being equipped with central fuel tanks. The aircraft was powered by two Pratt & Whitney JT8D-9 engines. The passenger capacity of the cabin was 109 seats, though the maximum number of people on board was 116. The aircraft had 6,674 hours and 50 minutes flight time and 2,373 landings at the time of the accident. The last Y-l check (every 12–15 months) was performed by Finnair (under a contract) on 5 June 1971. The aircraft's last overhaul was performed on 8 February 1972, when the aircraft had 6,270 hours 39 minutes of flying time. The last A and B technical inspections were performed one day before the accident flight on 13 March 1972, before departure from Copenhagen. The last B-check was performed in Bombay the same day.[3]:9[4]

Flight

Sterling Airways Flight 296 was chartered by the tour company Tjaereborg Rejser to take 106 Europeans home from vacations in Ceylon (present day Sri Lanka). The flight from Colombo to Copenhagen was scheduled to make refuelling stops in Bombay, Dubai, and Ankara. A change of crew was also scheduled during the stop in Ankara. Flight 296 departed from Colombo on time at 17:20 local time for Bombay.

The 106 passengers were from Denmark, Finland, Norway, Sweden, and West Germany. The Danish cockpit crew consisted of Captain Ole Jorgensen, 35 and First Officer Jorgen Pedersen, 30.

At 19:45, it landed in Bombay. The passengers were not allowed to de-plane during the stop in Bombay. After refuelling Flight 296 departed Bombay for the next stop in Dubai at 21:20.[3]:2

According to the flight plan, Flight 296 from Bombay to Dubai was to follow the R19 air corridor at flight level 310 (31,000 feet (9,400 m; 9.4 km). The length of the route was 1,045 nautical miles (1,935 km; 1,203 mi) the majority of it passing over the Arabian Sea, while the route had 5 waypoints for reports on position: SALMON, SEAHORSE, BLUE WHALE, DOLPHIN and SPEARFISH, located 292, 531, 706 and 854 miles (185, 541, 983, 1308 and 1582 km) respectively, from Bombay.[3]:2

At 21:40, the crew of Flight 296 informed the Bombay approach controller that they were passing the SALMON waypoint and that they were climbing from flight level 250 (7.62 km), to 310. At 21:49 the controller reported the flight reaching FL 310. At 21:14 the crew reported passing the SEAHORSE waypoint. At 21:52, the Bombay controller instructed the crew to change frequencies. Beginning at 21:47 the controllers experienced communication problems with Flight 296, but managed to re-establish communication at 22:04. Flight 296 passed the BLUE WHALE waypoint at 22:49 which 3 to 6 minutes earlier than expected.[3]:2

Flight 296 reported passing the DOLPHIN point at 22:14 via a relay — a minute earlier than planned at Blue Whale, and already 10 minutes earlier than planned when departing from Dubai. At 21:25 pm, the crew contacted the tower of the Dubai Airport and received information about the weather in Dubai. At 21:42 at a frequency of 124.9 MHz, flight 296 contacted the control center in Dubai and reported on the passage of the SPEARFISH waypoint at 21:42 at flight level 310, and the estimated landing time in Dubai is 22:10. At the same time, Flight 296 was instructed to go under the control of the Dubai-approach. The crew received information that the bearing on them from the D0 radio beacon (Dubai VOR) is 084, and the descent from FL 310 would begin at 21:55. However at 21:49, 95 miles (153 km) from the airport, the crew requested to descend early. The approach controller cleared Flight 296 to descend to FL 40 (4000 feet or 1219 meters). Then the control center asked the crew if they wanted a heading of 084, to which the crew accepted. The controller then gave instructions regarding the heading. Shortly before 22:00 local time, Flight 296 began the approach into Dubai.[3]:2–3

Accident

The weather in Dubai was cloudy with scattered thunderstorms.[3]:10–11 The crews of other aircraft reported an overcast sky with the formation of large cumulus clouds over the coast. The crew of BOAC Flight 833 (also flying to Dubai, though departing from Calcutta) indicated that the coast was poorly visible on meteorological radar due to thunderstorms, although the crew of SABENA Flight 352 (which also departed Bombay but was bound for Athens), on the contrary, reported a clear sky.[3]:13

At 21:50, the crew of Flight 296 reported descending from 310 to 40 and asked which runway to take. The controller responded that the wind was at 045/6 knots and that the landing could be carried out on either runway 30 or 12. The crew selected runway 30. At 21:56, The crew reported leaving flight level 135 and the controller instructed the flight to maintain 2,000 feet (610 m) relative to the level of Dubai Airport (1016 hPa) with a report on occupying a height of 2000 and observing the airfield. The crew acknowledged the transmission.[3]:13

For better communication, the crew switched to the backup radio, but since it was quiet, the radio communications on the cockpit voice recorder were in poor condition or unusable. At 22:01, Flight 296 contacted the controller, but this was not recorded on the CVR. According to the controller's testimony, when the crew asked how the airport’s driving station worked, the controller replied, "it functions normally." The dispatcher also warned: "the ADF radio station antenna was reduced in length due to the runway extension, and 'DO' is not giving much power. Use the VOR at 115.7 [MHz] or the ILS localizer at 110.1 [MHz]."[3]:3

Just after this transmission, the crew transmitted another message. At 22:02:04 the controller made the following response: "296, Dubai,you are fading away say again please." And at 18:02:12 said, "296, Dubai, QNH Dubai 1016.5." Transmissions from flight 296 were not recorded by the CVR. At 22:03:15, the controller transmitted: 296, Dubai, next report field in sight", but the controller believed Flight 296 did not hear his message. At 22:04, the crew radioed that the VOR was not properly working, to which the controller transmitted at 18:03:42: "296, Dubai, if the VOR indication are not reliable, select ILS on and tune [at a] frequency of 110.1. The QDM is 300°, this will align you with the runway."[3]:3–4

Local residents stated that it was raining at the time.[3]:3–4 Several residents of Kalba were digging a ditch around a hut to divert rainwater, when at 22:00 local time an aircraft flew over the city at a low altitude. One of the residents stated that the aircraft flew so low that its navigation lights were clearly visible. An explosion was seen shortly after. The residents got into a Land Rover vehicle and tried to get to the crash site, but the vehicle was stuck in the mud. The residents of the nearby Al-Heilruen settlement heard the explosion but thought that it was thunder.[3]:4

Travelling at a speed of 95 knots (109 mph; 176 km/h), at a heading of 285° the aircraft descended at a vertical speed of about 800 feet (240 m) per minute and had already descended to 1,400 feet (430 m) when the crew saw the mountains right on the course. Engine power was increased, and the aircraft began to climb with a vertical speed of 600 feet (180 m)–700 feet (210 m) feet per minute (3–3.6 m / s). 10 later seconds at 22:04 pm local time, the aircraft, at an altitude of 1,600 feet (490 m), 50 miles from Dubai airport and 10 miles north of the continuation of the longitudinal axis of runway 30 at a speed of 190 knots (220 mph; 350 km/h), the aircraft's left wing hit a mountain ridge. In the impact the left wing broke off. The plane flew another 869 feet (265 m) meters before impacting below the top of the next ridge. The wreckage slid down the slope and ended up in five different valleys.[3]:19–21

At 22:10, dispatchers in Dubai informed Bahrain about the loss of communication with Flight 296. All attempts to contact the plane were unsuccessful, and an emergency was declared at 22:40 and a search began. The next morning, the wreckage of the aircraft was discovered in the mountains of Sharjah, 50 miles (80 km) from Dubai Airport and 12 miles (19 km) west of Kalba at 25°04′06″N 56°13′48″E There were no survivors among the 106 passengers and 6 crew members.[2][3]:4

Cause

The investigation found that the pilots descended below the minimum prescribed altitude. This was due to incorrect information on the outdated flight plan and/or due to a misreading of the weather radar which led the pilots to believe they were closer to Dubai than they actually were.[3]:63

Nationalities of the passengers and crew
Nationality Passengers Crew Total
Denmark 68 6 74
Sweden 20 - 20
Norway 12 - 12
Finland 4 - 4
West Germany 2 - 2
Total 106 6 112

Sources:[5][6]

gollark: <@709333181983096834> ```haskelldata T = TautocompleteIsAlive :: TautocompleteIsAlive = Tmain = print $ autoCompleteIsAlive```
gollark: Mine is more accurate because it has syntax highlighting.
gollark: ```haskelldata T = TautocompleteIsAlive :: TautocompleteIsAlive = T```
gollark: skynet1, if you're curious, is deprecated and I don't run it.
gollark: I was doing this on the server skynet2 runs on, so it might be skynet's fault, who knows.

References
  1. "Photo of Caravelle OY-STL".
  2. "Aviation Safety Network".
  3. "FLYVEHAVARI RAPPORT STERLING AIRWAYS A/S CARAVELLE SE-210-10B3, OY-STL FUJAYRAH 50 NM ØST FOR DUBAI LUFTHAYN 14, MARTS 1972" [AIRCRAFT ACCIDENT REPORT STERLING AIRWAYS CARAVELLE SE-210-10B3, OY-STL FUJAYRAH 50 NM EAST FOR DUBAI AIRPORT 14, MARCH 1972] (PDF) (in Danish). DANMARK LUFTFARTSDIREKTORATET [DENMARK AIRPORT DIRECTORATE]. Retrieved 2019-04-28.
  4. "Sterling Airways OY-STL – 14. March 1972". SudAviation.com. Retrieved 2014-05-19.
  5. "112 persons feared killed in crash of Danish plane". The Telegraph. 1972-03-15. Retrieved 2019-04-28.
  6. "Plane crash death count may reach 112". Retrieved 2019-04-28.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.