FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA121 · Eurocopter AS 350 B2

29 Jan 2019 · Tampa, FL, United States

Hillsborough County Sheriffs Office Eurocopter AS 350 B2 · Accident: hard landing

From Tampa Executive Airport (VDF) to Tampa Executive Airport (VDF)

Report a problem

Event

NTSB case
GAA19CA121
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
Government
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

Eurocopter AS 350 B2

Aircraft type
Eurocopter AS-350
Category
Helicopter
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
N680DG
Onboard fatalities
Unknown
Route
From Tampa Executive Airport (VDF), Tampa, FLTo Tampa Executive Airport (VDF), Tampa, FL
Aircraft age
About 14 years (built 2005)
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
Public Aircraft
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 flight instructor reported that, during preparation for the pilot's helicopter commercial checkride, they were going to practice autorotation procedures. He added that, during the second autorotation, he saw that the rotor rpm had dropped significantly and that the pilot was pulling up on the collective. He immediately took command of the flight controls and attempted to lower the collective. Subsequently, the helicopter landed hard, bounced, yawed right, bounced again, and then came to rest on the right side of the runway.

The helicopter sustained substantial damage to the tailboom.

The flight instructor reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.

Probable cause

The pilot's improper landing flare while practicing autorotations, which resulted in a hard, bounced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA121
Event ID
20190129X01825
Case number
GAA19CA121
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: 84aca7881cc5bc144192e57d601f96354acb91505ce4dce1f544c500294f0bb1; retrieved 2026-09-16T08:33:58.351Z.