CEN12CA509 · Cessna 182Q
Cessna 182Q · Accident: abnormal runway contact during landing
From Abraham Lincoln Capital Airport (SPI) to Three Lakes Municipal Airport (40D)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN12CA509
- 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 182Q
- 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
- N1DV
- Operator
- Vecchie Donald J
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Abraham Lincoln Capital Airport (SPI), Spingfield, ILTo Three Lakes Municipal Airport (40D), Three Lakes, WI
- 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 · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Upon arrival at his destination airport after an uneventful instrument flight rules flight, the pilot entered the left downwind leg of the traffic pattern for a visual landing. The initial flare and touchdown were smooth at 85 knots. The airplane then floated and bounced twice, the nose gear collapsed, and the airplane came to rest about halfway down the runway. An examination of the airplane showed that the nose gear was separated from the airplane, resulting in substantial damage to the engine firewall. The pilot reported that he should have slowed to about 70 to 75 knots for touchdown to avoid floating and the subsequent bounced landing. The pilot stated that he was a corporate jet pilot and that he flew light reciprocating-engine aircraft only a few times a year. His perspective was that in flying corporate jets, computations of final approach speeds are more precisely determined and executed by the pilot. Final approach speeds in the light airplane category are determined moreso by an airspeed range depending on the wind conditions and gross weight. He offered that his higher-than-optimal approach speed was a result of not having recent experience in flying light airplanes. He stated that he had not flown a light aircraft for 6 months prior to this event.
Probable cause
The pilot's excessive touchdown speed, which resulted in a bounced landing. Contributing to the accident was the pilot's lack of recent experience in flying light airplanes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12CA509
- Event ID
- 20120802X61111
- Case number
- CEN12CA509
- 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: 541bc2d3488d61fd7f6f5a57a1427c34a7caa349fee79e7f2e0c9793b04e4427; retrieved 2026-09-15T19:11:56.714Z.