DEN66A0043

NTSB accident investigation · Fairchild F-27 · Yuma, AZ · December 8, 1965

Accident · No injuriesClosed
Date
December 8, 1965
Place
Yuma, AZ · YUMA, AZ
Injuries
17 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N749LFairchild F-27
Status
Completed · report April 27, 1966
Report
Brief approved by the director
Case key
175475

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
----------------------------------------------------------------------------------------------------------------------------
1-0079   65/12/8   YUMA,ARIZ           FAIRCHILD F-27      CR-  0  0  3  SCHED DOM PASSG SRV       ATP,FLIGHT INSTR., AGE
        TIME - 2045                    N749L               PX-  0  0 14                            37, 10878 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            4707 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - YUMA INTL
        OPERATOR - BONANZA AIR LINES,INC.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR RETRACTED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADVERTENTLY RETRACTED GEAR

Aircraft

Registration
N749L
Reported as
Fairchild F-27
Category
Airplane
Engine
turbo prop
Damage
Substantial damage
Airport
Yuma Intl

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.