GAA15CA063 · Cessna 172P P
Glendale Community College Cessna 172P P · Accident: hard landing
From Whiteman Airport (WHP) to Whiteman Airport (WHP)
Event
- NTSB case
- GAA15CA063
- 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
- 0
- 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 172P P
- 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
- N65813
- Operator
- Glendale Community College
- Onboard fatalities
- Unknown
- Route
- From Whiteman Airport (WHP), Los Angeles, CATo Whiteman Airport (WHP), Los Angeles, CA
- Aircraft age
- About 32 years (built 1983)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On the student pilot's first supervised solo flight; she reported that on her first landing the airplane porpoised three times and then came to a full stop. She taxied back to the departure end of the runway for a second takeoff. On her second landing the airplane porpoised four times, she taxied back to her flight school without further incident. As a result of the hard landing and subsequent porpoise, the flight instructor conducted a postaccident examination of the engine and airframe, and substantial damage to the firewall was discovered.
The student pilot reported there were no pre-impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Probable cause
The student pilot's failure to maintain attitude control during the landing flare, resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA063
- Event ID
- 20150507X15611
- Case number
- GAA15CA063
- 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. 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: 72715bbad26d49e5ed5b666de7b5cb0a0ce9f13d6b5b2f67942195c1c6bee39e; retrieved 2026-09-16T02:17:47.595Z.