FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA158 · SOCATA TBM700 B

27 Feb 2017 · Bellingham, WA, United States

4197802 Manitoba SOCATA TBM700 B · Accident: loss of control in flight during takeoff

From Bellingham International Airport (BLI) to Pierce County-Thun Field (PLU)

Report a problem

Event

NTSB case
GAA17CA158
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
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

SOCATA TBM700 B

Aircraft type
Socata TBM700
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
CGWVS
Onboard fatalities
Unknown
Route
From Bellingham International Airport (BLI), Bellingham, WATo Pierce County-Thun Field (PLU), Puyallup, WA
Aircraft age
About 15 years (built 2002)
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
Part 91: General Aviation
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
Takeoff
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, during the preflight, it was snowing, and he wiped the snow that had accumulated on the wings off "as best as [he] could." He added that, while taxiing to the runway, "snow was falling heavily," and he observed "light accumulation of wet snow" on the wings. During the takeoff roll, he observed the snow "sloughing off" the wings as the airspeed increased. Subsequently, during the climb to about 150 ft above the ground, the airplane yawed to the left, and he attempted to recover using right aileron. He reported that he "could see a stall forming," so he lowered the nose and reduced power to idle. The airplane impacted the general aviation ramp in a left-wing-down attitude and slid 500 to 600 ft.

The pilot reported on the National Transportation Safety Board Aircraft Accident/ Incident Report 6120.1 form that the airplane stalled, and he recommended "better deicing" before takeoff.

The airplane sustained substantial damage to the fuselage and left wing.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

A review of recorded data from the automated weather observation station located on the airport revealed that, about 27 minutes before the accident, the wind was 010° at 8 knots, 1/2-mile visibility, moderate snow, freezing fog, and sky condition broken at 500 ft above ground level (agl) and overcast at 1,500 ft agl. The airplane departed from runway 16.

The Federal Aviation Administration (FAA) Aeronautical Information Manual stated, in part: "The presence of aircraft airframe icing during takeoff, typically caused by improper or no deicing of the aircraft being accomplished prior to flight has contributed to many recent accidents in turbine aircraft."

The manual further stated, "Ensure that your aircraft's lift-generating surfaces are COMPLETELY free of contamination before flight through a tactile (hands on) check of the critical surfaces when feasible. Even when otherwise permitted, operators should avoid smooth or polished frost on lift-generating surfaces as an acceptable preflight condition."

FAA Advisory Circular, AC 135-17, stated in part: "Test data indicate that ice, snow, or frost formations having thickness and surface roughness similar to medium or course sandpaper on the leading edge and upper surfaces of a wing can reduce wing lift by as much as 30 percent and increase drag by 40 percent."

Included in the public docket for this report is a copy of a service bulletin from the airplane manufacturer, which describes deicing and anti-icing ground procedures. It stated, in part:

During conditions conducive to aeroplane icing during ground operations, take-off shall not be attempted when ice, snow, slush or frost is present or adhering to the wings, propellers, control surfaces, engine inlets or other critical surfaces.

This is known as the "Clean Aircraft Concept". Any deposit of ice, snow or frost on the external surfaces may drastically affect its performance due to reduced aerodynamic lift and increased drag resulting from the disturbed airflow.

Probable cause

The pilot’s failure to properly deice the airplane before takeoff, which resulted in an aerodynamic stall during the initial climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA158
Event ID
20170228X14333
Case number
GAA17CA158
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 7061afcbbec1ac98aa4f228040abf9be60a114688bc85f95aecde76e971fb7d9; retrieved 2026-09-16T05:02:50.656Z.