CEN17LA061 · Mead RV 8A
Mead RV 8A · Accident: collision during takeoff/landing
From Farmington Regional Airport (FAM) to Farmington Regional Airport (FAM)
Event
- NTSB case
- CEN17LA061
- 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
Mead RV 8A
- Aircraft type
- Mead 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
- N918KS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Farmington Regional Airport (FAM), Farmington, MOTo Farmington Regional Airport (FAM), Farmington, MO
- Aircraft age
- About 12 years (built 2004)
- 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
- Takeoff
- 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
- Collision during takeoff/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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport pilot reported that all indications were normal during takeoff in the experimental amateur-built airplane. The airplane accelerated normally and became airborne, then the left wing raised, which the pilot assumed was the result of the left crosswind conditions. He applied a correction to the left; however, he overcorrected and the airplane entered a steep left bank. After regaining control of the airplane, the pilot noted that the airplane was about 60° from the runway heading, and he thought that the airplane was too low to correct back to runway heading. The pilot reduced power to land on airport property; however, the terrain was rough and the left wing sustained substantial damage during the landing. The pilot stated that there were no mechanical malfunctions or anomalies that would have precluded normal operation of the airplane.
Probable cause
The pilot's failure to maintain airplane control during takeoff in crosswind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA061
- Event ID
- 20161227X80237
- Case number
- CEN17LA061
- 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: 0c2feae76b36c4648e08cfba78cd099230f333bafbdf4df6f08eb3d57d8f2763; retrieved 2026-09-16T04:54:55.405Z.