FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13LA579 · Beech 58P

16 Jun 2013 · St Paul, MN, United States

Beech 58P · Accident during landing

From Duluth International Airport (DLH) to Saint Paul Downtown Holman Field (STP)

Report a problem

Event

NTSB case
CEN13LA579
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Beech 58P

Aircraft type
Beechcraft 58
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N5958P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Duluth International Airport (DLH), Duluth, MNTo Saint Paul Downtown Holman Field (STP), St Paul, MN
Aircraft age
About 34 years (built 1979)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · aborted after touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that, after touching down, he realized that the airplane had landed long, so he chose to reject the landing. He then heard a "thump" during the initial climb, so he returned to the airport and landed the airplane. A postaccident examination revealed that the right side of the lower fuselage and cockpit floor had been damaged beneath the copilot/right-front passenger seat. Damage was also observed to an airport sign off the runway's right side. The pilot reported no preaccident failures or malfunctions with the airplane that would have precluded normal operation and that no flight control issues occurred during the go-around after the impact with the airport sign.

Probable cause

The pilot's failure to maintain directional control during a rejected landing, which resulted in a collision with an airport sign off the right side of the runway during the transition to the initial climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13LA579
Event ID
20140305X13315
Case number
CEN13LA579
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: fefe7e1490f83f4a812a250db4e627e03ac53a8317349eb2cf5315a1c8f84af6; retrieved 2026-09-15T23:22:23.077Z.