FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI05FA016 · Cessna P210N

26 Oct 2004 · Wautoma, WI, United States

Cessna P210N · Accident: in flight encounter with weather en route

From Chicago Executive Airport (PWK) to Pine River Regional Airport (PWC)

Report a problem

Event

NTSB case
CHI05FA016
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
2 · 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

Cessna P210N

Aircraft type
Cessna 210
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
N5485W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chicago Executive Airport (PWK), CHICAGO/PROSPEC, ILTo Pine River Regional Airport (PWC), Pine River, 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 · 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 › Design stress limits of aircraft, exceeded
  • Wing › Overload

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

NTSB narrative

The airplane was destroyed during an in-flight break-up and subsequent impact with terrain. The pilot advised the controller that the airplane was losing its gyros and that he needed to descend. The pilot then reported that the gyros appeared to be working. The controller advised the pilot that the airplane was on a southwest heading and that the pilot could fly whatever altitude he was able to maintain. The controller was looking for an airport with visual meteorological conditions present and asked the pilot if the airplane was in the clouds. The pilot reported affirmative. The pilot's last transmission was that it was going into a spin. Radar contact was lost about that time. In a Sheriff's report, two witnesses indicated that they heard thunder or jets flying. The report showed that they heard a "high winding noise from [the] plane engine." The noise was directly above their position and they heard a loud bang. They reported seeing a plane at about 1,500 to 2,000 feet above ground level. The airplane was observed spinning straight down without its wings. The witnesses indicated that they observed something hanging from its tail section. A Meteorological Factual Report was compiled and the flight's plotted radar track showed that the airplane was in layered clouds and that there was visual flight rules weather conditions below the clouds. Recorded groundspeed varied between 130 to 160 knots. Winds aloft were headwind and quartering winds. The airplane's information manual's limitations section stated, in part, "Maneuvering Speed:4000 pounds-130 Knots Indicated Air Speed (KIAS), 3350 pounds-119 KIAS, 2700 pounds-106 KIAS Remarks: Do not make full or abrupt control movements above this speed." A flapper valve in the vacuum manifold exhibited deterioration and a crack. General observation of the manifold revealed that it had been disassembled and reassembled with non-manufacturer specified rivets. No further airframe of engine preimpact anomalies were detected with the recovered wreckage. Examination of instrument gyro rotors revealed rotational scoring. Post-accident toxicology evaluation of specimens from the pilot was consistent with the intermittent use of fluoxetine (a prescription antidepressant often known by the trade name Prozac). The pilot did not indicate any mental conditions or the use of any psychiatric medications on applications for airman medical certificate.

Probable cause

The pilot not maintaining airplane control during cruise flight in instrument meteorological conditions after reporting a loss of gyros leading to his exceeding the design load limits of the wings. Factors were the clouds, the deteriorated vacuum manifold flapper valve, and the non-factory modification of that manifold by an unknown party.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI05FA016
Event ID
20041102X01741
Case number
CHI05FA016
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, 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: 1c5d5c9b91ad8f431283b3555704ec8e32ff76debdc62c34cfdc26a475a2ba4f; retrieved 2026-09-20T18:15:38.429Z.