WPR25LA296 · Cessna 172M
Cessna 172M · Accident: abnormal runway contact during landing
From Corvallis Municipal Airport (CVO) to an unrecorded destination
Event
- NTSB case
- WPR25LA296
- 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 172M
- 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
- N20490
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Corvallis Municipal Airport (CVO), Corvallis, ORTo not recorded
- Aircraft age
- About 52 years (built 1973)
- 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
- Abnormal runway contact
- 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
- 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 pilot reported that, during landing, the airplane bounced, and the pilot attempted to hold the airplane level to bleed off airspeed. The airplane then bounced three more times, and its pitch increased after each bounce. After the fourth bounce, the airplane ballooned, and the pilot applied back pressure to the yoke. Subsequently, the airplane’s pitch decreased rapidly, and the airplane impacted the runway surface in a nose low attitude. The airplane sustained substantial damage to the forward fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operations.
Probable cause
The pilot’s improper landing flare and subsequent improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR25LA296
- Event ID
- 20250926201731
- Case number
- WPR25LA296
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-08-19.
- API snapshot SHA-256: 92cfe74fc09fea89593b1a52e0e97d9fb8988eb9f78b3198725b8944781e05fb; retrieved 2026-09-16T20:23:29.209Z.