WPR25LA105 · Textron Aviation Inc 172S
Embry-Riddle Aeronautical University Textron Aviation Inc 172S · Accident: abnormal runway contact during landing
From Prescott Regional Airport - Ernest A. Love Field (PRC) to an unrecorded destination
Event
- NTSB case
- WPR25LA105
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
Textron Aviation Inc 172S
- 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
- N726ER
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo not recorded
- Aircraft age
- About 2 years (built 2023)
- 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 was practicing landing maneuvers with their flight instructor. The early part of the flight was uneventful, and they decided to work on short-field landings, all of which resulted in go-arounds. They subsequently started to practice power-off 180° landings, and on the third landing attempt, the airplane was high on the approach. The student performed a forward slip maneuver, however the airplane was traveling too fast on touchdown, and it bounced. The nose then dropped, and the nosewheel struck the runway. The flight instructor took the flight controls just as the nosewheel struck the runway again and added power to initiate a go-around. The airplane sustained substantial damage during the sequence, however the airplane performance appeared unaffected and the crew continued training unaware of the damage. It was not until after landing, when the lesson was complete, that they noticed damage to the propeller tip and forward fuselage structure. The pilot and flight instructor reported no preimpact mechanical anomalies or malfunctions that could have precluded normal operation.
Probable cause
The pilot undergoing instructions’ loss of aircraft control during landing, and the flight instructor’s failure to promptly intervene.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR25LA105
- Event ID
- 20250224199748
- Case number
- WPR25LA105
- 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: 69de9ebd275f95953aada3a9f19933c743ce17c7135549868f2d3c2a171cfa72; retrieved 2026-09-16T19:41:09.415Z.