CHI08FA054 · Piper PA-32R-300
Wisconsin Aviation Piper PA-32R-300 · Accident: loss of control in flight en route
From Chippewa Valley Regional Airport (EAU) to Watertown Municipal Airport (RYV)
Event
- NTSB case
- CHI08FA054
- 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
- 1 · 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
Piper PA-32R-300
- Aircraft type
- Piper PA-32
- 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
- N1919H
- Operator
- Wisconsin Aviation
- Onboard fatalities
- Unknown
- Route
- From Chippewa Valley Regional Airport (EAU), Eau Claire, WITo Watertown Municipal Airport (RYV), Watertown, WI
- 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
- 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
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Flight into known adverse weather, performed
- Pilot in command › Spatial disorientation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The air traffic controller who was working the tower position at the departure airport reported that the accident airplane had landed at the airport. Within about 10 - 15 minutes, the pilot departed again. It was dark, and the weather was "just above" visual flight rule (VFR) minimums during the airplane's arrival and departure. The pilot did not file a flight plan. Radar track data indicated that the accident airplane flew about a 131-degree magnetic heading at about 2,500 feet mean sea level (msl) from the departure airport to the airspace near the accident site at the time associated with the accident. The radar track data indicated that the airplane was in a left, descending turn prior to being "lost" from radar contact, consistent with spatial disorientation. The post-crash inspection of the airplane revealed no preexisting anomalies. The accident site bordered an area of instrument flight rule (IFR) conditions, and was within the area with marginal VFR conditions at the time of the accident. Weather data obtained from a reporting station about 100 miles east-northeast of the accident site indicated multiple freezing levels, first at approximately 1,000 feet above ground level (agl) with temperatures below freezing to 1,500 feet, and the second freezing level at approximately 4,746 feet msl.
Probable cause
The decision by the pilot to fly into known adverse weather, and the pilot's failure to maintain control of the airplane due to spatial disorientation. Contributing factors include the clouds and the night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08FA054
- Event ID
- 20071231X02011
- Case number
- CHI08FA054
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-12-21.
- API snapshot SHA-256: d80e5f5723516adbf12cb97b2115f4820b44c953bfe3f761dc651b4d19096ed1; retrieved 2026-09-20T16:03:04.376Z.