FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10FA101 · Cessna 172 N

17 Jan 2010 · Holland, MI, United States

Tulip City Air Service Cessna 172 N · Accident: loss of control in flight while maneuvering

From West Michigan Regional Airport (BIV) to West Michigan Regional Airport (BIV)

Report a problem

Event

NTSB case
CEN10FA101
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
2 · 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 172 N

Aircraft type
Cessna 172
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
N8405E
Onboard fatalities
Unknown
Route
From West Michigan Regional Airport (BIV), Tulip City, MITo West Michigan Regional Airport (BIV), Tulip City, 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
Maneuvering
Defining eventThe 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
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

  • Personnel issues › Action/decision
  • Personnel issues › Experience/knowledge

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot rented the airplane for most of the day to give rides to friends and had fueled it to capacity. He told a lineman that he planned to takeoff and, if necessary, would file an instrument-flight-rules flight plan and return to the airport. Witnesses saw the airplane take off and disappear into the overcast. Shortly thereafter, they heard an airplane make four passes over the airport. The sound became progressively louder but they could not see the airplane. On the fifth pass, the airplane was seen approximately 50 feet above the ground and it barely cleared a stand of trees. Recorded ATC transscripts revealed that the pilot contacted approach control and told the controller that he was caught in heavy fog and wanted vectors back to the airport. The airplane crashed shortly thereafter in a snow-covered field.

An examination of the airplane showed impact damage consistent with having descended to the ground in an uncontrolled spin. An examination of the airplane's systems showed no anomalies.

Although the pilot was instrument rated, he had not flown with instruments since receiving his rating 2 years ago. He had logged 1.8 hours in actual instrument meteorological conditions, 50.8 in simulated IMC, and 6.7 hours in a flight simulator. Ceiling and visibility at the time of the accident was below landing minimums and was recorded as 200 feet overcast and 3/4-mile in mist. The RNAV (GPS) RWY 8 approach chart was found on the pilot’s lap. Although the airplane was IFR certified, it was not RNAV or GPS equipped. Toxicology results indicated the presence of propoxyphene, a prescription narcotic medication. The concentration present was consistent with use at a time outside of 24 hours prior to the accident and would not have caused impairment. Cellular telephone records showed that the pilot had engaged in calls and text message conversations with the passenger the night before the accident. Starting at 6:00 P.M. the night before the accident, the pilot received or made calls or text messages every hour, through midnight, until 3:12 A.M. In one conversation, the passenger told the pilot that he would be in good flying shape for the next day, and the pilot replied that he needed to get 4 hours of rest before he flew. The final outgoing call to the passenger was placed at 7:59 A.M. on the day of the accident.

Probable cause

The pilot's decision to take off in known instrument meteorological conditions without instrument currency or recent instrument experience, which led to spatial disorientation resulting in an inadvertent spin. Contributing to the accident was the pilot's lack of adequate rest prior to the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10FA101
Event ID
20100119X42713
Case number
CEN10FA101
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 2ca7a7b1c8de88364e60c3a9ffa8f37af24c5fd8957374f61ce0ceb69ea73496; retrieved 2026-09-13T20:37:39.177Z.