CHI06CA203 · Cessna 182
Cessna 182 · Accident: in flight collision with object during landing
From Dupont-Lapeer Airport (D95) to Napoleon Airport (3NP)
Event
- NTSB case
- CHI06CA203
- 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 182
- 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
- N6155B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dupont-Lapeer Airport (D95), Lapeer, MITo Napoleon Airport (3NP), Napoleon, 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
- 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
- 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
- Substantial
Cause areas
- Pilot in command › Go-around, not performed
- Pilot in command › Proper touchdown point, exceeded
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane contacted fence posts, a fence, and a tree during an aborted landing. The pilot reported that he made a go around on his first landing approach because he was coming in high and long. He stated that the second approach was high, but he landed on the runway. He stated that he felt he did not have enough runway left to stop so he added full power. The pilot reported that he did not receive the expected response from the airplane, so he pulled the power off and landed the airplane back on the runway. Inspection of the grass airstrip and airplane revealed ground tracks began more than half way down the 2,740 foot long runway and right of the runway center. The ground scars indicate the left wing contacted the ground and the airplane slid to the left back toward the centerline. The tire tracks disappeared approximately 120 feet from the end of the runway. The airplane then contacted several fence posts, separating a tip of one of the propeller blades. Ground marks indicated the right wing then contacted the ground prior to the airplane contacting a chain link fence and a fence post. The leading edge of the right wing then contacted a tree trunk about 6 feet above ground level, separating the outboard section of the wing. The airplane continued for a short distance prior to striking smaller trees and coming to rest. The landing was being made on runway 27 and the pilot reported the winds were from 040 degrees at 7 knots.
Probable cause
The pilot failed to perform a go-around which resulted in landing long on the airstrip. Factors associated with the accident were the tailwind, the pilot's selection of runway direction, the fence posts, the fence, and the trees which were contacted.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06CA203
- Event ID
- 20060830X01256
- Case number
- CHI06CA203
- 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, coordinates. 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: 5d86a4caab318d91902502d758a4cf086a1694c6cfe89b0f35ef79603de53873; retrieved 2026-09-22T04:39:59.560Z.