N734AV accident

NTSB GAA16CA496 · 2016-08-30 · Delta, UT · near DTA

Docket — crew, injuries and powerplant

Summary

According to the student pilot, following the first leg of his solo cross-country flight, he entered the traffic pattern to land on runway 17 "because other traffic was using runway 17 even though winds were 050° at 3 knots." He reported that, as the airplane approached the runway, the airspeed was too high, and the airplane landed hard on the nosewheel and porpoised. He conceded, "I knew it was a hard landing, but did not hear the prop strike occur." The student pilot departed the airport and accomplished two approaches and a landing at a third airport before returning to his home airport where he accomplished two approaches, a landing, and then taxied to parking. The student pilot reported that he could have prevented the accident by performing a go-around when he realized that his approach speed was too high. The airplane sustained substantial damage to the firewall. The student pilot reported that there were no mechanical malfunctions or anomalies with the engine or airframe that would have prevented normal operation.

Full narrative

According to the student pilot, following the first leg of his solo cross-country flight, he entered the traffic pattern to land on runway 17; "because other traffic was using runway 17 even though winds were 050° at 3 knots".

He reported that as the airplane approached the runway, the airspeed was too high, and the airplane landed hard on the nose wheel and porpoised. He conceded, "I knew it was a hard landing, but did not hear the prop strike occur."

The student pilot departed the airport, and accomplished two approaches and a landing at a third airport, before returning to his home airport where he accomplished two approaches, a landing, and then taxied to parking.

The student pilot reported that he could have prevented the accident by performing a go around when he realized that his approach speed was too high. The airplane sustained substantial damage to the firewall.

The student pilot reported that there were no mechanical malfunctions or anomalies with the engine or airframe prior to the landing that would have prevented normal flight operation.

Probable cause

The student pilot’s improper landing flare, which resulted in a hard, porpoised landing. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
50
Wind speed (kt)
3
Temperature (F)
55
Nearest airport
DELTA MUNI
Distance from field
0.0
Airport elevation
4759

Aircraft

RegistrationMakeModelDamageFAR part
N734AV — — SUBS 091

Sequence of events

#OccurrencePhase
1 Landing-flare/touchdown Hard landing defining Cruise
2 Landing-flare/touchdown Attempted remediation/recovery Cruise
3 Landing-flare/touchdown Abnormal runway contact Cruise

Findings

Finding
Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot cause
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained cause
Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Effect on equipment factor