FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Atlantic Airways Flight 670

10 Oct 2006 · Stord Airport, Sørstokken, Norway

British Aerospace 146-200A · Runway overrun due to hydroplaning

From Stavanger Airport, Sola (SVG) to Molde Airport, Årø (MOL)

Report a problem

Event

NTSB case
DCA07WA002
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Unknown · led by another country; figures from NTSB notifications
Event fatalities
4 · all aircraft and ground
Ground fatalities
Unknown
Occupants
16
Survivors
12
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
12
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

British Aerospace 146-200A

Flight
RC670
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
OY-CRG
Onboard fatalities
4
Route
From Stavanger Airport, Sola (SVG)To Molde Airport, Årø (MOL)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Non-U.S., Commercial
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Not recorded
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Psychological
  • Environmental issues › Physical environment
  • Organizational issues › Development

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Atlantic Airways Flight 670 was a crash following a runway overrun of a British Aerospace 146-200A at 07:32 on 10 October 2006 at Stord Airport, Sørstokken, Norway. The aircraft's spoilers failed to deploy, causing inefficient braking. The Atlantic Airways aircraft fell down the steep cliff at the end of the runway at slow speed and burst into flames, killing four of sixteen people on board.

The flight was chartered by Aker Kværner from Stavanger Airport, Sola via Sørstokken to transport its employees from there and Stord to Molde Airport, Årø. An investigation was carried out by the Accident Investigation Board Norway (AIBN). It was not able to find the underlying cause of the spoiler malfunction. However, it found that, when the captain selected the emergency braking, the anti-lock braking system was disabled. This selection caused the brakes to completely lock, resulting in reverted rubber hydroplaning, a condition in which the tires became extremely hot due to frictional forces, and the water on the damp runway surface evaporated to steam, effectively causing the tires to float on a cushion of steam over the runway surface, greatly reducing braking action. This situation was made worse with a minimal runway end safety area and lack of grooves in the runway surface.

Flight

Flight 670 was a regular, chartered morning return flight for Aker Kværner to transport its employees from Stavanger Airport, Sola and Stord Airport, Sørstokken to Molde Airport, Årø on 10 October 2006. The aircraft had landed at Sola at 23:30 the day before and a 48 flying hour scheduled inspection was carried out during the night and completed at 05:00. The flight departed Sola at 07:15, just after schedule, with twelve passengers and a flight crew of four. The pilot in command, 34-year-old Niklas Djurhuus, was pilot flying (PF), while the first officer, 38-year-old Jakob Evald, was pilot monitoring (PM). The pilots had flown in as passengers on an Atlantic Airways flight to Stavanger the evening before. The commander had carried out twenty-one landings at Sørstokken previously. The weather was reported as wind speed of 3 m/s, a few clouds at 750 m altitude, visibility exceeding 10 km and air pressure (QNH) of 1021 hPa.

Accident

Flight 670 contacted Flesland Approach at 07:23, stating that they would land on runway 15 and that they would carry out a visual approach. Flesland approach cleared the aircraft for a descent to 1,200 m at 07:24. The aircraft left controlled airspace at 07:27, at which time the aerodrome flight information service (AFIS) at Sørstokken had visual sight of the aircraft. The pilots decided to land at runway 32 as it would give a faster approach. The flaps were extended to 33 degrees at 07:31:12, reducing ground speed from 150 to 130 kn. The pilots aimed for a ground speed of 112 kn at touchdown and were guided by the precision approach path indicator. Upon passing the threshold the aircraft had a slightly high speed, at 120 kn. The aircraft touched down at 07:32:14, a few meters past the ideal landing point, in a soft landing.

The first officer called for the arming of the spoilers one second after touchdown, and the commander armed them half a second later. Two seconds later the first officer called "no spoilers" as the spoiler indicator light had not switched on. He then verified the hydraulic pressure and that the switch was set correctly. Meanwhile, the commander had switched the thrust levers from flight idle to ground idle, and six seconds after touchdown activated the wheel brakes. From 12.8 seconds after touchdown various screeching sounds could be heard from the tires. The braking took place nominally until halfway down the runway. From this point the pilots reported that nominal retardation did not occur. The commander attempted to use the brake pedals to apply full braking, without effect. He then moved the brake lever from green to yellow and subsequently emergency brake, disconnecting the anti-lock. Witnesses observed smoke and spray emitted from the landing gear.

By then, the aircraft had insufficient speed to abort the landing. Aware that the aircraft most likely would overrun, the commander opted to not steer it off the left where there was a steep descent, or to the right where there were rocks. As a last resort, the commander attempted to reduce speed by skidding the aircraft by first steering it right, and then abruptly to the left. The aircraft overran the runway at 22.8 seconds after touchdown, at 07:32:37. At the same time, the crash alarm was activated by AFIS. The aircraft slid off the runway at about a 45-degree angle, roughly north-west.

Investigation and cause

Investigation

