ERA24LA287 · Airbus Helicopters AS350 B3
Seminole County Sheriffs Office Airbus Helicopters AS350 B3 · Accident: settling with power/vortex ring state while maneuvering
From Orlando Sanford International Airport (SFB) to an unrecorded destination
Event
- NTSB case
- ERA24LA287
- 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 AS350 B3
- 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
- N174SC
- Operator
- Seminole County Sheriffs Office
- Onboard fatalities
- Unknown
- Route
- From Orlando Sanford International Airport (SFB), Sanford, FLTo not recorded
- Aircraft age
- About 1 year (built 2023)
- 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 · low-altitude flying
- 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
- Settling with power/vortex ring state
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
As part of a law enforcement simulation exercise, the helicopter pilot was orbiting near the departure airport between 200 to 300 ft above ground level, at 20 to 40 knots indicated airspeed. The pilot described that while the helicopter was in a left orbit the airspeed decreased to near 0. At that time, the helicopter began to descend in a vortex ring state (VRS). Due to the low altitude, the pilot was not able to recover from VRS and entered an autorotation to a grass area on the airport. The helicopter subsequently landed hard and came to rest upright in the grass area resulting in substantial damage to the helicopter’s tail boom. The pilot reported that there were no preimpact mechanical malfunctions or failures of the helicopter.
Probable cause
The helicopter pilot’s improper maneuvering at low altitude in gusty wind conditions, which resulted in the helicopter entering a vortex ring state, and hard landing during a subsequent autorotation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA287
- Event ID
- 20240701194587
- Case number
- ERA24LA287
- 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: 8ddb3c2a61c57b996b156ab9367b5c82782570644be38caa49a7ff9253906f36; retrieved 2026-09-16T18:59:16.704Z.