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 27, 2024 · Beech 58 · N458K

Florence, SC

Overview

Report Status
Probable Cause
Event Type
Accident
Date
December 27, 2024
Injury Outcomes
No injuries (6 uninjured)
Location
Florence, SC
Aircraft
Beech 58 (1974)
Tail Number
N458K
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA25LA094

The pilot was on a return, cross country flight to his home airport in instrument meteorological conditions. The pilot reported that he first performed a non-precision approach into the airport, where he reported that the landing gear extended normally. After performing a missed approach, the pilot retracted the landing gear and he then performed a precision approach in the opposite direction. The pilot reported that he put the landing gear switch in the down position, but that the landing gear did not extend. The pilot elected to continue the approach without troubleshooting, extending the gear manually, or referring to the emergency checklist. The pilot subsequently landed the airplane on the runway with the landing gear retracted, which resulted in substantial damage to the fuselage. After the accident, the pilot performed an operational check and troubleshooting of the landing gear without authorization. The pilot reported that the landing gear again failed to extend, but would retract during his testing. The pilot also reported that the manual landing gear extension system operated normally. During the testing, the pilot said he found an “open circuit of the gear relay due to moisture or foreign debris.” After troubleshooting, the pilot reported that the landing gear started to operate normally. After the pilot had performed the unauthorized troubleshooting, a Federal Aviation Administration inspector examined the landing gear system, and performed a functional test, during which he found that it operated normally.

NTSB Probable Cause

The pilot’s failure to follow the emergency procedures and extend the landing gear manually after the landing gear did not initially extend normally.

Full Narrative

The pilot was on a return, cross country flight to his home airport in instrument meteorological conditions. The pilot reported that he first performed a non-precision approach into the airport, where he reported that the landing gear extended normally. After performing a missed approach, the pilot retracted the landing gear and he then performed a precision approach in the opposite direction. The pilot reported that he put the landing gear switch in the down position, but that the landing gear did not extend. The pilot elected to continue the approach without troubleshooting, extending the gear manually, or referring to the emergency checklist. The pilot subsequently landed the airplane on the runway with the landing gear retracted, which resulted in substantial damage to the fuselage. After the accident, the pilot performed an operational check and troubleshooting of the landing gear without authorization. The pilot reported that the landing gear again failed to extend, but would retract during his testing. The pilot also reported that the manual landing gear extension system operated normally. During the testing, the pilot said he found an “open circuit of the gear relay due to moisture or foreign debris.” After troubleshooting, the pilot reported that the landing gear started to operate normally. After the pilot had performed the unauthorized troubleshooting, a Federal Aviation Administration inspector examined the landing gear system, and performed a functional test, during which he found that it operated normally.

Flight

Event TypeAccident
Event Time18:30 EST
Nearest AirportFlorence Rgnl (0nm ENE)
Runway09
Runway Length6502 ft
Runway Width150 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech 58
Tail NumberN458K
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsContinental Motors · IO-520-C7B · Reciprocating · 285 | Continental Motors · IO-520-C7B · Reciprocating · 285
Seats6

People & Injuries

Injury SummaryNo injuries (6 uninjured)
Fatal0
Serious0
Minor0
Uninjured6
Total6
Crew 1None
Crew 2Age 74 · Basc · None
Crew 3None
Crew 4None

Conditions

ConditionsIMC
LightNight
Wind30° @ 7 kt
Visibility2 sm
CeilingOvercast 300 ft
Temperature / Dew Point48 F / 46 F
Altimeter30.28 inHg
Observation Time18:42
Weather SourceWFAC

Appendix: Source Data