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

November 18, 2023 · Flight Design Gmbh CTLS · N924RD

Hungry Horse, MT

Overview

Report Status
Probable Cause
Event Type
Accident
Date
November 18, 2023
Injury Outcomes
2 injuries (2 minor injuries)
Location
Hungry Horse, MT
Aircraft
Flight Design Gmbh CTLS (2016)
Tail Number
N924RD
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
WPR24LA048

About four hours into the repositioning flight, and about six miles from his intended destination, the pilot contacted the tower controller and was informed that the airport was under instrument flight rules (IFR) conditions, and that he was not cleared to land. The pilot made the decision to maneuver to the southeast to ascertain whether they should return to their home airport or land at a nearby airport and wait for the weather to clear. Shortly after departing the area enroute to an alternate airport, the airplane lost engine power. The pilot promptly attempted to restart the engine; however, his efforts were unsuccessful. The pilot subsequently executed a forced landing into a lake resulting in substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He reported that there was no engine roughness or warnings before the engine quit, and it sounded as if the airplane ran out of fuel. He reported that he departed with 26.1 gallons of fuel and, according to the inflight computer, had about 5.72 gallons of remaining fuel when they arrived at the destination airport. In the recommendation section of the NTSB Accident/Incident Reporting Form 6120.1, the pilot listed ways that the accident could have been prevented, to include not relying on fuel management systems.

NTSB Probable Cause

The pilot's inadequate fuel planning and improper in-flight decision-making, which resulted in a total loss of engine power due to fuel exhaustion.

Full Narrative

About four hours into the repositioning flight, and about six miles from his intended destination, the pilot contacted the tower controller and was informed that the airport was under instrument flight rules (IFR) conditions, and that he was not cleared to land. The pilot made the decision to maneuver to the southeast to ascertain whether they should return to their home airport or land at a nearby airport and wait for the weather to clear. Shortly after departing the area enroute to an alternate airport, the airplane lost engine power. The pilot promptly attempted to restart the engine; however, his efforts were unsuccessful. The pilot subsequently executed a forced landing into a lake resulting in substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He reported that there was no engine roughness or warnings before the engine quit, and it sounded as if the airplane ran out of fuel. He reported that he departed with 26.1 gallons of fuel and, according to the inflight computer, had about 5.72 gallons of remaining fuel when they arrived at the destination airport. In the recommendation section of the NTSB Accident/Incident Reporting Form 6120.1, the pilot listed ways that the accident could have been prevented, to include not relying on fuel management systems.

Flight

Event TypeAccident
Event Time12:25 MST
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftFlight Design Gmbh CTLS
Tail NumberN924RD
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsRotax · 912ULS · Reciprocating · 100
Seats2

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 59 · Sprt · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingOvercast 1200 ft
Temperature / Dew Point30 F / 28 F
Altimeter29.99 inHg
Observation Time11:28
Weather SourcePILO

Appendix: Source Data