CHI02FA067 · Cessna 402B
Riley Aviation Cessna 402B · Accident: loss of control in flight en route
From Kirsch Municipal Airport (IRS) to Ann Arbor Municipal Airport (ARB)
Event
- NTSB case
- CHI02FA067
- 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
Cessna 402B
- Aircraft type
- Cessna 402
- 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
- N371JD
- Operator
- Riley Aviation
- Onboard fatalities
- Unknown
- Route
- From Kirsch Municipal Airport (IRS), Sturgis, MITo Ann Arbor Municipal Airport (ARB), Ann Arbor, MI
- 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
- 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
- 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 › Maneuver to avoid obstructions, performed
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The aiplane was destroyed when it impacted the ground while maneuvering at a low altitude following a loss of control in instrument meteorological conditions. The airplane was on a flight in instrument meteorological conditions when radar and voice contact were lost. Prior to the loss of communication, controllers advised the pilot to check altitude. At this point, the radar data shows that the airplane was about 400 feet below the assigned altitude. Subsequently, the pilot said, "roger sir my auto pilot i just cut off uh correcting immediately." This was the last received transmission from the pilot. The radar data shows that the airplane then began a descending right turn at an average rate of descent of 1,276 feet per minute. This descent was followed by a climbing left turn with an average rate of climb of 5,423 feet per minute. The radar data shows that the radius of the left turn continued to decrease until radar contact was lost about 500 feet above the last assigned altitude. A witness who saw the airplane just prior to impact described the airplane maneuvering beneath the clouds prior to pulling up sharply and then pitching down and impacting the ground. There was a utility wire and associated poles running across the airplane's fight path in the field where the wreckage was located. The airplane exploded and burned upon impact. No anomalies were found with the airplane or associated systems. The autopilot section of the Pilot 's Operating Handbook states, "Sustained elevator overpower will result in the autopilot trimming against the overpower force." The result is that if up elevator pressure is applied with the autopilot engaged, the autopilot will trim the airplane nose down.
Probable cause
The maneuver to avoid the utility wire while maneuvering resulting in an inadvertent stall and subsequent impact with the ground. Factors were the pilot's inadvertent activation of the elevator trim, resulting in a loss of control during flight in instrument meteorological conditions, as a result of pilot's lack of knowledge concerning the operation of the autopilot system. Another factor was the utility wire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02FA067
- Event ID
- 20020201X00166
- Case number
- CHI02FA067
- 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: 134062f00831a776fa584961d2c250058f34702e8e9bc24678e3f04e9285630b; retrieved 2026-09-20T20:14:05.492Z.