MKC69A0043

NTSB accident investigation · Hughes 269B · Kansas City, MO · January 10, 1969

Accident · FatalClosed
Date
January 10, 1969
Place
Kansas City, MO · KANSAS CITY, MO
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N9496FHughes 269B
Status
Completed · report May 5, 1969
Report
Brief approved by the director
Case key
191583

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

NTSB brief

NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.

----------------------------------------------------------------------------------------------------------------------------
 FILE    DATE          LOCATION          AIRCRAFT DATA       INJURIES       FLIGHT                        PILOT DATA
                                                               F  S M/N     PURPOSE
----------------------------------------------------------------------------------------------------------------------------
3-0155  69/1/10    KANSAS CITY,MO      HUGHES 269B         CR-  1  0  0  INSTRUCTIONAL             STUDENT, AGE 34, 46 TOTAL
        TIME - 1321                    N9496F              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - SIMULATED CONDITIONS
           PILOT IN COMMAND - FAILED TO MAINTAIN ADEQUATE ROTOR R.P.M.
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS
         FIRE AFTER IMPACT
        REMARKS- PRACTICING AUTOROTATIVE LANDINGS.

Aircraft

Registration
N9496F
Reported as
Hughes 269B
Category
Helicopter
Engine
reciprocating
Damage
Destroyed

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.