MIA93LA189 · Ferrie FERRI EXEC
Ferrie FERRI EXEC · Accident: in flight collision with terrain/water during landing
Event
- NTSB case
- MIA93LA189
- 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
- 0
- 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
Ferrie FERRI EXEC
- Aircraft type
- Ferrie FERRI EXEC
- 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
- N71714
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- In flight collision with terrain/water
- 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
- Pilot in command › Flight controls, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was demonstrating an autorotation with power recovery to his passenger. The deceleration and initial collective pitch pull was late, and rotor rpm was low. The pilot lowered the collective pich to increase rotor rpm and the helicopter started spinning to the left. Right antitorque pedal was applied with negative results, and the helicopter continued to spin through 360 degrees. The pilot lowered collective pitch and the helicopter collided with the terrain and rolled over on its left side. The pilot stated he made no attempt to stop the rotation by increasing throttle before the helicopter collided with the terrain.
Probable cause
The pilot-in-command's improper use of the flight controls (cyclic and collective) during a simulated autorotation, resulting in an in flight collision with terrain and subsequent roll over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA93LA189
- Event ID
- 20001211X13456
- Case number
- MIA93LA189
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 3c4235219b607afcc8fc5e38ea640f17c54f1c586d97190181204d011f2a1f72; retrieved 2026-09-23T01:39:26.027Z.