CHI96LA266 · Cessna 404
Cessna 404 · Accident: in flight collision with object on approach
From Kalamazoo/Battle Creek International Airport (AZO) to an unrecorded destination
Event
- NTSB case
- CHI96LA266
- 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
- Charter & commuter
- 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 404
- Aircraft type
- Cessna 404
- 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
- N8919G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kalamazoo/Battle Creek International Airport (AZO), Kalamazoo, MITo not recorded
- 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 135: Air Taxi & Commuter
- 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
- Approach · VFR go-around
- 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
- 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
- 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
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not attained
- Pilot in command › Go-around, delayed
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that during the landing approach, the flight visibility was inadequate for landing, and he aborted the landing. Witnesses observed the airplane touch down long and fast, then it entered fog that shrouded the runway. Subsequently, the airplane collided with trees, then impacted on marshland about 70 feet below the runway elevation. No mechanical anomalies were found with the airplane or engines that would prevent flight. On the day before the accident, the pilot's duty day began at 0500. He had a 9-hour rest period (during the day) that did not involve any sleep. The pilot said that after work on the day before the accident, he arrived home about 2300. His wife said he awoke about 0230 on the accident date, then he returned to bed and arose between 0430 and 0500, departing for work about 0530. During his regular duty day rest period, the pilot would drive a total of 4 hours to and from his home each day. The pilot said he would generally get to bed about 2300 to 2330, arising about 0430 each work day. Also, he said he needed between 6 and 8 hours of sleep at night.
Probable cause
the pilot's delay in initiating a go-around after not attaining the proper touchdown point during the landing, and his failure to remain clear of obstructions (trees) during the go-around. Factors relating to the accident were the adverse weather condition (fog and low ceiling), pilot fatigue, and the proximity of trees to the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA266
- Event ID
- 20001208X06435
- Case number
- CHI96LA266
- 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: 24378a96381ecd2293a8384199f58f130fece0791fc1d142d393d63b63815011; retrieved 2026-09-18T17:48:09.183Z.