DEN69D0126

NTSB accident investigation · Beech 36 · Denver, CO · October 1, 1968

Accident · No injuriesClosed
Date
October 1, 1968
Place
Denver, CO · DENVER, CO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7505NBeech 36
Status
Completed · report December 19, 1968
Report
Brief approved by the director
Case key
107914

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-3663   68/10/1   DENVER,COLO         BEECH 36            CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1310                    N7505N              PX-  0  0  0  BUSINESS                  AGE 53, 7000 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            2500 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - STAPLETON INT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR RETRACTED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADVERTENTLY RETRACTED GEAR
        REMARKS- MAIN GEAR HELD, NOSE GEAR RETRACTED.

Aircraft

Registration
N7505N
Reported as
Beech 36
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Stapleton Int

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.