SEA68F0142

NTSB accident investigation · Piper PA-24 · Columbus, MT · August 14, 1967

Accident · No injuriesClosed
Date
August 14, 1967
Place
Columbus, MT · COLUMBUS, MT
Injuries
3 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N5384PPiper PA-24
Status
Completed · report February 2, 1968
Report
Brief approved by the director
Case key
114791

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-4305  67/8/14    COLUMBUS,MONT       PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 46, 2240
        TIME - 1500                    N5384P              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 21 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - COLUMBUS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        FACTOR(S)
           AIRFRAME - LANDING GEAR: NORMAL RETRACTION/EXTENSION ASSEMBLY
           MISCELLANEOUS ACTS,CONDITIONS - CIRCUIT BREAKER POPPED
         FIRE AFTER IMPACT

Aircraft

Registration
N5384P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Columbus

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.