CEN22LA022 · Cessna 152
Skypark Cessna 152 · Accident: loss of control in flight on approach
From Weltzien Skypark Airport (15G) to an unrecorded destination
Event
- NTSB case
- CEN22LA022
- 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 152
- Aircraft type
- Cessna 152
- 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
- N94400
- Operator
- Skypark
- Onboard fatalities
- Unknown
- Route
- From Weltzien Skypark Airport (15G), Wadsworth, OHTo not recorded
- Aircraft age
- About 39 years (built 1982)
- 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 final
- 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 student pilot reported he was conducting a solo traffic pattern flight and was on final approach for landing from his first traffic pattern when he lost control of the airplane at 50 ft, rounded out and impacted the runway on the nose wheel. The airplane subsequently bounced and impacted the runway again collapsing the nose wheel and allowing the left wing to impact in the grass next to the runway. The airplane then skidded off the left side of the runway and came to rest in the grassy area. The airplane sustained substantial damage to the top inboard left wing. The student pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The instructor pilot reported that he and the student pilot had completed four successful landings prior to the instructor getting out of the airplane for the student pilot’s solo traffic pattern flight. He reported that the student pilot’s approach was stable, but upon landing the airplane seemed to be out of control.
Probable cause
The student pilot’s failure to maintain aircraft control during the final approach resulting in a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA022
- Event ID
- 20211028104175
- Case number
- CEN22LA022
- 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: 30aded4610f16f7bee0971fa27663841ba649fc8eb2f8ec385577bf7d2732f67; retrieved 2026-09-16T14:42:25.721Z.