GAA16CA389 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: hard landing
From Cape Cod Gateway Airport (HYA) to Cape Cod Gateway Airport (HYA)
Event
- NTSB case
- GAA16CA389
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N799MR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cape Cod Gateway Airport (HYA), Hyannis, MATo Cape Cod Gateway Airport (HYA), Hyannis, MA
- Aircraft age
- About 12 years (built 2004)
- 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 reported that during landing she slowed the airplane's rate of decent to allow a touchdown after the runway intersection because of a slight surface rise that had caused bumpy landings in the past. She further reported that during touchdown the airplane landed hard and bounced about four feet into the air. She then added full power to abort the landing but was unable to regain airspeed and the airplane veered off the runway centerline to the left. The airplane collided with a security fence and airport rental cars sustaining substantial damage to both wings and fuselage.
The pilot reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Probable cause
The pilot's failure to maintain an appropriate descent rate during landing, which resulted in a hard landing, followed by a loss of directional control, runway excursion, and an impact with a security fence and vehicles during the subsequent attempt to abort the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA389
- Event ID
- 20160726X22534
- Case number
- GAA16CA389
- 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: 6de2c7a6ad06a72e3c11d195bb9a80bcf6ea50c1ec3db545e3cb449dc5c5adc9; retrieved 2026-09-16T03:42:01.099Z.