WPR23LA357 · Cessna 172R
Iasco Flight Training Cessna 172R · Accident: loss of control in flight during takeoff
Event
- NTSB case
- WPR23LA357
- 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
- Event fatalities
- Unknown
- 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
Cessna 172R
- Aircraft type
- Cessna 172
- 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
- N17274
- Operator
- Iasco Flight Training
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 25 years (built 1998)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- 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 solo student pilot of the airplane reported that shortly after rotation, the airplane began to drift to the left of runway centerline. He tried/attempted to correct back to runway centerline, but the airplane continued to drift left. The airplane descended and landed hard. It bounced back into the air and impacted the windsock. The airplane came to rest upright inside the windsocks segmented circle.
The airplane sustained substantial damage to the right wing, aft fuselage, right horizontal stabilizer, and right elevator.
The student pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The student pilot’s loss of airplane control during takeoff, which resulted in a bounced landing and impact with the airport’s windsock.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA357
- Event ID
- 20230927193154
- Case number
- WPR23LA357
- 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, coordinates, cause areas. 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: f8f281b7214d67d0abc3a69dc66e8d6c954726dfb0f5ca559973f79937824e12; retrieved 2026-09-16T18:10:26.884Z.