Scandinavian Airlines System Flight 933

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Scandinavian Airlines System Flight 933
300px
LN-MOO at Stockholm Arlanda Airport in 1967
Accident summary
Date January 13, 1969 (1969-01-13)
Summary Controlled flight into terrain caused by pilot error
Site Santa Monica Bay, Los Angeles, California, United States
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 36
Crew 9
Injuries (non-fatal) 17
Fatalities 15
Survivors 30
Aircraft type McDonnell-Douglas DC-8-62
Aircraft name Sverre Viking
Operator Scandinavian Airlines System
Registration LN-MOO
Flight origin Copenhagen Airport
Stopover Seattle–Tacoma International Airport
Destination Los Angeles International Airport

Scandinavian Airlines System Flight 933 was a scheduled international flight from Denmark to the United States, on January 13, 1969 it was being operated by a Douglas DC-8-62 when it crashed into Santa Monica Bay at 19:21, approximately 6 nautical miles (11 km) west of Los Angeles International Airport (LAX) in California, United States. The DC-8 was registered in Norway as LN-MOO and named Sverre Viking by the airline. The crash into the sea was caused by pilot error during approach to runway 07R. The pilots were so occupied with the nose gear light not turning green that they lost their situation awareness and failed to keep track of their altitude. The Scandinavian Airlines System (SAS) aircraft had a crew of nine and thirty-six passengers; thirty people survived while fifteen died. The flight originated at Copenhagen Airport, Denmark, and had a stop-over at Seattle–Tacoma International Airport where there was a change of crew.

The crash site was within international waters, but the National Transportation Safety Board carried out an investigation, which was published on July 1, 1970. It stated that the probable cause was improper crew resource management and stated that the aircraft was fully capable of carrying out the approach and landing. The aircraft was conducting an instrument approach, but was following a back course approach which it was not authorized to do.

Flight

The accident aircraft was a McDonnell Douglas DC-8-62 with serial number 45822 and line number 270. It was originally registered in the United States by McDonnell Douglas as N1501U for testing before delivery to SAS.[1] It was then registered as LN-MOD, but as SAS already had a Douglas DC-7 with that registration, it was re-registered as LN-MOO.[2] The aircraft was registered on 23 June 1967 and named Sverre Viking by SAS. Five days later it was re-registered with Norwegian Air Lines, the Norwegian holding company of the SAS conglomerate, as owner.[3] The DC-8-62 was an implementation which McDonnell Douglas had tailor-made for SAS to allow it to operate to Los Angeles with a full payload in all wind conditions, although the model was later sold to other airlines as well. SAS took delivery of the first of ten DC-8-62 aircraft in 1967.[4] Sverre Viking had flown 6,948 hours as of January 7 and had met all maintenance requirements. The last overhaul was carried out on April 3, 1968.[5]

File:Airport, Airport Overview JP6194421.jpg
Contemporary view of Los Angeles International Airport

Flight 933 was a regular, international scheduled flight from SAS' main hub at Copenhagen Airport in Denmark to Los Angeles International Airport in Los Angeles, California, in the United States. It had a scheduled stop-over at Seattle–Tacoma International Airport in the US state of Washington for change of crew and refueling. There were 45 people on board the aircraft at the time of the accident,[6] consisting of 36 passengers and 9 crew members.[7]

The crew outbound from Seattle had flown a flight from Copenhagen on January 11 and had about 48 hours of rest before the flight.[6] The crew consisted of a captain, a first officer, a flight engineer and six flight attendants.[7] Captain Kenneth Davies, a 50-year-old Briton, had been employed by SAS since 1948 and had a past in the RAF Coastal Command. He had flown 11,135 hours with SAS and 900 hours in the DC-8.[8] First Officer Hans Ingvar Hansson was aged 40 and had worked for SAS since 1957. He had flown 5,814 hours for the airline, including 973 hours in the DC-8. Flight Engineer Ake Ingvar Andersson, aged 32, had worked for SAS since 1966. He had flown 985 hours, all of the time on a DC-8. All three had valid certificates, training and medical checks.[9]

