Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

August 7, 2016 · Vans RV4 · N924WZ

Shelbyville, KY

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 7, 2016
Injury Outcomes
1 injury (1 serious injury)
Location
Shelbyville, KY
Aircraft
Vans RV4 (2016)
Tail Number
N924WZ
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
ERA16LA281

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.

NTSB 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.

Full 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 form on 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.

Flight

Event TypeAccident
Event Time18:09 EDT
Nearest AirportMiles Field (0nm SSW)
Runway05
Runway Length3000 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftVans RV4
Tail NumberN924WZ
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 150
Seats2

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 59 · Third Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind90° @ 6 kt
Visibility10 sm
CeilingBroken clouds 6000 ft
Temperature / Dew Point59
Altimeter29.95 inHg
Observation Time20:53
Weather SourceWFAC

Appendix: Source Data