FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA558 · Bellanca 14 19 3A

26 Aug 2017 · Redding, CA, United States

Bellanca 14 19 3A · Accident: runway excursion during landing

From Redding Municipal Airport (KRDD) to Redding Municipal Airport (KRDD)

Report a problem

Event

NTSB case
GAA17CA558
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 14 19 3A

Aircraft type
Bellanca 14
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
N36KC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Redding Municipal Airport (KRDD), Redding, CATo Redding Municipal Airport (KRDD), Redding, CA
Aircraft age
About 51 years (built 1966)
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
Runway excursion
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, the airplane's airspeed was fast during the landing, and the airplane veered to the left during the landing roll. The airplane exited the left side of the runway, and the nose landing gear collapsed.

The airplane sustained substantial damage to the lower fuselage.

The METAR at the accident airport reported that, about the time of the accident, the wind was calm, and the sky was clear.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain directional control during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA558
Event ID
20170927X10647
Case number
GAA17CA558
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-08-27.
  • API snapshot SHA-256: fa8c0c94f39144ffc6d0c5979560c6a082372fdb8e48c9feabdfb507413ba548; retrieved 2026-09-16T05:53:31.301Z.