The cabin crew consisted of Renning Lenshoj, Arne Roosand, Peter Olssen, Marie Britt Larsson, Susanne Gothberg-Ingeborg and Ann-Charlotte Jenninge. A steward and two stewardesses were killed in the crash [1 Confirmed dead, the other two missing presumed dead]

The flight to Seattle had gone without incident. The landing took place with an instrument landing system (ILS) approach, with the autopilot coupler being used down to 100 to 60 meters (300–200 ft) before a manual completion. The aircraft had three maintenance issues at Seattle, consisting of a non-functioning fast–slow airspeed function, low oil on the number one engine and a non-functioning lavatory light.[6] The final crew arrived at Seattle–Tacoma an hour before the flight and given necessary documentation. Flight time was estimated at 2 hours and 16 minutes. All pre-flight checks were concluded without discrepancies. The aircraft was de-iced and the altimeters set and cross-checked.[10] The flight departed Seattle at 15:46 Pacific Standard Time (PST), one hour and eleven minutes after schedule. The first officer was designated as pilot flying. The altimeters were re-calibrated and the autopilot was used for the climb and cruise.[11]

Approach and landing

File:LAXfromabove.jpg
Modern aerial view of Los Angeles International Airport—runway 07R is located to the left and Santa Monica Bay in the background.

Slightly after 17:20 the airline dispatcher confirmed that the weather was suitable at LAX for the landing. The aircraft made contact with Los Angeles Air Route Traffic Control Center at 17:32 and were told to hold at Bakersfield. This holding was confirmed at 17:47.[11] At 18:39 the aircraft was cleared to descend via Fillmore and to keep an altitude of 1,500 meters (5,000 ft) via the newly designated Westlake Intersection, which was not yet on the charts. Further, they were to conduct a back course ILS at LAX, although they lacked authorization and plates to conduct this.[12] The weather at 19:00 consisted of scattered clouds at 300 meters (900 ft), ceiling-measured 500 meters (1,500 ft) overcast, visibility of 2.5 nautical miles (4.6 km; 2.9 mi) and light rain and fog.[13]

The night was dark and the pilots lacked any visual ground references. Descent was controlled through the use of the vertical speed wheel of the autopilot, combined with an altitude preselect in manual mode. Whenever the aircraft approached preselected altitudes the preselect warning light would come on. While retaining use of the autopilot, the pilots reduced their speed to Lua error in Module:Convert at line 272: attempt to index local 'cat' (a nil value). at the request of air traffic control at 19:07. At this point the pilots were working through the approach checklist.[12] The captain halted the checklist at the point regarding the radio altimeter, as the aircraft was above its operational limit and the captain wanted to control its operation during further descent. At 19:11 the aircraft received permission to bear 180 degrees and descend to and maintain 1,000 meters (3,000 ft) altitude. Both navigational receivers were tuned to the ILS frequency.[14]

At 19:17:55 the controller requested that SK933 reduce its speed to 153 knots (283 km/h; 176 mph), which was confirmed. At 19:19:05 the controller confirmed that the aircraft was cleared for approach for Runway 07R. At the time the first officer thought the aircraft was 14 nautical miles (26 km; 16 mi) from the VHF omnidirectional range (VOR) transmitter, while the captain thought they were 11 to 12 nautical miles (20 to 22 km; 13 to 14 mi) away. The first officer therefore disconnected the autopilot. The captain put the landing gear in down position and the first officer asked for the landing checklist to be completed. This was interrupted by radio traffic and cockpit activities. The aircraft then descended to a minimum altitude of 176 meters (576 ft) at a nominal speed of 5 meters per second (300 fpm).[14]

