Skip to content

GAA16CA048

2015-11-07 · Mesa, Arizona, United States · None · 1 aircraft · Status: Completed

Airport FFZ

Current FAA registration · N1107G

Make / Model
CESSNA 172S
Year of manufacture
2006 · 9 years old at event
Engine
LYCOMING IO-360-L2A (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20060918
ADS-B equipped
Yes — Mode-S A02F87

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's failure to maintain pitch control during landing, resulting in a porpoise, and firewall damage.

Factual narrative

A certificated flight instructor, who witnessed the landing sequence, reported that upon touchdown, the airplane porpoised three times. He reported that the pilot aborted the landing, the airplane climbed to approximately 50 feet above ground level, and then the airplane landed on the remaining runway without further incident. The Federal Aviation Administration aviation safety inspector, who spoke with the pilot, stated that the pilot reported that the airplane was "not stable" during the approach and that he should have aborted the landing. The pilot also reported that the crosswind condition "complicated his final approach," which was "too high." The airplane landed hard, resulting in substantial damage to the firewall. The pilot did not make a statement to the National Transportation Safety Board (NTSB) investigator-in-charge during a telephone interview. The pilot did submit a NTSB Form 6120.1 Pilot/Operator Aircraft Accident/Incident Report, but with no narrative of the accident. The pilot did not report any pre-impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. A flight instructor, who witnessed the landing sequence, reported that upon touchdown, the airplane porpoised three times. He reported that the pilot aborted the landing, the airplane climbed to approximately 50 feet above ground level, and then the airplane landed on the remaining runway without further incident. The Federal Aviation Administration aviation safety inspector, who spoke with the pilot, stated that the pilot reported that the airplane was "not stable" during the approach and that he should have aborted the landing. The pilot also reported that the crosswind condition "complicated his final approach," which was "too high." The airplane landed hard, resulting in substantial damage to the firewall. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

FAA avdata. C = Cause, F = Factor.

  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Pitch control-Not attained/maintained - C

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

Related research

Matched on aircraft type. All research papers