LAX07CA171 · Cessna 172S
Embry-Riddle Aeronautical University Cessna 172S · Accident: hard landing
From Prescott Regional Airport - Ernest A. Love Field (PRC) to Payson Airport (PAN)
Event
- NTSB case
- LAX07CA171
- 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
Cessna 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
- N533ER
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Payson Airport (PAN), Payson, AZ
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Pilot in command › Airspeed(vso), excessive
- Pilot in command › Flare, misjudged
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane landed hard, bouncing multiple times before coming to rest on an adjacent taxiway. In an attempt to allow excessive airspeed to decay, the pilot elected to land 1,700 feet beyond the threshold. The airplane contacted the runway with the nose wheel and the propeller striking first. The airplane then bounced, and landed hard approximately 95 feet further down the runway, again sustaining propeller strikes. It became airborne for another 125 feet before striking the runway and departing to the left, passing through turf and coming to rest on the adjacent taxiway. The operator reported no preimpact mechanical malfunctions or failures with the airplane.
Probable cause
The pilot's inadequate in-flight planning/decision, excessive airspeed on final approach, and failure to execute a go-around resulting in a misjudged flare and hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA171
- Event ID
- 20070524X00625
- Case number
- LAX07CA171
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 7c8074f13378591ac8663b56afbf1627625fe80240adf4afba415fc1a726638d; retrieved 2026-09-22T03:50:58.438Z.