CEN14CA470 · Evektor-Aerotechnik AS SPORTSTAR
Evektor-Aerotechnik AS SPORTSTAR · Accident: abnormal runway contact on approach
From Flying Cloud Airport (FCM) to Airlake Airport (LVN)
Event
- NTSB case
- CEN14CA470
- 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
Evektor-Aerotechnik AS SPORTSTAR
- Aircraft type
- Evektor SPORTSTAR
- 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
- N821EV
- Operator
- Baar Ronald
- Onboard fatalities
- Unknown
- Route
- From Flying Cloud Airport (FCM), Minneapolis, MNTo Airlake Airport (LVN), Minneapolis, MN
- Aircraft age
- About 7 years (built 2007)
- 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 go-around
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot maneuvered the airplane to land on runway 12 at the destination airport. Wind was from 190 degrees at 11 knots gusting to 18 knots. The estimated crosswind component was between 10.5 to 17.5 knots. The pilot crabbed the airplane on a 1-2 mile straight-in approach for the runway. Prior to landing, the pilot aligned the nose of the airplane with the runway centerline and reduced power. When the airplane touched down a gust of wind lifted the right wing and lowered the left wing to the runway. As the pilot initiated a go-around the left wing contacted the ground and control of the airplane was lost. The pilot stated that the airplane then stalled and impacted the ground. The pilot reported that his flight school did not fly if the crosswind component was 10 knots or higher and as a result he did not have much experience flying in winds greater than 10 knots of crosswind.
Probable cause
The pilot's loss of control while landing with a crosswind. Contributing to the accident was the pilot lack of experience flying in similar weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA470
- Event ID
- 20140902X03227
- Case number
- CEN14CA470
- 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: b428ab18be13929c9d4395bca9fb8707f09c68ce5cfe7263170f9a7757cbf22c; retrieved 2026-09-16T01:42:24.019Z.