FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA276 · Bell 206-L4

10 May 2013 · Fort Worth, TX, United States

Bell Helicopter Customer Training Academy Bell 206-L4 · Accident: hard landing during autorotation

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

Report a problem

Event

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

Bell 206-L4

Aircraft type
Bell 206
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
N2036F
Onboard fatalities
Unknown
Route
From Perot Field/Fort Worth Alliance Airport (AFW), Fort Worth, TXTo Perot Field/Fort Worth Alliance Airport (AFW), Fort Worth, TX
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
Autorotation
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 › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot receiving instruction was performing a practice right 180-degree autorotation. During the approach, the airspeed decreased to about 40 knots, which shortened the approach angle. At 8 to 10 feet above the ground, the flight instructor advised the pilot to apply forward cyclic while maintaining the collective position. The flight instructor then "used what was left of the rotor rpm to cushion the landing." During the touchdown, the helicopter landed hard, which resulted in structural damage to the tailboom. The pilot reported no preimpact mechanical malfunctions or failures with the helicopter that would have precluded normal operation.

Probable cause

The flight instructor's inadequate supervision and delayed remedial action during a practice autorotation, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA276
Event ID
20130514X15720
Case number
CEN13CA276
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: cda4e073e89ec7fbbb5c813949e944f53c7f6f036c0261cb31d85527576bea8f; retrieved 2026-09-15T21:32:54.681Z.