GAA18CA186 · Terry G. Olson Kitfox S7 Super Spor
Terry G. Olson Kitfox S7 Super Spor · Accident: hard landing
From BFW · Silver Bay, MN to BFW · Silver Bay, MN
Event
- NTSB case
- GAA18CA186
- 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
Terry G. Olson Kitfox S7 Super Spor
- Aircraft type
- Terry G Olson KITFOX S7 SUPER SPOR
- 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
- N141AB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From BFW · Silver Bay, MNTo BFW · Silver Bay, MN
- Aircraft age
- About 1 year (built 2017)
- 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
- Hard landing
- 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 in the experimental amateur-built, tailwheel-equipped airplane reported that, during landing with a slight right crosswind, he flared too early and the airplane bounced. He aborted the landing by adding full power, and the airplane drifted to the left. The left wing contacted the ground and he over corrected to the right. The airplane stalled and impacted the ground, and subsequently nosed over.
The airplane sustained substantial damage to the right wing and the empennage.
The pilot reported that the wind at the accident airport at the time of the accident was from 280° at 6 knots, gusting to 8 knots. The pilot aborted the landing on runway 25.
The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s hard landing and subsequent failure to maintain airspeed and bank control during the aborted landing, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA186
- Event ID
- 20180329X20254
- Case number
- GAA18CA186
- 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: cc5cb00177889a5b2568d21724d4dfbc0b268c9cf05b8be7896c1861e2940d35; retrieved 2026-09-16T06:44:40.366Z.