CEN19CA227 · Vans RV-8
Vans RV-8 · Accident: hard landing
From DeKalb Taylor Municipal Airport (KDKB) to Wittman Regional Airport (OSH)
Event
- NTSB case
- CEN19CA227
- 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
Vans RV-8
- Aircraft type
- Vans RV-8
- 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
- N143MS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From DeKalb Taylor Municipal Airport (KDKB), De Kalb, ILTo Wittman Regional Airport (OSH), Oshkosh, WI
- Aircraft age
- About 2 years (built 2017)
- 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
- Hard landing
- 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
- Environmental issues › Operating environment
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was the second airplane in a flight of two and had been instructed by the air traffic controller to land on the orange dot on the runway (dots were used to facilitate multiple landings for the fly-in). During the descending turn from the base leg to the final leg, the pilot saw a third airplane. The third airplane appeared to be landing straight-in to the same runway. The air traffic controller instructed the flight of two to land further down the runway, on the green dot, to accommodate the third airplane. As the pilot adjusted the engine power and descent rate for the new landing point, he noted that the closure rate with the lead airplane in his flight of two had increased and that the lead airplane decelerated quickly as it landed. The pilot increased the pitch to overfly and avoid a collision with the lead airplane. After he confirmed that he was past the lead airplane, he adjusted the pitch and engine power to land, but the airplane landed hard. During the landing, the airplane settled left wing down and veered left off the runway, and the left main landing gear collapsed. The airplane sustained substantial damage to both wings and the fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain adequate spacing from the lead airplane while landing following revised landing instructions, which necessitated that the pilot conduct an improper landing flare and resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19CA227
- Event ID
- 20190720X61321
- Case number
- CEN19CA227
- 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: 1ee3a78bdc882e271e1287cc92ba2576b5ccdcd36ccf62fffff735feab25153f; retrieved 2026-09-16T09:28:04.939Z.