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 4, 2018 · Beech 35 J35 · N533JW

Knox, IN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 4, 2018
Injury Outcomes
No injuries (4 uninjured)
Location
Knox, IN
Aircraft
Beech 35 J35 (1958)
Tail Number
N533JW
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN18LA319

The private pilot and three passengers were on a cross-country flight in a single-engine airplane. About 10 miles from the destination airport, the pilot switched to the fullest fuel tank, entered the traffic pattern, and reduced the throttle to slow the airplane. While on final approach, he advanced the throttle; however, the engine did not respond. The pilot turned the boost pump on to "emergency – high," but the engine still did not respond. Shortly after, the pilot turned the boost pump off and conducted a forced landing in a field, during which the engine was bent downward from the firewall and the fuselage sustained substantial damage. The on-site examination found sufficient fuel available in each of the wing fuel tanks. Additionally, fuel was present in the fuel lines near the engine's fuel manifold. A detailed engine examination and download of the engine monitor were conducted after airplane recovery. A review of the engine data for the day of the accident found three files. The last file corresponded to the accident flight, and the monitor indicated 30.4 gallons used. The pilot reported the fuel at last takeoff was 33 gallons. The engine examination did not find any evidence of mechanical malfunctions or failures that would have precluded normal operation. Although data from the engine monitor indicated that the airplane was very low on fuel, the on-site examination showed various levels of fuel available in the fuel tanks. Thus, it is likely that the airplane's engine monitor did not accurately reflect the airplane's correct fuel state. Based on the available evidence, the reason for the total loss of engine power could not be determined.

NTSB Probable Cause

The total loss of engine power for reasons that could not be determined based on the available evidence.

Full Narrative

On August 4, 2018, about 1500 central daylight time, a Beech 35 airplane, N533JW, impacted terrain after a loss of engine power during an approach to the Starke County Airport (OXI), Knox, Indiana. The pilot and three passengers were not injured, and the airplane was substantially damaged during the accident. The airplane was registered to and operated by a private individual, under the provisions of 14 Code of Federal Regulations Part 91 as personal flight. Visual meteorological conditions prevailed at the time. The flight originated from Lacon, Illinois, about 1400. The pilot reported he leveled off at 5,500 ft for the cross-country flight, and selected the left main fuel tank, which indicated just under ½ tank. About 10 miles from the destination airport, he switched to the fullest fuel tank. He then entered the traffic pattern and reduced the throttle to slow the airplane. While on final approach, to arrest a decent, he advanced the throttle; however, the engine did not respond. The pilot turned the boost pump on to "emergency – high" and the engine still did not respond. The pilot then reduced the throttle to idle and slowly advanced the throttle, again the engine did not respond, so he turned the boost pump off and prepared for the forced landing. The responding Federal Aviation Administration (FAA) inspector found the airplane had impacted a cornfield and terrain just short of the runway. The airplane's engine was bent downward from the firewall and fuselage sustained substantial damage during the accident. The inspector opened the fuel tanks, and noted fuel was available at various levels. The inspector also disconnected the lines near the fuel manifold, and fuel was present in the lines. The airplane was recovered to a secure facility and examined by a National Transportation Safety Board (NTSB) investigator and a technical representative from the engine manufacturer. Data from the airplane's engine monitor was downloaded. A review of the data found for August 4th, found 3 files. The first file contained information for a 1.85 hr flight, starting at 1810 UTC. The data block field for fuel used started with 0.0 and ended with 19.1 gallons used. The second file indicated the engine monitor was powered on for just over a minute. The third file, started at 2108 UTC and was for 0.94 hr. The last file corresponded to the accident flight, and the monitor indicated 30.4 gallons used. The pilot reported his fuel at last takeoff was 33 gallons. During the examination, the propeller shaft was rotated by hand and drivetrain continuity was confirmed through the valve train, and to the accessory section of the engine. Suction and compression were noted on all cylinders. No anomalies were found that would have prevented the engine from producing rated horsepower.

Flight

Event TypeAccident
Event Time16:00 EDT
Nearest AirportStarke County Airport (0nm)
Runway18
Runway Length4401 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech 35 J35
Tail NumberN533JW
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engine TypeReciprocating
Engine DetailsContinential · IO-470 · Reciprocating · 250

People & Injuries

Injury SummaryNo injuries (4 uninjured)
Fatal0
Serious0
Minor0
Uninjured4
Total4
Crew 1Age 62 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind270° @ 8 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point68 F
Altimeter29.78 inHg
Observation Time19:53
Weather SourceWFAC

Appendix: Source Data