CEN17LA144 · Cirrus Design Corp SR20
Trustees of Purdue University Cirrus Design Corp SR20 · Accident: loss of control in flight during landing
From Purdue University Airport (LAF) to Fort Wayne International Airport (FWA)
Event
- NTSB case
- CEN17LA144
- 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
Cirrus Design Corp SR20
- Aircraft type
- Cirrus SR20
- 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
- N580PU
- Operator
- Trustees of Purdue University
- Onboard fatalities
- Unknown
- Route
- From Purdue University Airport (LAF), Lafayette, INTo Fort Wayne International Airport (FWA), Fort Wayne, IN
- Aircraft age
- About 7 years (built 2010)
- 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
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that the private pilot receiving instruction performed the approach and crosswind landing. During the landing flare, the airplane suddenly and severely rolled to the left. He thought that he heard the left wing scrape the runway. The instructor took control of the airplane and simultaneously added full engine power and full right aileron to attempt a go-around. He stated that the full right aileron input did little to correct the airplane's attitude, and the wind continued to push the airplane to the left of the runway. As the airplane's airspeed increased, the instructor was able to level the wings and started to pitch the airplane up for the go-around. The instructor noted that he did not feel as if he had the airplane "under control" during the go-around. When the airplane was about 25-50 ft above the ground, it rolled right and pitched down to ground contact.
Examination of the airplane, flight control system, and engine did not reveal any preimpact anomalies that would have precluded normal operation. Damage to the left wing was consistent with runway contact.
The data recovered from the airplane's Recoverable Data Module (RDM) showed that, seconds before impact during the go-around, the airplane was banked 17° left and pitched 13° nose up at an airspeed of 55 knots. The pilot's operating handbook listed the airplane's aerodynamic stall speed as 59 knots when loaded to full gross weight with the most rearward center of gravity. The RDM data also indicated that the airplane's aerodynamic stall warning activated about 6 seconds before the impact.
At the time of the accident, there was an approximate 50° right crosswind at 20 knots with gusts to 26 knots; these conditions exceeded the flight school's established crosswind limitations.
Based on the available information, it is likely that the pilot receiving instruction failed to maintain control of the airplane during the crosswind landing, which led to the left wing contacting the runway. When the flight instructor assumed control of the airplane, he failed to attain appropriate airspeed and allowed the airplane to exceed its critical angle of attack during the attempted go-around, which resulted in an aerodynamic stall and incipient spin.
Probable cause
The pilot receiving instruction’s failure to maintain airplane control during a crosswind landing in high gusting winds, and the flight instructor’s failure to maintain a proper airspeed and angle of attack during the go-around, which resulted in an aerodynamic stall/spin. Contributing to the accident was the flight instructor’s decision to conduct a flight in crosswind conditions that exceeded flight school limitations.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA144
- Event ID
- 20170403X05402
- Case number
- CEN17LA144
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-03-30.
- API snapshot SHA-256: b7f7ec27b723c1b4ff42634a6b4655b6c1f63aaf7daa1404af0276a070d88edb; retrieved 2026-09-16T05:08:13.017Z.