The DC-8 was following a Cessna 177, designated 67T, which was also conducting a back course approach,[14] flying at 110 knots (200 km/h; 130 mph). All communication between SK933, 67T and air traffic control were being carried out on the same frequency. Air traffic control asked SK933 at 19:19:35 to reduce their speed further to take in account the Cessna, and the pilots reduced their speed to 126 knots (233 km/h; 145 mph). This speed requires the full extension of the flaps, but this was not carried out. The nose gear was showing an unsafe indication; should the flaps be extended fully without the nose gear down, a horn would blow which could not be silenced without retracting the flaps. The captain recycled the gear, but the indicator light still showed an unsafe condition. Meanwhile, the first officer believed that the flaps were fully extended, and started reducing speed to 126 knots (233 km/h; 145 mph). After the flight engineer confirmed that the nose gear was down and locked, the captain fully extended the flaps.[15]

The flight engineer carried out a systems check, first from memory and then after consulting the flight manual. At this time, 19:20:42, the captain informed air traffic control that they were experiencing nose gear problems and that if it was not resolved by the time they reached minimum altitude they would abort the landing and divert to the designated alternate, McCarran International Airport in Las Vegas. This was the last transmission from Flight 933. The flight engineer conducted a manual check of the landing gear from the cockpit peephole, confirming it was down and locked. At this time the aircraft had an elevation of 300 meters (1,000 ft). The lowest recalled speed that the pilots remembered 130 knots (240 km/h; 150 mph) with full flap extension.[16]

At 1:58 minutes before impact the aircraft had an altitude of 930 meters (3,050 ft). It descended to 670 meters (2,200 ft) in the next 26 seconds, leveled for 16 seconds before descending to sea level in 1 minute and 16 seconds.[17] The pilots did not have control over their rate of descent and the next thing remembered by the first officer is seeing the altimeter approaching zero. He attempted to pull up through back pressure and adding power, but the aircraft hit the water before he was able to execute this. The impact took place at 19:21:30 PST (03:21:30 on January 14 Coordinated Universal Time) in Santa Monica Bay, about 6 nautical miles (11 km; 6.9 mi) west of LAX, in international waters where the sea is 110 meters (350 ft) deep. There was no recollection amongst the crew of any unusual sink rate, buffeting and yawing, nor were there any instrument warnings except a last-moment flashing of the heading difference light.[16]

The aircraft hit the water with the tail first.[18] The impact caused the fuselage to break into three main parts. The largest was the 26-meter (85 ft) forward section of the aircraft, from the nose to the trailing edge of the wings. It remained afloat after the accident for about twenty hours.[17] The midsection was 13 meters (42 ft) long, from the trailing edge of the wing to the rear pressure bulkhead. The aft section consisted of the tail cone, including all of the horizontal stabilizers and the vertical stabilizers. The engines and landing gears separated from the aircraft at the time of impact.[19]

Rescue and salvage

Three cabin crew and twelve passengers were killed in the impact. Of these, four were confirmed drowned, while eleven are missing and presumed dead. Eleven passengers and the remaining six crew members were injured, while thirteen passengers reported no injuries. Thirty people survived the crash.[6] The passengers were evenly distributed throughout the aircraft,[18] although there was a slightly higher proportion of survivors forward than aft. The surviving three cabin crew, an off duty captain and flight attendant, evacuated the passengers onto the wings and into liferafts.[20]

When the first two liferafts were filled, they were tied together and rowed from the port wing towards the nose of the aircraft. One of the rafts scraped against a piece of metal and deflated rapidly, with its passengers falling into the water. Other passengers launched a life raft from the starboard wing, but it was also punctured.[20] A search and rescue mission was quickly initiated by the United States Coast Guard.[21] It took between 45 and 60 minutes before the rescue team was able to pick up the survivors.[20] The coast guard stayed for hours searching for survivors.[21]

The forward part of the aircraft was towed towards Malibu Beach, where it sank. This was later raised and brought to Long Beach Terminal Island Naval Shipyard where it was investigated. All flight instruments were recovered.[17] The remaining other two sections, along with the engines and landing gear, were not recovered.[19]

