LAX08CA010 · Cessna 172R
AirSafety Flight Academy Cessna 172R · Accident: hard landing
From Glendale Municipal Airport (GEU) to Glendale Municipal Airport (GEU)
Event
- NTSB case
- LAX08CA010
- 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 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
- N9914F
- Operator
- AirSafety Flight Academy
- Onboard fatalities
- Unknown
- Route
- From Glendale Municipal Airport (GEU), Glendale, AZTo Glendale Municipal Airport (GEU), Glendale, 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
- Dual student › Recovery from bounced landing, improper
- Dual student › Rudder, improper use of
- Pilot in command(cfi) › Supervision, 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 instructor reported that as the airplane neared touchdown during final approach, he set the throttle to idle, leaving his hand on the throttle. The student pilot leaned forward, moving his hand, which in turn moved the throttle forward. The airplane then ballooned on the runway. The student pilot tried to correct this by applying full right rudder. The airplane descended in a 45-degree yaw angle to the right. The instructor said that he tried to correct the yaw, but he was not successful before impact with the runway. The propeller collided with the ground and the airplane skidded off the runway. The nose gear collapsed and the firewall was damaged. The winds were calm.
Probable cause
the student pilot's improper bounced landing recovery technique, improper use of the flight controls, and the instructor's inadequate supervision of the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA010
- Event ID
- 20071113X01790
- Case number
- LAX08CA010
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-10-12.
- API snapshot SHA-256: ec8b6b046fc716bdd313a8379cf3b082cf7ee9c6ce79676962e1ce70eb79340c; retrieved 2026-09-22T03:20:53.723Z.