FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09LA558 · Hughes 269C

2 Sept 2009 · Arapahoe, NE, United States

Cavalea Continental Freight Hughes 269C · Accident en route

From Arapahoe Municipal Airport (37V) to Colorado Plains Regional Airport (AKO)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Hughes 269C

Aircraft type
Hughes 269
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
N58163
Onboard fatalities
Unknown
Route Narrative disagrees
From Arapahoe Municipal Airport (37V), Arapahoe, NETo Colorado Plains Regional Airport (AKO), Colorado Plains, CO
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
En route · cruise
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
Unknown or undetermined
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

  • Not determined › Not determined

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

NTSB narrative

During cruise flight in a reciprocating single-engine helicopter, the pilot heard a loud noise and felt a vibration. The pilot immediately entered an autorotation and turned the flight controls over to the flight instructor. The flight instructor elected to continue the autorotation to an open field. During the landing the helicopter's landing skids stuck into the soft terrain, causing the helicopter's nose to pitch down and tail to pitch up. The main rotor blades impacted the tail boom, severing it; the helicopter subsequently rolled onto its side. An examination of the helicopter failed to find a reason for the noise and vibration.

Probable cause

A sudden vibration for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09LA558
Event ID
20090903X22528
Case number
CEN09LA558
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: 425daa3d35ad5558d6e3d2c4e7a438ee470fd9293750ebd292376c103e6e35bd; retrieved 2026-09-15T12:53:05.794Z.