GAA19CA287 · Jihlavan Airplanes SRO KP5
Jihlavan Airplanes SRO KP5 · Accident: aerodynamic stall/spin during takeoff
From Chester Airport (SNC) to Chester Airport (SNC)
Event
- NTSB case
- GAA19CA287
- 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
Jihlavan Airplanes SRO KP5
- Aircraft type
- Jihlavan KP5
- 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
- N235KP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chester Airport (SNC), Chester, CTTo Chester Airport (SNC), Chester, CT
- Aircraft age
- About 14 years (built 2005)
- 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
- Aerodynamic stall/spin
- 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
The pilot receiving instruction reported that, during takeoff from the grass adjacent to a paved runway, after adding full power, he held the stick back during acceleration. He added that the airplane did not accelerate "much above the red line (40 mph)" and that he felt a "bump." The airplane then bounced and veered right. The flight instructor reported that, during the takeoff, the angle of attack was "higher than normal" and that the airplane aerodynamically stalled 3 ft above ground level. The right wing dropped, the airplane yawed right, and he and the pilot attempted to recover with nose-down, left-rudder, and left-aileron inputs. The airplane landed sideways, the landing gear collapsed, and the propeller struck the ground. The airplane sustained substantial damage to the right wing. The pilot and instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to maintain the proper airspeed and his exceedance of the airplane's critical angle of attack during takeoff, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA19CA287
- Event ID
- 20190525X64158
- Case number
- GAA19CA287
- 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: e1388602257711973ad62310b5905c2c69ead976788b7356c9a2d94b630de59c; retrieved 2026-09-16T09:03:30.260Z.