WPR25LA243 · Cessna 172N
Red Eagle Aviation Cessna 172N · Accident: abnormal runway contact during landing
From Kalispell City Airport (S27) to an unrecorded destination
Event
- NTSB case
- WPR25LA243
- 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 172N
- 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
- N734SW
- Operator
- Red Eagle Aviation
- Onboard fatalities
- Unknown
- Route
- From Kalispell City Airport (S27), Kalispell, MTTo not recorded
- Aircraft age
- About 48 years (built 1977)
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The purpose of the flight was for the student pilot to perform a solo cross-country and land at the accident airport. The student pilot stated that following a stabilized approach, he did not properly maneuver the airplane into a flare. The airplane touched down hard on the runway surface and bounced back into the air. The airplane then touched down again and then bounced multiple times, porpoising along the runway. As a result of the impact, the airplane incurred damage to the firewall. The student pilot noted that he failed to add engine power to correct the self-induced oscillation. He stated that there were no pre-impact mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The student pilot's inadequate landing flare and recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR25LA243
- Event ID
- 20250808200741
- Case number
- WPR25LA243
- 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: bcd29ae6cce87a849ca0307641fec6da8386e025a57debabfc2d6b9c12014b37; retrieved 2026-09-16T20:11:33.501Z.