Investigation

Because the crash took place in international waters, the investigation was carried out in accordance with the Convention on International Civil Aviation. The Government of Norway requested that the investigation be carried out by the United States' National Transportation Safety Board. The maintenance records were investigated by Norway's Aviation Accident Commission.[22] The final report from the board was issued on July 1, 1970, after 534 days of investigation.[23]

Flight 933 was the 20th hull loss to a DC-8; it was at the time the tenth-deadliest accident of the type and remains the twentieth-deadliest.[24] It was SAS' third fatal crash—they would not see another until 2001.[25] It was the third fatal crash at or in the immediate vicinity of LAX—and remains the second-most fatal.[26]

All navigational aid systems at LAX were controlled and found to be working at the time of the accident.[27] The flight recorder was recovered using a remotely operated underwater vehicle and found to be intact.[17] Flights and simulator tests were carried out by SAS, confirming that the recorded data could be simulated in an appropriate manner on schedule.[28] As the aircraft was found airworthy and able to conduct the flight, the bulk of the work of the investigation commission focused on operational procedures.[29]

Cause

The accident was caused through a series of events which, although not in themselves sufficient to cause the crash, combined to create a break-down in crew resource management. The flight experienced two delays, from de-icing at Seattle–Tacoma and holding a Bakersfield, which along with above-announced wind speeds increased the flight time by nearly three hours.[29] This caused the captain to have to consider if it was necessary to divert to Las Vegas. The first pilot error occurred when the first officer incorrectly set his altimeter when the descent started. The difference between his and the captain's altimeter was never noticed.[30]

Upon receiving clearance, a non-standard terminology was used by air traffic control. As they did not have authorization to use a localizer back course approach, the captain should have requested a different approach. They instead opted to conduct a VOR approach without informing air traffic control. Neither pilot had carried out instrument approach and landing at runway 07R, making them less familiar with this than their commonly used runway 25.[30] There was also an issue that the SAS aircraft was catching up to the Cessna, which was forcing it to operate at the lowest permissible safe speeds.[31]

The commission interpreted several of these actions as taking short-cuts to avoid further delays on an already severely delayed flight. They regarded the decision to descend at 5 meters per second (1,000 fpm) as reasonable given the conditions. However, as the first officer focused on the nose gear issue, the aircraft actually experienced a descent of 10.0 meters per second (1,960 fpm) for 26 seconds, zero descent for 16 second and then an average descent of 8.6 meters per second (1,720 fpm) until impact. The first officer was distracted by the captain's dealings with the landing gear issues, hindering him from primary task—flying the aircraft. The cycling of the landing gear and delay in extending the flaps made speed and altitude control more difficult. The captain also failed to inform the first officer when the flaps were fully extended.[32]

Both the landing gear issue and the concerns regarding speed made the captain focus on the possibility of a missed approach. This would be a major inconvenience, as the aircraft lacked sufficient fuel to remain in Los Angeles and would have to divert to Las Vegas.[32] It was the commission's impression that the captain failed to properly monitor the approach and crew resource management broke down. He failed to give proper instructions to the first officer, failed to carry out instructions from the first officer, which moved the first officer's attention away from his task of monitoring the flight instruments. The situation was amplified through the crew attempting to fly the aircraft at 126 knots (233 km/h; 145 mph) while it was not configured for that speed. Thus, there arose a situation where neither pilot was monitoring the altitude. There was also an shortcoming in the approach chart, which did not display a minimum altitude at Del Rey Intersection. This would have given the pilots an opportunity to correct the aircraft's altitude.[33]

The commission classified the accident as survivable because the impact forces varied along the fuselage. The tail-first impact was caused by the first officer's last-second attempt at raising the aircraft.[33] Most of the fatalities were caused by their being trapped in the sinking sections, which was caused by the collapsing of the structure after impact. The collapse was caused by the compromise of the tubular integrity which was dependent on the keel beam, which was torn off on impact.[34]

