CEN14CA499 · Evektor-Aerotechnik AS SPORTSTAR
Evektor-Aerotechnik AS SPORTSTAR · Accident: loss of control in flight on approach
From Cushing Field Ltd Airport (0C8) to Cushing Field Ltd Airport (0C8)
Event
- NTSB case
- CEN14CA499
- 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
- N800NW
- Operator
- Ryan Boston
- Onboard fatalities
- Unknown
- Route
- From Cushing Field Ltd Airport (0C8), Newark, ILTo Cushing Field Ltd Airport (0C8), Newark, IL
- 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 pattern base
- 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
- Loss of control in flight
- 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 flight instructor reported that the student pilot made a normal takeoff from a turf runway. While the student pilot was flying the departure leg, the flight instructor initiated a simulated engine failure. During the student pilot's approach, the flight instructor noticed the airspeed deteriorate. The flight instructor stated that when he attempted to assume control of the airplane, the student pilot did not release the controls. A sink rate developed and the airplane struck a power line prior to the runway. During ground impact, both wings and fuselage were substantially damaged. The student pilot did not recall the accident sequence of events due to his injuries.
Probable cause
The student pilot did not maintain proper airspeed during the simulated emergency landing and failed to relinquish control to the flight instructor when the flight instructor attempted to intervene, which resulted in the loss of control. Contributing was the flight instructor's failure to properly monitor the student pilot, and the poor communication between the flight instructor and student pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA499
- Event ID
- 20140918X31614
- Case number
- CEN14CA499
- 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: ea350d8ea1fe1478f2fc22fef2db762fc65c0e8856d2fe2df716c0387b844559; retrieved 2026-09-16T01:46:07.868Z.