N206DZ accident

NTSB ERA15CA302 · 2015-08-09 · Titusville, FL · near X21

Docket — crew, injuries and powerplant

Summary

The pilot stated that he was conducting a skydiver "jump run", and prior to letting the skydivers out the radio squelch interrupter failed causing a constant static noise. After letting the skydivers out over the airport the pilot set up the descent based on the winds acquired for the previous landing on runway 22. As he circled for landing the manifold pressure indication "dropped off" to zero. The pilot was unsure if he had a partial power loss or a gauge failure. He could not hear or feel the engine indications because of the static noise on the radio squelch and descent profile, so he committed to a power off glide path for his approach. The pilot stated that the airplanes approach speed was about 100 knots prior to the threshold for landing. The airplane touched down beyond the threshold and as the pilot applied full braking the airplane "ballooned" back into the air. The pilot attempted to stop the airplane but was unsuccessful and exited the runway, coming to rest after colliding with a ditch. An examination of the airplane revealed that the empennage and firewall was buckled during the landing sequence. The airplane was equipped with a JPI engine monitor and review of the data did not reveal a loss in engine power during the flight. The wind reported from a nearby weather station revealed that winds were 010 degrees at 6 knots at the time of the accident.

Full narrative

The pilot stated that he was conducting a skydiver "jump run", and prior to letting the skydivers out the radio squelch interrupter failed causing a constant static noise. After letting the skydivers out over the airport the pilot set up the descent based on the winds acquired for the previous landing on runway 22. As he circled for landing the manifold pressure indication "dropped off" to zero. The pilot was unsure if he had a partial power loss or a gauge failure. He could not hear or feel the engine indications because of the static noise on the radio squelch and descent profile, so he committed to a power off glide path for his approach. The pilot stated that the airplanes approach speed was about 100 knots prior to the threshold for landing. The airplane touched down beyond the threshold and as the pilot applied full braking the airplane "ballooned" back into the air. The pilot attempted to stop the airplane but was unsuccessful and exited the runway, coming to rest after colliding with a ditch.An examination of the airplane revealed that the empennage and firewall was buckled during the landing sequence. The airplane was equipped with a JPI engine monitor and review of the data did not reveal a loss in engine power during the flight.

The wind reported from a nearby weather station revealed that winds were 010 degrees at 6 knots at the time of the accident.

Probable cause

The pilot's landing with a tailwind at an excessive speed, which resulted in a runway excursion, and collision with a ditch. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
Minor
Weather conditions
Visual Meteorological Cond
Light condition
Day
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
10
Wind speed (kt)
6
Temperature (F)
86
Nearest airport
Arthur Dunn Airpark
Distance from field
0.0
Airport elevation
30

Aircraft

RegistrationMakeModelDamageFAR part
N206DZ — — SUBS 091

Sequence of events

#OccurrencePhase
1 Approach Miscellaneous/other Cruise
2 Landing-landing roll Runway excursion defining Cruise
3 Landing Collision with terr/obj (non-CFIT) Cruise

Findings

Finding
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Incorrect use/operation cause
Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot cause
Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Contributed to outcome factor