Skip to content

GAA16CA209

2016-04-30 · Palo Alto, California, United States · None · 1 aircraft · Status: Completed

Airport PAO

Aircraft involved

Probable cause & findings

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.

Factual 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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

FAA avdata. C = Cause, F = Factor.

  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
  • C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Student/instructed pilot - C
  • C Environmental issues-Conditions/weather/phenomena-Wind-High wind-Decision related to condition - C
  • C Environmental issues-Conditions/weather/phenomena-Wind-High wind-Effect on operation - C

Verbatim from NTSB's published report. Source file NTSB_2016_GAA16CA209.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Search this event elsewhere

External sources are reported, not agency: signal that something happened, not fact about what happened.

Related research

Matched on aircraft type. All research papers