CHI99LA170 · Cessna T210N
Cessna T210N · Accident: overrun during landing
From 7D2 · Troy, MI to Kalamazoo/Battle Creek International Airport (AZO)
Event
- NTSB case
- CHI99LA170
- 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
- Visual Meteorological Cond
Cessna T210N
- 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
- N9612Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 7D2 · Troy, MITo Kalamazoo/Battle Creek International Airport (AZO)
- 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
- Landing · aborted
- 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
- Overrun
- 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 › Aborted landing, not obtained
- Pilot in command › Airspeed, excessive
- Pilot in command › Proper touchdown point, not obtained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aircraft overran the departure end of the runway and struck an airport boundary fence and an automobile. In a written statement, the pilot reported the following, 'High approach to runway 27. Touched down approximately half way down the runway. Decision was made to go around. Added full power, mixture rich, propeller takeoff position. Proceeded with forced landing. Impacted fence at departure end of runway 27. Deplaned aircraft.' A video tape taken of the accident site revealed that there were black marks from the runway numbers of runway 05, across the north south road and towards the main wreckage. The threshold of runway 05 is displaced 315 feet. The throttle, mixture and propeller controls were in the forward position. The fence was wrapped around the aircraft's spinner and behind the propeller hub. The trailing edge flaps were in the 10-degree position. The engine was run on the airframe and no anomalies were noted.
Probable cause
the excessive airspeed, the proper touchdown point not obtained and the aborted landing not performed by the pilot. The fence and automobile were contributing factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA170
- Event ID
- 20001212X18733
- Case number
- CHI99LA170
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1999-05-29.
- API snapshot SHA-256: dca6d650853630decea8137c781554616e71e849c5669ca8f5bf4402c7651151; retrieved 2026-09-21T11:02:27.364Z.