CHI67I0078

NTSB incident investigation · Boeing 720 · Cleveland, OH · December 19, 1966

Incident · Serious injuriesClosed
Date
December 19, 1966
Place
Cleveland, OH · CLEVELAND, OH
Injuries
1 serious, 38 uninjured
Damage
No damage
Phase of flight
Enroute
Aircraft
N7226UBoeing 720
Status
Completed · report May 19, 1967
Report
Brief approved by the director
Case key
119481

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

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
----------------------------------------------------------------------------------------------------------------------------
4-0048  66/12/19 NR.CLEVELAND OHIO     BOEING 720          CR-  0  0  7  SCHED DOM PASSG SRV       CERTIFICATE UNKNOWN, AGE
        TIME - 1559                    N7226U              PX-  0  1 31                            UNK/NR, UNK/NR TOTAL
                                       DAMAGE-NONE         OT-  0  0  0                            HOURS, UNK/NR IN TYPE,
                                                                                                   UNK/NR INSTRUMENT RATED.
        CLASSIFIED AS INCIDENT
        OPERATOR - UNITED AIR LINES,INC.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           MISCELLANEOUS                                            IN FLIGHT: DESCENDING
        REMARKS- ACFT DESCENDING TO LAND,SEAT-BELT SIGN ON,AIR SMOOTH.PAX LEFT SEAT,FELL AND BROKE HER LEG

Aircraft

Registration
N7226U
Reported as
Boeing 720
Category
Airplane
Engine
turbo jet
Damage
No damage

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.