The investigation was carried out by the Accident Investigation Board Norway (AIBN), who arrived by helicopter at the scene at 13:08. Three individuals filmed the accident, of which one was especially useful: from 13 seconds after the aircraft left the runway and subsequent 21 minutes was filmed by a witness across Stokksundet, 1.5 km from the site of impact. He sold the tape to TV 2, which subsequently handed the video over to AIBN. The investigators concluded that the runway was damp when they arrived, but were not able to conclude if it was wet at the time of the accident. It was nearly impossible to carry out a meaningful investigation of the fuselage because of the heat damage, although the detached left landing gear could be investigated.

The commission mapped all skid marks on the runway. The first skid marks found to be by OY-CRG was at 945 m past the threshold for runway 32. The aircraft also left rubber tire debris. Initially following the centerline, the aircraft was found to drift to the right after 1140 m and then shifted direction after 1206 m. From 1274 m the aircraft was skidding to the left, gradually reaching an angle of twenty-five degrees, at the time it ran off the runway at 1465 m.

The flight data recorder was recovered but had sustained substantial fire damage, exceeding its design limits. The tape-based Plessey Avionics PV1584J was sent to the Air Accidents Investigation Branch for investigation. They were only able to extract three segments of the flight, one hour during the flight from the Faroe Islands to Stavanger; 12 seconds during the approach to Sørstokken, ending 43 seconds before the final segment, which lasts for 3 seconds, ending three seconds before the end of the recording. The Fairchild A100S cockpit voice recorder used a solid-state storage medium. It was sent to the same laboratory, but no data could be retrieved there due to fire damage in the circuit board. However, when sent to the manufacturer, they were able to apply repairs to successfully retrieve the content. The sound files were sent to the Accident Investigation Board Finland, who were able to establish a timeline and that the spoiler lever had been set correctly.

All cockpit communication was strictly related to the flight and proper crew resource management was executed. The pilot stated that he believed the aircraft had sufficiently low speed that it would have stopped had the runway been 50 to 100 m longer. The first officer estimated the speed at the overrun time at 5 to 10 km/h and that the aircraft would have stopped had the runway been 10 to 15 m longer.

The six spoiler actuators were sent to the Royal Norwegian Air Force's facility at Kjeller for examination. Radiographic examinations confirmed that they were all in a closed and locked position. A simulation was carried out in a flight simulator to see if, given the conditions, a 146 could land at Sørstokken without operative spoilers. It concluded that this would be possible with a dry runway, but not if it is wet. An extensive investigation of the spoiler system was carried out by Aviation Engineering, who published their findings on 10 May 2011. AIBN quickly started working out from a hypothesis that the spoilers did not deploy and investigated three possible causes: a mechanical failure in the lever, a failure in two thrust lever micro switches, and an open circuit breaker in the lift spoiler system. In the latter case, it would have been necessary for two of four to fail although one could have failed without being detected.

The commission found that the approach and landing were normal with natural variations but that the spoilers were not deployed when the pilot pulled the lever. No conclusion to the cause was found, although the commission believed it must either have been a mechanical fault in the spoiler lever mechanism or a fault in two of the four thrust lever micro switches. The pilots received warning of the failure of deployment and also noticed the lack of sufficient retardation, but failed to connect the two issues, instead focusing on the wheel brakes. The pilots perceived they would not stop in time and activated the emergency braking system. This system bypasses the antilock braking system and can lock the wheels completely. In this incident the wheels locked and the tires rapidly heated due to friction with the runway surface. Combined with damp conditions on a non-grooved runway, this situation resulted in reverted rubber hydroplaning, a state where the heated rubber created a layer of steam between the tires and the runway thereby further significantly decreasing the effectiveness of the braking system and adding approximately 60% to the distance required to stop. The lack of runway grooving was decisive for the hydroplaning to take place. The aircraft was estimated to be traveling at 15 to 20 kn at the time of the overrun. Had optimum braking taken place, the aircraft would probably have come to a stop on the runway. The massive damage was not caused by the overrun as such, but rather the steep slopes on the side of the runway.

Further, the commission found that the fire was caused by a fuel leak ignited by a short circuit. This spread to the fuel tanks, leading to the scale of the inferno. Supply of ample oxygen was provided by an engine still running. All people on board had a chance of survival, but that rapid and correct evacuation was decisive for actual survival. Although the fire crew were quick to the scene, they were hindered by the terrain, preventing efficient containment of the fire during the crucial evacuation period. The aircraft and crew were found to be fit, airworthy and certified. No training or procedures were available in case spoilers failed to deploy, and that these could have prevented the accident. The airport's physical geography and lack of adequate safety were decisive in the outcome of the accident.

Text from the Wikipedia article “Atlantic Airways Flight 670” (revision 1348986491, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

Sources

Wikipedia article: Atlantic Airways Flight 670
Article
Atlantic Airways Flight 670
Revision
1348986491 · 2026-04-15 · retrieved 2026-09-18
Wikidata
Q2822713
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA07WA002
Event ID
20061011X01495
Case number
DCA07WA002
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
Record
Wikipedia article "Atlantic Airways Flight 670" (page 7378014, revision 1348986491); merged with NTSB case DCA07WA002 (events / aircraft)
Date
Wikipedia infobox: date
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA07WA002
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Atlantic Airways Flight 670" and NTSB case DCA07WA002, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • No bulk values were replaced by the NTSB case API.