The nose gear light indicators are designed to be fail safe through having two separate light bulbs. This proved to be inadequate as it was not possible through the cover to see if one of the bulbs had been compromised. Thus a failure of one bulb would not be detected until both bulbs broke. The first bulb was thus presumed broken for a while, while the second bulb broke during Flight 933.[35] The NTSB therefore advised the Federal Aviation Administration to articulate means to avoid similar compromised fail-safe designs in the future.[36] Both pilots had minimum descent altitude light warnings which are presumed to have given a visual warning, but neither pilot directed their attention to these because of the work overload.[35]

The investigation commission came with the following conclusion:

<templatestyles src="Template:Blockquote/styles.css" />

"...the probable cause of this accident was the lack of crew coordination and the inadequate monitoring of the aircraft position in space during a critical phase of an instrument landing approach which resulted in an unplanned descent into the water. Contributing to this unplanned descent was an apparent unsafe landing gear condition induced by the design of the landing gear indicator lights, and the omission of the minimum crossing altitude at an approach fix depicted on the approach chart."[36]

Two similar accidents occurred in the following decade. Eastern Air Lines Flight 401 took place on December 29, 1972, when the entire flight crew becoming preoccupied with a burnt-out landing gear indicator light and failed to notice that the autopilot had inadvertently been disconnected. As a result, the aircraft gradually lost altitude and eventually crashed while the flight crew was distracted with the indicator problem.[37] Similarly, in United Airlines Flight 173 on December 28, 1978, the captain became preoccupied with a landing gear issue. This caused them to not properly monitor the aircraft's fuel state and his crewmember's advisories concerning this. This resulted in fuel exhausting to all engines and a subsequent crash.[38]

References

  1. ↑ Hagby: 326
  2. ↑ Hagby: 228
  3. ↑ Hagby: 230
  4. ↑ Hall: 103–105
  5. ↑ National Transportation Safety Board: 13
  6. ↑ 6.0 6.1 6.2 6.3 National Transportation Safety Board: 3
  7. ↑ 7.0 7.1 National Transportation Safety Board: 2
  8. ↑ National Transportation Safety Board: 11
  9. ↑ National Transportation Safety Board: 12
  10. ↑ National Transportation Safety Board: 4
  11. ↑ 11.0 11.1 National Transportation Safety Board: 5
  12. ↑ 12.0 12.1 National Transportation Safety Board: 6
  13. ↑ National Transportation Safety Board: 15
  14. ↑ 14.0 14.1 14.2 National Transportation Safety Board: 7
  15. ↑ National Transportation Safety Board: 8
  16. ↑ 16.0 16.1 National Transportation Safety Board: 9
  17. ↑ 17.0 17.1 17.2 17.3 National Transportation Safety Board: 17
  18. ↑ 18.0 18.1 National Transportation Safety Board: 20
  19. ↑ 19.0 19.1 National Transportation Safety Board: 18
  20. ↑ 20.0 20.1 20.2 National Transportation Safety Board: 21
  21. ↑ 21.0 21.1 Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ National Transportation Safety Board: 10
  23. ↑ National Transportation Safety Board: 35
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ National Transportation Safety Board: 16
  28. ↑ National Transportation Safety Board: 22
  29. ↑ 29.0 29.1 National Transportation Safety Board: 24
  30. ↑ 30.0 30.1 National Transportation Safety Board: 25
  31. ↑ National Transportation Safety Board: 26
  32. ↑ 32.0 32.1 National Transportation Safety Board: 27
  33. ↑ 33.0 33.1 National Transportation Safety Board: 28
  34. ↑ National Transportation Safety Board: 29
  35. ↑ 35.0 35.1 National Transportation Safety Board: 30
  36. ↑ 36.0 36.1 National Transportation Safety Board: 33
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=Scandinavian_Airlines_System_Flight_933&oldid=1767891"