CEN23LA256 · Cessna 172R
Lewis University Cessna 172R · Accident: hard landing
From Lewis University Airport (LOT) to an unrecorded destination
Event
- NTSB case
- CEN23LA256
- 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
- N674MA
- Operator
- Lewis University
- Onboard fatalities
- Unknown
- Route
- From Lewis University Airport (LOT), Romeoville, ILTo not recorded
- Aircraft age
- About 24 years (built 1999)
- 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 · flare/touchdown
- 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
- Hard landing
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot stated that during her initial solo flight, she attempted three landings. The first and second landing attempts resulted in go-arounds. During the third landing attempt, there was a “severe porpoise,” and she felt the airplane “rushing down the runway uncontrollably.” She “pushed down” to stop the porpoise because she felt that she was never going to be able to land. The airplane then impacted the runway surface and sustained substantial damage, which included damage to the fuselage. The pilot stated that the accident could have been prevented by performing a go-around instead of forcing the airplane onto the runway. There was no mechanical malfunction/failure of the airplane reported that would have precluded normal operation.
Probable cause
The student pilot’s failure to attain/maintain a proper landing flare and failure to perform a go-around that resulted in an impact with the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA256
- Event ID
- 20230623192428
- Case number
- CEN23LA256
- 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, 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: f56feb8cfb653fb0e5f2939db526163fd6a5fac7f8a08d3840c552446b66def4; retrieved 2026-09-16T17:45:34.148Z.