FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA435 · Piper PA34 220T

26 Jun 2019 · State College, PA, United States

Kilo Sierra Piper PA34 220T · Accident: loss of control on ground during landing

From Westover Metropolitan Airport / Westover Air Reserve Base (CEF) to State College Regional Airport (UNV)

Report a problem

Event

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

Piper PA34 220T

Aircraft type
Piper PA34
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
N497SA
Operator
Kilo Sierra
Onboard fatalities
Unknown
Route
From Westover Metropolitan Airport / Westover Air Reserve Base (CEF), Springfield/Chicopee, MATo State College Regional Airport (UNV), State College, PA
Aircraft age
About 38 years (built 1981)
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
Loss of control on ground
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, while landing with gusting winds, the airplane bounced several times. During the last bounce, the nose landing gear and the right main landing gear collapsed, and the airplane veered right, exited the runway, and came to rest in the adjacent grass. The airplane sustained substantial damage to the fuselage and the right wing. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Probable cause

The pilot's improper landing flare in gusting wind conditions, which resulted in a bounced landing and landing gear collapse.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA435
Event ID
20190718X51611
Case number
GAA19CA435
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, coordinates. 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: a81aff30b975149d700b6007d69b8ce8e72b19d3719375fb003b6db71bd2b650; retrieved 2026-09-16T09:27:00.156Z.