GAA16CA209 · Cessna 152
Sundance Flying Club Cessna 152 · Accident: abnormal runway contact during landing
From Palo Alto Airport (PAO) to Palo Alto Airport (PAO)
Event
- NTSB case
- GAA16CA209
- 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 152
- Aircraft type
- Cessna 152
- 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
- N94565
- Operator
- Sundance Flying Club
- Onboard fatalities
- Unknown
- Route
- From Palo Alto Airport (PAO), Palo Alto, CATo Palo Alto Airport (PAO), Palo Alto, CA
- Aircraft age
- About 33 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
- 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
- Environmental issues › Conditions/weather/phenomena
- 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
According to the student pilot, during his fifth solo flight, he struggled to keep the nose straight during the landing on runway 31. He reported that during the touchdown the airplane porpoised, the nose gear collapsed, and the airplane came to rest on the runway. According to his certificated flight instructor (CFI), the student pilot was endorsed to fly the airplane in a maximum wind velocity of 8 knots. The meteorological aerodrome report (METAR) indicated that the wind at the time of the accident was 310 degrees true at 15 knots, gusting to 22 knots. According to METAR data the wind velocity exceeded the pilot's endorsed limitation at 0747 Pacific daylight time (PDT), and did not subside during the remainder of that day. The student pilot's solo flight commenced at 1259 PDT. The airplane sustained substantial damage to the firewall.
The pilot reported that there were no mechanical failures or anomalies with the airplane prior to or during the flight that would have prevented normal flight operation.
Probable cause
The student pilot's decision to takeoff in wind conditions that exceeded his certificated flight instructor's maximum wind endorsement, and the student pilot's failure to maintain pitch control during the touchdown, resulting in abnormal runway contact, and substantial damage to the firewall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA209
- Event ID
- 20160502X40721
- Case number
- GAA16CA209
- 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. 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: 9aa7de4b3e772926dffb24f3916a14a09017f7f4f8a4bd0d70a5bc5dbb5eed58; retrieved 2026-09-16T03:20:28.879Z.