FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA532 · Airborne EDGE X

1 Sept 2014 · Willow Springs, MO, United States

Airborne EDGE X · Accident: windshear or thunderstorm during landing

From Willow Springs Memorial Airport (1H5) to Willow Springs Memorial Airport (1H5)

Report a problem

Event

NTSB case
CEN14CA532
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

Airborne EDGE X

Aircraft type
Airborne EDGE
Category
Weight-Shift
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
N2017A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Willow Springs Memorial Airport (1H5), Willow Springs, MOTo Willow Springs Memorial Airport (1H5), Willow Springs, MO
Aircraft age
About 7 years (built 2007)
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
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
Windshear or thunderstorm
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

  • Environmental issues › Conditions/weather/phenomena
  • 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, about 45 minutes before departure, he obtained the current weather conditions via an internet website and observed a thunderstorm located about 100 miles west of the departure airport. About 20 minutes into the local area flight, he recalled seeing a low cloud bank, with a base of about 1,000 feet above ground level (agl), about 1/4 mile east of the airport. At the same time, he noticed an area of heavy rain from clouds located about 15 miles west of his position. He decided to land as soon as possible due to the deteriorating weather. Instead of making an approach to the airport's single runway, he decided to land toward the west in an open pasture area that was located on the airport property. Shortly after clearing trees and hangars that were located on the east side of the airport, the weight-shift-control aircraft suddenly lost altitude, from about 20 feet agl, and impacted the ground in an upright attitude. After the impact, the aircraft rolled over onto its left side. The pilot reported that the aircraft did not appear to have any forward velocity when it impacted terrain, as indicated by a lack of damage to the surrounding vegetation. The aircraft sustained substantial damage to the wing and fuselage. He stated that there were no mechanical malfunctions of the aircraft that would have precluded normal operation. Additionally, he reported that the aircraft's operating limitations included a maximum headwind and crosswind component of 21 knots and 11 knots, respectively.

Meteorological data collected during the accident investigation indicated that, at the time of the accident, there was a squall line of strong-to-severe thunderstorms within a few miles of the accident site. Local weather stations indicated that there was a wind shift from the south to the north that was associated with the passage of the frontal boundary. The weather stations also reported wind gusts reaching 24 knots. A review of weather radar imagery indicated that, at the time of the pilot's preflight weather check, there was a line of thunderstorms located about 40 miles northwest of the departure airport. The same line of thunderstorms was within a few miles of the airport at the time of the accident and moved through the area almost immediately thereafter. The meteorological data suggested that the aircraft likely encountered a gust front that was associated with approaching line of thunderstorms. Although the pilot checked the weather before departure, his failure to correctly identify the location and speed of the approaching line of thunderstorms contributed to the low-level wind shear encounter shortly before touchdown.

Probable cause

The pilot's loss of control after the weight-shift-control aircraft encountered low-level wind shear shortly before touchdown. Also causal to the accident was the pilot's inadequate preflight weather assessment that failed to correctly determine the actual location and speed of the approaching line of thunderstorms.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA532
Event ID
20141118X30316
Case number
CEN14CA532
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: 547428d2065fee2818f9ce8b7b6260b322da5b046197feccc39b118c8a729c64; retrieved 2026-09-16T01:56:10.588Z.