GAA16CA294 · Bellanca 17 30 A
Bellanca 17 30 A · Accident: loss of control on ground during landing
From Cincinnati Municipal Airport Lunken Field (LUK) to Shannon Airport (EZF)
Event
- NTSB case
- GAA16CA294
- 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
Bellanca 17 30 A
- Aircraft type
- Bellanca 17
- 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
- N14753
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cincinnati Municipal Airport Lunken Field (LUK), Cincinnati, OHTo Shannon Airport (EZF), Fredericksburg, VA
- Aircraft age
- About 42 years (built 1974)
- 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 · landing roll
- 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 on ground
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
According to the pilot, during the landing roll in gusting wind, the airplane made a sharp turn to the right and exited the runway. He reported that after passing the ramp area, the aircraft made a sudden turn to the right, and "I was unable to get it turned before leaving the runway and losing braking on the grass." The airplane crossed through the grass safety area and the right wing collided with a tree. The airplane sustained substantial damage to both wings, the nose and left main landing gear attachment points.
The wind reported at the airport at the time of the accident was 320 degrees true, at 12 knots with gusts to 24 knots, the airplane landed on runway 24.
The crosswind component was calculated at18 knots at the time of the accident, and according to the manufacturer, the airplane has a demonstrated direct crosswind component of 20 knots during takeoffs and landings.
The pilot reported that there were no mechanical anomalies or malfunctions with any portion of the airplane that would have prevented normal flight operations.
Probable cause
The pilot's failure to maintain directional control during the landing roll in gusting wind resulting in a runway excursion and substantial damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA294
- Event ID
- 20160609X33959
- Case number
- GAA16CA294
- 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: 5970995d51d89fb3e679dd88bf766e1f0c49da1c7daa8836ab0a1bdcc52f35e1; retrieved 2026-09-16T03:29:16.527Z.