FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14LA324 · Beech 95 55

26 Jun 2014 · Gulf Shores, AL, United States

Beech 95 55 · Accident: abnormal runway contact during landing

From an unrecorded airport to Jack Edwards National Airport (JKA)

Report a problem

Event

NTSB case
ERA14LA324
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
Visual Meteorological Cond

Beech 95 55

Aircraft type
Beechcraft 95
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
N9411Y
Onboard fatalities
Unknown
Route
From not recordedTo Jack Edwards National Airport (JKA), Gulf Shores, AL
Aircraft age
About 54 years (built 1960)
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 · flare/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
Abnormal runway contact
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 › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot stated that there were no problems with the airplane's performance and handling throughout the flight. He further stated that, after the airplane had touched down for the second time (witnesses reported that the airplane bounced after landing) and had slowed to about 30 knots during the landing roll, he felt a "shimmy" coming from the airplane's nose area. The nose landing gear then collapsed, and the airplane slid on its nose until it stopped partially off the side of the runway. The airframe sustained substantial damage. According to one witness, the airplane's approach speed was "excessive," and the airplane landed in a flat attitude and then bounced. Another witness stated that the airplane touched down on all three landing gear, bounced, and then touched down a second time on the nose landing gear. Examination of the wreckage revealed overstress damage consistent with a hard landing.

Probable cause

The pilot’s improper landing flare, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14LA324
Event ID
20140703X75746
Case number
ERA14LA324
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: 1b0800b533122e2153c27d56bf8bff86e6ded6e1097502b604d0b80ce1d9f610; retrieved 2026-09-16T00:50:29.084Z.