CHI07FA183 · Piper PA-46-500TP
Piper PA-46-500TP · Accident: in flight encounter with weather en route
From Spirit of St Louis Airport (SUS) to Buffalo Municipal Airport (CFE)
Event
- NTSB case
- CHI07FA183
- 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
- 3 · 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
- Visual Meteorological Cond
Piper PA-46-500TP
- Aircraft type
- Piper PA-46
- 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
- N477MD
- Operator
- David L. McCormick · private individual
- Onboard fatalities
- Unknown
- Route
- From Spirit of St Louis Airport (SUS), ST LOUIS, MOTo Buffalo Municipal Airport (CFE), Buffalo, MN
- 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
- 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
- En route · climb to cruise
- First occurrenceThe 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
- In flight encounter with weather
- 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
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Anti-ice/deice system, not used
- Pilot in command › Checklist, not complied with
- Pitot/static system › Ice
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot, before departure, obtained a weather briefing that indicated there were thunderstorms and areas of heavy precipitation along the route of flight. The pilot told the briefer that the airplane was equipped with onboard radar for weather avoidance. After takeoff, the pilot received two adverse weather advisories from the departure air traffic controller. The pilot acknowledged, requested and was cleared for course deviations to avoid the weather. The pilot was subsequently told to contact an en route traffic control center. The pilot did not request an update on, nor was he advised of, any additional adverse weather after switching over. Avionics data recovered from the wreckage showed the airplane encountered decreasing outside air temperatures (OAT) during the en route climb to a cruise altitude. The OAT decreased below freezing as the airplane climbed through 15,900 feet mean sea level. The primary flight display's (PFD) airspeed data decreased from about 140 knots indicated airspeed (KIAS) to 0 KIAS. During the loss of airspeed, the airplane's recorded climb rate decreased and the airplane entered a left turn. At this point, the en route controller asked the pilot if he had been given a clearance to deviate around weather. The pilot responded, "mike delta we've got problems uh... ." There were no additional communications received from the pilot and radar contact with the airplane was lost shortly thereafter. The recovered PFD data indicated that the airplane exceeded its maximum structural operating speed during a rapid descent. In the descent, the airplane reached a ground speed of 250 knots and vertical loads reaching 5g. The recovered data and witness marks from the right wing indicated the airplane sustained an in-flight breakup after exceeding the airplane's maximum load factor limit. A review of the available weather data indicated that there was an area of extreme precipitation associated with thunderstorms east of the accident site and that the airplane was likely in instrument meteorological conditions at the time of the upset. An on-scene investigation did not reveal any pre-impact anomalies with the airplane and its related systems. Analysis of the recovered PFD and Multi-Function Display (MFD) data indicated that the pilot did not utilize the available pitot tube heat that would have afforded ice protection. Recovered PFD/MFD data, along with a weather analysis, indicated that the airplane was operating in an environment conducive for pitot tube icing. Additionally, recovered data showed airspeeds were recorded during the rapid descent at altitudes lower than the observed freezing level. The before takeoff checklist indicated, "Pitot Heat ... ON."
Probable cause
The pilot's failure to activate the pitot heat as per the checklist, resulting in erroneous airspeed information due to pitot tube icing, and his subsequent failure to maintain aircraft control. Contributing to the accident was the pilot's continued flight in an area of known adverse weather.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07FA183
- Event ID
- 20070705X00878
- Case number
- CHI07FA183
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 707abffd08ddcd021ede2e58293176f3b8cdcd1619102c3681c9855fb40fe224; retrieved 2026-09-20T16:31:26.948Z.