FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20CA395 · Bell 407

15 Sept 2020 · Fort Worth, TX, United States

Bell 407 · Accident: hard landing

From Perot Field/Fort Worth Alliance Airport (AFW) to an unrecorded destination

Report a problem

Event

NTSB case
CEN20CA395
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
Event fatalities
Unknown
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

Bell 407

Aircraft type
Bell 407
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
N489DM
Operator
Dea
Onboard fatalities
Unknown
Route
From Perot Field/Fort Worth Alliance Airport (AFW), Fort Worth, TXTo not recorded
Aircraft age
About 16 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 · flare/touchdown
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

During a routine training flight, the helicopter was in the traffic pattern practicing power recovery auto-rotations, with the pilot under training at the flight controls. During the 5th practice auto-rotation, the flight instructor reduced the throttle, and the helicopter began a normal descent. During the deceleration flare, about 75 ft above ground level, the flight instructor heard the low rotor RPM audio tone. Using a positive transfer of control, the flight instructor quickly took the flight controls. He increased the throttle to what he believed to be the “FLY” position. The helicopter settled onto a taxiway. The main rotor blades severed the vertical fins on the horizontal stabilizer, and the tail rotor driveshaft was severed. The operator reported that the pilot did not rapidly roll the throttle to the “FLY” position during the deceleration/flare, and the helicopter contacted the ground at less than 100% rotor RPM. The operator stated that there were no mechanical anomalies with the helicopter that would have precluded normal operations.

Probable cause

The flight instructor’s delay in rolling the throttle to the fly position during a practice autorotation maneuver that resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20CA395
Event ID
20200916X90520
Case number
CEN20CA395
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, cause areas. 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: d7ffb97207222c514c035503a0eeeb5b6db1516f05691f4030f1b0c7d56b936f; retrieved 2026-09-16T13:03:11.925Z.