ERA16LA281

NTSB accident investigation · Vans RV4 · Shelbyville, KY · August 7, 2016

Accident · Serious injuriesLimited investigationFinal report
Date
August 7, 2016, 17:09 local (22:09 UTC)
Place
Shelbyville, KY
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N924WZVans RV4
Defining event
Approach: Loss of engine power (partial)
Weather
Visual (VMC) · Day
Status
Completed · report September 10, 2018
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20160807014159A
Case key
93780

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The partial loss of engine power due to carburetor icing. Contributing to the accident was the pilot’s failure to effectively use carburetor heat.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Temp/humidity/pressure: conducive to carburetor icingEnvironmental issues › Conditions/weather/phenomena · Effect on equipmentJules S Roberie RV-4: 1 caseAll aircraft: 435 casesProbable cause
Action: delayed actionPersonnel issues › Action/decision · PilotJules S Roberie RV-4: 1 caseAll aircraft: 894 casesProbable cause
Ice/rain protection system: intake anti-ice, deiceAircraft › Aircraft systems · Incorrect use/operationJules S Roberie RV-4: 1 caseAll aircraft: 108 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

Following several uneventful touch-and-go-landings, the private pilot refueled the airplane and returned to his home airport. During the approach for landing, the pilot saw wildlife on the runway, so he conducted a low pass over the runway; however, when he applied full throttle to climb, the engine did not produce full power. The pilot continued to climb the airplane with the intention of staying in the airport traffic pattern and making a full stop landing. Continuing through the pattern, he applied carburetor heat, then turned it off again. The airplane began sinking fast on final approach and impacted terrain short of the runway, resulting in substantial damage. A postaccident examination of the engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The atmospheric conditions at the time of the accident were conducive to serious carburetor icing at glide power settings. After observing the loss of engine power during the climb out from the low approach, the pilot applied carburetor heat briefly, then, due to low altitude and sink rate, he turned off the carburetor heat to reduce the loss of power. It is likely that the carburetor accumulated ice during the low approach, which resulted in the observed partial loss of engine power, and the brief application of carburetor heat was insufficient to clear the ice from the carburetor and restore engine power.

Factual narrative

On August 7, 2016, about 1709 central daylight time, an experimental amateur-built Vans RV-4, N924WZ airplane, was substantially damaged during a forced landing while on approach to Miles Field Airport (3KY9), Shelbyville, Kentucky. The private pilot owner was seriously injured. No flight plan was filed for the personal flight that originated at the Capital City Airport (FFT), Frankfort, Kentucky. Visual meteorological conditions prevailed for the local flight conducted under the provisions of 14 Code of Federal Regulations Part 91.According to a Federal Aviation Administration (FAA) inspector, the pilot completed a series of touch-and-go landings at 3KY9, flew to FFT to refuel, and was returning to 3KY9 at the time of the accident. In a statement to the FAA, the pilot reported that he observed a deer while on the final approach leg of the traffic pattern and he elected to execute a low approach. He stated the engine was "running fine" until he applied full power on climbout; then the engine only produced partial power. Because the airplane was still able to climb, the pilot elected to fly the traffic pattern and make another approach. After turning onto the base leg of the traffic pattern, he added carburetor heat and 10 degrees of flaps. After he reduced engine power on the final approach leg of the traffic pattern, the engine began "running bad" and "a little rough." The airplane began sinking too fast, the pilot added full power and turned the carburetor heat off. The engine continued to lose power and the airplane kept descending until it impacted terrain about 200 feet from the runway. The airplane's wings sustained leading edge damage, the cockpit was heavily damaged and folded open, and there was significant damage to the firewall. The airplane was equipped with a Lycoming O-320, 150-horsepower engine. Initial examination of the engine by an FAA inspector revealed that both magnetos produced spark at their respective distributor blocks and the spark plugs appeared to be new and undamaged. The fuel selector was in the "ON" position. The pilot's total flight experience could not be reconciled, but at the time of his most recent application for an FAA medical certificate on August 13, 2015, he reported 170 total hours of flight experience. The closest weather reporting facility was the about 11 miles east of the accident site. At 1653, an aviation routine weather report at FFT was reporting in part: temperature 86° F; dewpoint 57° C. An FAA carburetor icing probability chart indicated the temperature and dew point conditions were conducive to the formation of serious icing at glide power. According to the FAA Pilot's Handbook of Aeronautical Knowledge, carburetor ice occurs due to the effect of fuel vaporization and the decrease in air pressure in the carburetor's venturi, which can cause a sharp temperature decrease in the carburetor. If water vapor in the air condenses when the carburetor temperature is at or below freezing, ice may formon the internal surfaces of the carburetor, including the throttle valve. This then restricts the flow of the fuel/air mixture and reduces engine power. Generally, the first indication of carburetor icing in an airplane with a fixed-pitch propeller is a decrease in engine rpm, which may be followed by engine roughness. Under certain conditions, carburetor ice can build unnoticed until power is added. The handbook further described that carburetor heat is an anti-icing system that preheats the air before it reaches the carburetor, and is intended to keep the fuel/air mixture above the freezing temperature to prevent the formation of carburetor ice. Carburetor heat can be used to melt ice that has already formed in the carburetor if the accumulation is not too great, but using carburetor heat as a preventative measure is the better option.

Aircraft

Registration
N924WZ
Reported as
Vans RV4
Category
Airplane, amateur-built
Serial number
3218
Built
2016
Engine
Lycoming O-320, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Departed
FFT · Frankfort, KY
Destination
3KY9 · Shelbyville, KY
Airport
3KY9 · Miles Field, runway 05, 3,000 × 75 ft, grass/turf

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
59
Injuries
Serious
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Flight hours
170 total

Weather

Conditions
Visual (VMC) · Day
Wind
90° at 6 knots
Visibility
10 statute miles
Lowest ceiling
6,000 ft broken
Temperature
86 °F, dew point 59 °F
Altimeter
29.95 inHg
Observed at
FFT, 11 nm away

Docket · 3

The files NTSB released with the investigation on July 16, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 716 KB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.