FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA055 · Cessna 182P

21 Dec 2001 · Elkhart, IN, United States

Cessna 182P · Accident: in flight collision with object on approach

From Ann Arbor Municipal Airport (ARB) to Mishawaka Pilots Club Airport (3C1)

Report a problem

Event

NTSB case
CHI02LA055
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
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
Visual Meteorological Cond

Cessna 182P

Aircraft type
Cessna 182
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
N58797
Operator
Donald C. Camp · private individual
Onboard fatalities
Unknown
Route
From Ann Arbor Municipal Airport (ARB), Ann Arbor, MITo Mishawaka Pilots Club Airport (3C1), Elkhart, IN
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
Approach · VFR pattern final
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

  • Pilot in command › Altitude, low

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

NTSB narrative

The airplane contacted the passenger side of a pickup truck while on short final approach. Neither the pilot nor the driver of the truck saw each other prior to the accident. Witnesses reported seeing the airplane "too low" on final approach just prior to the collision. The witnesses reported that the nose gear of the airplane contacted the side of the truck. The airplane then contacted the ground and nosed over. The end of the runway is approximately 50 feet from the south edge of the road. The runway had a 200 foot displaced threshold.

Probable cause

The pilot allowed the airplane's altitude to get too low while on final approach. A factor associated with the accident was the pickup truck which the airplane struck.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA055
Event ID
20011227X02443
Case number
CHI02LA055
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: 5d05b0acb8d91439e567b752161deb2c2c70b8dbf606c9757392f236676481ac; retrieved 2026-09-21T09:42:47.497Z.