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

January 29, 2025 · Cessna 172 S · N1159K

Kennesaw, GA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
January 29, 2025
Injury Outcomes
No injuries (2 uninjured)
Location
Kennesaw, GA
Aircraft
Cessna 172 S (2006)
Tail Number
N1159K
Operator
Cavu Aero
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA25LA118

According to the flight instructor, the student pilot had previously completed three-night landings to a full stop and taxi back during the dual instructional flight. On the fourth attempt, the instructor elected to simulate a loss of engine power. While on final approach, the student pilot aligned the airplane with the runway centerline, and the flight instructor thought that the airplane would be able to reach the runway threshold. As the airplane approached the runway, the instructor described that the airplane was in a “flat position” and struck the ground, short of the runway. The nose landing gear was displaced upwards and aft which resulted in substantial damage to the airplane’s lower firewall. The flight instructor reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The student pilot and instructor stated that they believed that the runway end identifier lights were not operating during their flight and that only the two outer left and right green lights were illuminated for the entirety of the flight, including the preceding three landings, which factored into their depth perception for touchdown. During correspondence with the student pilot following the accident, he provided an annotated aerial image where he circled the lights he believed to be inoperative at the time of the accident. According to the airport manager, the lights referenced by the student, which appeared to be the runway end and edge lighting, were operational at the time of the accident.

NTSB Probable Cause

The student pilot’s failure to maintain an appropriate glide path and the flight instructor’s inadequate monitoring of the landing approach, which resulted in the airplane contacting the ground short of the runway.

Full Narrative

According to the flight instructor, the student pilot had previously completed three-night landings to a full stop and taxi back during the dual instructional flight. On the fourth attempt, the instructor elected to simulate a loss of engine power. While on final approach, the student pilot aligned the airplane with the runway centerline, and the flight instructor thought that the airplane would be able to reach the runway threshold. As the airplane approached the runway, the instructor described that the airplane was in a “flat position” and struck the ground, short of the runway. The nose landing gear was displaced upwards and aft which resulted in substantial damage to the airplane’s lower firewall. The flight instructor reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The student pilot and instructor stated that they believed that the runway end identifier lights were not operating during their flight and that only the two outer left and right green lights were illuminated for the entirety of the flight, including the preceding three landings, which factored into their depth perception for touchdown. During correspondence with the student pilot following the accident, he provided an annotated aerial image where he circled the lights he believed to be inoperative at the time of the accident. According to the airport manager, the lights referenced by the student, which appeared to be the runway end and edge lighting, were operational at the time of the accident.

Flight

Event TypeAccident
Event Time21:05 EST
Nearest AirportCobb County Intl/Mccollum Fld (0nm E)
Runway27
Runway Length6295 ft
Runway Width100 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 S
Tail NumberN1159K
Aircraft CategoryAir
DamageSubstantial
OperatorCavu Aero
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming Engines · IO-360-L2A · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 28 · First Class · None
Crew 2Age 66 · First Class · None

Conditions

ConditionsVMC
LightNight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point45 F / 27 F
Altimeter30.03 inHg
Observation Time18:49
Weather SourceWFAC

Appendix: Source Data