FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15FA257 · Morse Frank L REBEL

5 Jun 2015 · Eagle, CO, CO, United States

Morse Frank L REBEL · Accident: loss of control in flight during landing

From an unrecorded airport to Eagle County Regional Airport (EGE)

Report a problem

Event

NTSB case
CEN15FA257
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
1 · 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

Morse Frank L REBEL

Aircraft type
Morse Frank REBEL
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
N914FM
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo Eagle County Regional Airport (EGE), Eagle, CO, CO
Aircraft age
About 19 years (built 1996)
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
Loss of control in flight
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was landing the experimental, amateur-built airplane in gusty, crosswind conditions. Witnesses observed the airplane enter a sharp left turn away from the runway at a very low altitude, overfly the airport taxiway and ramp area, then impact a hangar on the airport property. A witness stated that "the wind caught [the airplane]" as it was landing. The airplane had a stated crosswind limitation of 15 knots. Based on recorded wind data, the calculated crosswind component was between 13.7 knots and 16.8 knots. Examination of the airplane wreckage did not reveal any anomalies that would have prevented normal operation. The accident sequence is consistent with the pilot losing control of the airplane while landing in gusty, crosswind conditions that likely exceeded the recommended crosswind limitation of the airplane.

Probable cause

The pilot’s failure to maintain control of the airplane while landing in gusty, crosswind conditions that likely exceeded the recommended limitation of the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15FA257
Event ID
20150605X23836
Case number
CEN15FA257
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: 5c8127397240bb7e936bc088a83d2c2c1d4e9c86306d12545e7fbce84293327c; retrieved 2026-09-14T19:28:40.970Z.