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 19, 2023 · Aero Commander 112 · N1143J

Saluda, SC

Overview

Report Status
Probable Cause
Event Type
Accident
Date
November 19, 2023
Injury Outcomes
2 injuries (2 minor injuries)
Location
Saluda, SC
Aircraft
Aero Commander 112 (1974)
Tail Number
N1143J
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA24LA044

The pilot and the flight instructor planned a flight itinerary that included multiple stops with the aim of the pilot receiving 7 hours of training in the airplane. Prior to the accident, the flight instructor learned that the pilot had not performed go-arounds or touch-and-go landings in the airplane make and model. Upon flying the airplane into the accident airport, the favorable weather conditions and lack of air traffic led them to decide to conduct the training in the traffic pattern there. The first landing was made by the pilot to a full stop with taxi back. The second landing, which was a touch-and-go, was performed by the flight instructor. The third, followed by the fourth and final landing was performed by the pilot. During the fourth landing, with the wing flaps fully extended, the pilot lost directional control of the airplane and attempted to abort the landing as the airplane veered to the left (a right crosswind prevailed at that time). The pilot tried to correct back toward to the runway centerline, but the airplane went off the left side of the runway. The airplane then touched down in the grass, traveled down an embankment, nosed over, and came to rest inverted. The airframe was substantially damaged during the accident sequence. The pilot reported 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 maintain directional control of the airplane during an aborted landing in crosswind conditions. Contributing to the accident was the flight instructor’s inadequate remedial action.

Full Narrative

The pilot and the flight instructor planned a flight itinerary that included multiple stops with the aim of the pilot receiving 7 hours of training in the airplane. Prior to the accident, the flight instructor learned that the pilot had not performed go-arounds or touch-and-go landings in the airplane make and model. Upon flying the airplane into the accident airport, the favorable weather conditions and lack of air traffic led them to decide to conduct the training in the traffic pattern there. The first landing was made by the pilot to a full stop with taxi back. The second landing, which was a touch-and-go, was performed by the flight instructor. The third, followed by the fourth and final landing was performed by the pilot. During the fourth landing, with the wing flaps fully extended, the pilot lost directional control of the airplane and attempted to abort the landing as the airplane veered to the left (a right crosswind prevailed at that time). The pilot tried to correct back toward to the runway centerline, but the airplane went off the left side of the runway. The airplane then touched down in the grass, traveled down an embankment, nosed over, and came to rest inverted. The airframe was substantially damaged during the accident sequence. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.

Flight

Event TypeAccident
Event Time11:26 EST
Nearest AirportSaluda County Airport (0nm WNW)
Runway1
Runway Length3189 ft
Runway Width60 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftAero Commander 112
Tail NumberN1143J
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360-C1D6 · Reciprocating · 200
Seats4

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 61 · Third Class · Minor
Crew 2Age 51 · Second Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind50° @ 9 kt
Visibility10 sm
CeilingOvercast 2100 ft
Temperature / Dew Point59 F / 36 F
Altimeter30.03 inHg
Observation Time11:35
Weather SourceWFAC

Appendix: Source Data