The U.S. aircraft register, updated daily
Accidents · NTSB CEN16LA098 · Final report

Cessna 441 accident near Fargo, North Dakota, January 8, 2016

On January 8, 2016 at about 3:00 pm local time, a 1980 Cessna 441, registered N779CC, was substantially damaged in an accident during landing (flare/touchdown) near Fargo, North Dakota (Hector International Airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot’s failure to cycle the surface deice boots during the instrument approach in icing conditions, which led to ice accumulation on the leading edges of the wings and empennage, and resulted in an aerodynamic stall and subsequent hard landing.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 8, 2016 · about 3:00 pm local time
Place
Fargo, North Dakota · Hector International Airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cessna 441, built 1980 · all 441s on the register
Registration
N779CC · registry record · serial 4410155
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The airline transport pilot reported that the accident flight was the airplane's first flight after a phase maintenance check, and that he was repositioning the airplane to an airport about 40 nautical miles away. While en route, the airplane experienced a series of avionics and fuel-related anomalies. The pilot eventually declared an emergency and was cleared to land at the destination airport. The first approach for landing in instrument meteorological conditions resulted in a missed approach. The pilot reported that, about this time, the airframe was accumulating ice and he cycled the deice boots. During the second approach, the airplane broke out of the clouds, and the pilot proceeded to land. The pilot reported that, before he initiated the landing flare, he reduced engine power to idle, fully extended the flaps, and flared the airplane. He stated the airplane was shaking and shuddering, but no stall warning horn sounded, and then the "bottom fell out." The airplane landed hard, and the left engine's propeller blades struck the runway. The airplane incurred wing spar and propeller damage. A postflight examination of the airplane revealed between ½ to 1 inch of rime ice on the leading edge surfaces of both wings, the horizontal stabilizer, and the vertical stabilizer. The pilot's operating handbook for the airplane stated that the deicing boots should be cycled as necessary when ice accumulation reached between ¼ and ½ inch. The amount of ice on the wing and empennage surfaces after the accident was consistent with the pilot not cycling the deice boots as prescribed, which resulted in an excessive ice accumulation on approach and a subsequent aerodynamic stall during the landing flare.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Structural icing during approach
  2. Aerodynamic stall/spin during landing (flare/touchdown)
  3. Hard landing during landing (flare/touchdown) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • cause Aircraft › Aircraft systems › Ice/rain protection system › Airfoil anti › ice, deice › Not used/operated
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Capability exceeded
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Drizzle/mist › Contributed to outcome

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 2,274 hours in all; 82 in this make and model; 65 in the last 90 days; 25 in the last 30 days
  • Last flight review: August 7, 2014
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 6,226 hours
  • Last inspection: approved inspection programme, December 6, 2015
  • Maximum gross weight: 9,850 lb
  • Seats: 9
  • Landing gear: retractable
  • Engine 1: Honeywell TPE 331-10N (turboprop); 0 hours total
  • Engine 2: Honeywell TPE 331-10N (turboprop); 0 hours total

The flight

  • Departed from: DTL Detroit Lakes MN at 2:30 pm
  • Destination: FAR Fargo ND
  • Flight plan: IFR
  • Runway 36, 9,001 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 340° at 19 knots
  • Visibility: 5 statute miles
  • Sky: overcast at 7,000 ft; clear
  • Temperature: 19°F (-7°C), dew point 16°F (-9°C)
  • Altimeter: 29.97 inHg
  • Observation at 2:53 pm from FAR

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.