Delayed Reaction: Severe Icing and the Minutes That Matter
An instrument-rated TBM 700 pilot climbed into icing he'd been warned about and asked for a higher altitude instead of declaring. About two minutes later the airplane came apart. Based on the AOPA Air Safety Institute case study and the NTSB final report, a look at using your command authority early.
Ice protection buys time. It doesn't buy permission to stay. When ice builds faster than the airplane can handle, the only fix is to leave, and the longer you wait for a routine clearance, the less airplane you have left to leave with.
The AOPA Air Safety Institute (ASI) re-creates this flight in its video "Accident Case Study: Delayed Reaction," which you can watch below. The summary that follows is ours and is based on the NTSB final report (ERA12FA115), which also gives the official probable cause. Watch the full case study for ASI's own analysis.
The flight, in short
On December 20, 2011, a 45-year-old instrument-rated private pilot with about 1,400 hours departed Teterboro, New Jersey (TEB) in a Socata TBM 700 on an IFR flight plan to Atlanta (PDK), planning to cruise at FL260. Four passengers were aboard. He had filed his flight plan online at 0700, but the NTSB found no record that he got a weather briefing, and no weather was requested or issued on the ground at Teterboro. An AIRMET for moderate icing from the freezing level to FL200 was issued at 0945. The flight departed about 0950.
On the climb, the controller warned of moderate rime icing from 15,000 to 17,000 feet, with light rime at 14,000, and asked the pilot to report if it got worse. The pilot said they'd let him know and that if they could go straight through, “it’s no problem for us.” He entered the clouds climbing through about 12,800 feet.
At 10:02, level near 16,800 feet, the pilot told the controller “light icing has been present for a little while and a higher altitude would be great.” The airplane's groundspeed was about 101 knots. Seventeen seconds later he reported “a little rattle” and asked to climb as soon as possible. The controller coordinated and cleared him to FL200 about 25 seconds later. Just over a minute after that, the airplane peaked at 17,800 feet, turned sharply left and descended. Passing 17,400 feet the pilot transmitted “and N731CA’s declaring…” and nothing more. The outboard right wing separated in flight and struck the tail. The airplane hit Interstate 287 near Morristown, and all five people aboard were killed.
The NTSB determined the probable cause to be: “The airplane’s encounter with unforecasted severe icing conditions that were characterized by high ice accretion rates and the pilot's failure to use his command authority to depart the icing conditions in an expeditious manner, which resulted in a loss of airplane control.”
Why the delay matters
Pilots in the area that morning reported icing, and at least three crews called it severe. The airplane's handbook warned that it wasn't certificated for severe icing and told pilots who meet it to request priority handling and change altitude or route immediately. The NTSB said the pilot likely either didn't recognize how bad the icing was or was reluctant to use his command authority to get out right away.
- Treat a controller's icing report as a reason to plan your exit before you enter the clouds, not after.
- Watch the airspeed. A steady drop at the same power setting is the airplane telling you how much ice it's carrying.
- Declare early. “Request higher” puts you in line. An emergency puts you first.
- Know your airplane's limits cold. Ice protection certified for known icing is not certified for severe icing.
Putting it into practice
Why it matters
As pilot in command, you can take the altitude or heading you need and sort out the paperwork later. That authority only helps if you use it while there's still time. PlaneWX never recommends GO or NO‑GO. The pilot makes the call.
Decision loop
- 1Weather Briefing
- 2FRAT
- 3GO / NO-GO
- 4Self Debrief
Mentor is an optional layer on any step, not a fifth stage.
Tool or habit
Brief every flight, even a short hop out of a busy airport. PlaneWX's icing analysis shows model agreement, cloud layers and SLD potential along your route and altitude, and the WX Score checks it against your own icing limits. Use the FRAT, which opens 4 hours before departure, to write down your plan if the ice is worse than forecast. You record your own GO / NO‑GO decision.
Sources
- AOPA ASIAOPA Air Safety Institute: Accident Case Study: Delayed Reaction (video)
- NTSBNTSB Aviation Investigation Final Report ERA12FA115 (N731CA)
PlaneWX complements FAA and Flight Service weather products. PlaneWX is decision support. It is not a substitute for your full preflight briefing (for example a standard briefing through Flight Service or your EFB).