OAK67D0161

NTSB accident investigation · Globe GC-1B · Las Vegas, NV · November 15, 1966

Accident · No injuriesClosed
Date
November 15, 1966
Place
Las Vegas, NV · LAS VEGAS, NV
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3880KGlobe GC-1B
Status
Completed · report January 31, 1967
Report
Brief approved by the director
Case key
178390

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-3524  66/11/15   LAS VEGAS NEV       GLOBE GC-1B         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 50, 270
        TIME - 1700                    N3880K              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 27 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - AIR TERMINAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3880K
Reported as
Globe GC-1B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Air Terminal

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.