FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI97FA059 · Cessna 401

22 Jan 1997 · Crystal, MN, United States

Air One Cessna 401 · Accident: in flight collision with object during initial climb

From Crystal Airport (MIC) to Capital Region International Airport (LAN)

Report a problem

Event

NTSB case
CHI97FA059
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
0 · 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
Instrument Meteorological Cond

Cessna 401

Aircraft type
Cessna 401
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
N5AS
Operator
Air-One
Onboard fatalities
Unknown
Route
From Crystal Airport (MIC)To Capital Region International Airport (LAN), Lansing, 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
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
In flight collision with object
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

  • Airframe › Ice
  • Pilot in command › Aircraft preflight, inadequate
  • Pilot in command › Ice/frost removal from aircraft, inadequate

Approximate · Estimated position: the centre of Crystal, MN, the place the record names. Not the accident site.

NTSB narrative

After landing at the airport, the airplane was taxied to a fixed base operator to pick up a passenger. Rime ice, as thick as two inches was seen on the airplane, and the pilots of the airplane attempted to manually remove the ice. The airplane was topped off with fuel before departure. During departure from runway 31R, the airplane collided with a fence. Numerous areas of ice were found on the airplane following the accident. Both propellers had similar damage. The pilots had reported to the FAA that the left engine had sustained a loss of power. The passenger reported that he did not notice any loss of power from either engine. No preimpact part failure or malfunction of the left engine was found.

Probable cause

failure of the pilot-in-command to ensure adequate removal of airframe ice from the aircraft during preflight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI97FA059
Event ID
20001208X07263
Case number
CHI97FA059
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: 35e6b500ca83230b4a770d7b6f359183ebb43230dd3e0c84f581f8d578f7a426; retrieved 2026-09-21T21:30:56.181Z.