FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA205 · Robinson Helicopter R22 BETA

30 May 2024 · Palmyra, MO, United States

Robinson Helicopter R22 BETA · Accident: low altitude operation/event while maneuvering

From Palmyra, MO to an unrecorded destination

Report a problem

Event

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

Robinson Helicopter R22 BETA

Aircraft type
Robinson R22
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
N221RH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Palmyra, MOTo not recorded
Aircraft age
About 26 years (built 1998)
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
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
Low altitude operation/event
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
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
  • Environmental issues › Physical environment
  • Personnel issues › Psychological

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

NTSB narrative

The helicopter pilot reported that during an approach to an off-airport confined area, the skid struck the top of a power line that he did not see. Upon impact the helicopter began to nose over and spin as the pilot closed the engine throttle. The helicopter subsequently impacted the road adjacent to the intended landing point. The tail boom separated, and the main rotor system and airframe sustained substantial damage. The pilot reported that there were no preimpact mechanical failures or malfunctions that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain clearance from power lines during approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA205
Event ID
20240603194364
Case number
CEN24LA205
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: 58b63737b5e1cc6fc97c02842eeb5a132c695d4c2208f26998760bddd295ae9b; retrieved 2026-09-16T18:49:46.895Z.