FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA338 · Robinson Helicopter R44 UNDESIGNAT

2 Jul 2014 · Olathe, KS, United States

Robinson Helicopter R44 UNDESIGNAT · Accident while standing

From Iola, KS to Johnson County Executive Airport (OJC)

Report a problem

Event

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

Robinson Helicopter R44 UNDESIGNAT

Aircraft type
Robinson R44
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
N225TV
Operator
KC Copters
Onboard fatalities
Unknown
Route
From Iola, KSTo Johnson County Executive Airport (OJC), Olathe, KS
Aircraft age
About 18 years (built 1996)
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
Standing · engine(s) shutdown
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
Miscellaneous/other
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 he landed at the airport without incident. During engine shutdown, he applied rotor brake to slow the main rotor blades. When the pilot released the brake, he heard a bang and felt an impact to the aircraft on the rear left side. He reapplied the main rotor brake intermittently until the blades stopped. The pilot exited the aircraft and noticed a tail boom strike occurred. He stated he input aft cyclic during landing to accommodate landing slightly downhill and did not place the controls in neutral during shutdown. According to the manufacture's shutdown procedures, the cyclic and pedals should be in the neutral position.

Probable cause

The pilot's failure to follow the manufacturer's engine shutdown procedure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA338
Event ID
20140703X85332
Case number
CEN14CA338
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: a9961069a1805056141b4a2322104d73dc6e803f8fef0e9ba26042d2d004e1fe; retrieved 2026-09-16T00:50:35.876Z.