FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA205 · Airbus Helicopters Inc AS350B3 B3e

1 May 2024 · Plant City, FL, United States

Hillsborough County Sheriff's Office Airbus Helicopters Inc AS350B3 B3e · Accident: loss of tail rotor effectiveness while maneuvering

From Lakeland Linder International Airport (LAL) to Tampa Executive Airport (VDF)

Report a problem

Event

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

Airbus Helicopters Inc AS350B3 B3e

Aircraft type
Airbus AS350
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
N413JM
Onboard fatalities
Unknown
Route
From Lakeland Linder International Airport (LAL), Lakeland, FLTo Tampa Executive Airport (VDF), Tampa, FL
Aircraft age
About 5 years (built 2019)
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
Maneuvering · hover
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
Loss of tail rotor effectiveness
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

During the enroute portion of the flight, the pilot in the left seat of the helicopter requested a transfer of control from the pilot in the right seat so that he could gain proficiency in preparation for obtaining a flight instructor certificate. After a positive transfer of control, the pilot in the left seat successfully conducted a confined-area approach to a 15-ft hover, then departed to search for an area to conduct a second approach. When the helicopter was about 50 ft above ground level (agl) and at an airspeed of about 20 kts, its forward airspeed slowed, and it entered a left turn that the pilot’s control inputs were ineffective in arresting. The turn progressed into a full rotation to the left and the helicopter completed two or three full rotations before impacting the ground, separating the right skid and tail rotor and damaging the tailboom and lower vertical fin. Postaccident examination of the airframe revealed that all damage features observed on the tailboom, aft ring frame, and tail rotor gearbox were consistent with overload structural failures sustained during the hard landing. The separated tail rotor blade did not show significant fragmentation, consistent with unpowered separation of the blade, likely due to impact with the ground after the tail rotor gearbox separated from the airframe. The tail rotor control system was continuous to the point where the tail rotor gearbox had separated from the airframe. One of six attachment bolts for the No. 1 tail rotor driveshaft (TRDS) hanger bearing support was not present in its installed location. The bolt was found lying in the tray area of the TRDS cover, and the respective nut was not found. The five remaining attachment bolts for the No. 1 TRDS hanger bearing support were found loose, consistent with having been inadequately torqued when installed during maintenance activities performed about 1 month before the accident. However, the tail rotor driveshafts showed no evidence of anomalous wear or preimpact fracture; thus, it is unlikely that the improper maintenance of the No. 1 TRDS hanger bearing support attachment hardware was a factor in this accident. No evidence of a pre-accident mechanical malfunction of the helicopter, control systems, or components that would have precluded normal operation was identified. Although the pilot stated that his control inputs were ineffective to counter the helicopter’s uncommanded left turn, data recovered from the engine data recorder (EDR) showed that the tail rotor potentiometer (XPA) value peaked only at 58.82% (consistent with a pedal position value of only 74.5%) and for only 1 second. This indicated that the pilot did not push the right pedal to its fullest extent and did not push it long enough for the pedal input to effectively counter the uncommanded left turn. According to a safety notice published by the helicopter manufacturer, all types of single-rotor helicopters can be susceptible to unanticipated left yaw at low speed. The notice indicated that unanticipated yaw has historically been referred to as “loss of tail rotor effectiveness,” but noted that the term “wrongly implies that tail rotor efficiency is reduced.” The notice stated that, when an unanticipated left yaw situation is encountered, “swift corrective action is needed in response, otherwise loss of control and possible accident may result.” According to the notice, “the key feature of an unanticipated left yaw recovery is large amplitude right pedal input. Recovery may not be immediate but will occur if the pilot persists in maintaining right pedal.” The helicopter was equipped with a cockpit image recorder that could have provided additional data to better understand the sequence of events leading up to the accident. However, it did not record the accident flight or any other flights in the previous 90 days and would not record when examined after the accident. The required annual functional check of the system, which maintenance records indicated was performed about 1 month before the accident, should have detected and rectified the malfunction before returning the helicopter to service.

Probable cause

The pilot’s inadequate yaw control of the helicopter while maneuvering at a low altitude and airspeed, which resulted in a hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA205
Event ID
20240502194194
Case number
ERA24LA205
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, coordinates, 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: ffceb8442fd37589e20388850c680b0d4279d416c308404a2522e6010fc630ed; retrieved 2026-09-16T18:43:38.527Z.