CHI97FA200 · Piper PA-32R-301
Piper PA-32R-301 · Accident: loss of control in flight during initial climb
From SGS to Fort Dodge Regional Airport (FOD)
Event
- NTSB case
- CHI97FA200
- 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
- 0
- 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-32R-301
- 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
- N83353
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From SGSTo Fort Dodge Regional Airport (FOD), Fort Dodge, IA
- 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
- Initial climb
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush; Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Airspeed, not maintained
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff in gusty winds, the forward baggage door opened. The pilot attempted to return to the airport when the airplane impacted trees and descended into the river. The passengers stated the airplane was at a low altitude, the wings were rocking left and right, and a buzzer was sounding just before the accident. One passenger stated to his knowledge the baggage door was latched, but not locked prior to takeoff. Inspection of the baggage door latch after the accident showed it was in the latched position. No failure of the latch was noted which would have resulted in it opening during the flight. The takeoff was performed on runway 16 and the winds were from 210 degrees at 13 knots, gusting to 21 knots.
Probable cause
The pilot's failure to maintain adequate airspeed which resulted in a stall. Related factors were the pilot's diverted attention and gusty wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97FA200
- Event ID
- 20001208X08307
- Case number
- CHI97FA200
- 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: d2a29cb3678d83c8899866c76d5a0418d9843f5773a53156dd569fb73a369524; retrieved 2026-09-20T22:54:39.785Z.