FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10LA477 · Bell 206B

13 Aug 2010 · Rocky Mount, MO, United States

Computer Service Professionals Bell 206B · Accident: dynamic rollover during landing

From Jefferson City Memorial Airport (JEF) to Rocky Mount, MO (private airstrip)

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
CEN10LA477
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 206B

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
N54BE
Onboard fatalities
Unknown
Route Narrative disagrees
From Jefferson City Memorial Airport (JEF), Jefferson City, MOTo Rocky Mount, MO (private airstrip)
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
Landing
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
Dynamic rollover
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

  • 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

The pilot reported that the approach and landing were normal. After landing, he lowered the collective and began to decrease engine power by manipulating the throttle closed. Before the throttle was completely closed, the helicopter suddenly rolled to the right and came to rest on its right side, incurring damage to the airframe, main rotor, and tail boom. A postaccident examination did not reveal any anomalies consistent with a preimpact failure or malfunction. Dynamic rollover is the tendency of a helicopter to continue rolling when the critical angle is exceeded, if one skid is on the ground, and the helicopter is pivoting around that point. Dynamic rollover is possible when a skid is caught by a projection on the surface or when landing on a slope.

Probable cause

A dynamic rollover inadvertently induced by the pilot during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10LA477
Event ID
20100813X61915
Case number
CEN10LA477
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. 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: 9da9b5d40f4c005c897df89e32a0024ee86b3d44d50b4463ab9e1156577bc8e9; retrieved 2026-09-15T14:50:27.102Z.