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

December 30, 2025 · Cirrus Design SR20 · N506SR

Louisburg, NC

Overview

Report Status
Probable Cause
Event Type
Accident
Date
December 30, 2025
Injury Outcomes
No injuries (1 uninjured)
Location
Louisburg, NC
Aircraft
Cirrus Design SR20 (2006)
Tail Number
N506SR
Operator
Mcknight Aviation
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA26LA081

The pilot reported that the purpose of this flight was to perform closed-traffic pattern operations at the departure airport. Shortly after departure, the pilot noticed increased wind on the downwind leg and during the turn to final approach. Once on final approach, he initially flew at an indicated airspeed of 65 knots. The pilot then accelerated the airplane to 80 knots “to maintain control” and because “final approach was longer than usual, and the PAPIs [precision approach path indicators] indicated I was low.” He crossed the threshold left of the runway centerline, then at 15 to 20 ft above the runway, the pilot reduced engine power to idle. At the same time, he encountered a gust of wind and the airplane yawed to the left. The pilot attempted to perform a go-around, but touched down with the airplane’s nose pointed 20° to 25° left of the runway heading. He then reduced the engine power to idle and applied right brake to keep the airplane on the runway. The airplane continued to the left, departed the runway, and struck a lighting assembly for the precision approach path indicator. The airplane passed through an area of grass and impacted an embankment east of the runway. During the runway excursion, the airplane sustained substantial damage to the left wing. The pilot stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

NTSB Probable Cause

The pilot’s failure to compensate for gusting crosswind conditions and subsequent loss of directional control following an aborted go-around attempt, which resulted in a runway excursion.

Full Narrative

The pilot reported that the purpose of this flight was to perform closed-traffic pattern operations at the departure airport. Shortly after departure, the pilot noticed increased wind on the downwind leg and during the turn to final approach. Once on final approach, he initially flew at an indicated airspeed of 65 knots. The pilot then accelerated the airplane to 80 knots “to maintain control” and because “final approach was longer than usual, and the PAPIs [precision approach path indicators] indicated I was low.” He crossed the threshold left of the runway centerline, then at 15 to 20 ft above the runway, the pilot reduced engine power to idle. At the same time, he encountered a gust of wind and the airplane yawed to the left. The pilot attempted to perform a go-around, but touched down with the airplane’s nose pointed 20° to 25° left of the runway heading. He then reduced the engine power to idle and applied right brake to keep the airplane on the runway. The airplane continued to the left, departed the runway, and struck a lighting assembly for the precision approach path indicator. The airplane passed through an area of grass and impacted an embankment east of the runway. During the runway excursion, the airplane sustained substantial damage to the left wing. The pilot stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Flight

Event TypeAccident
Event Time09:30 EST
Nearest AirportTriangle North Exec (0nm ENE)
Runway23
Runway Length5498 ft
Runway Width100 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCirrus Design SR20
Tail NumberN506SR
Aircraft CategoryAir
DamageSubstantial
OperatorMcknight Aviation
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsTeledyne Continental Motors · IO-360-ES · Reciprocating · 210
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 48 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind280° @ 9 kt, gusting 16 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point32 F / 12 F
Altimeter30.08 inHg
Observation Time09:35
Weather SourceWFAC

Appendix: Source Data