UNK67X0120

NTSB accident investigation · Pilatus PC-6C · Saigon, VM · March 29, 1967

Accident · No injuriesClosed
Date
March 29, 1967
Place
Saigon, VM · SAIGON, Vietnam
Injuries
7 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N9444Pilatus PC-6C
Status
Completed · report February 29, 1968
Report
Brief approved by the director
Case key
116739

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
----------------------------------------------------------------------------------------------------------------------------
6-0029  67/3/29    SAIGON,VIETNAM      PILATUS PC-6C       CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 36, 4400
        TIME - 1322                    N9444               PX-  0  0  6  CORP/EXEC                 TOTAL HOURS, 700 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           GEAR COLLAPSED                                           LANDING: ROLL
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND
        REMARKS- INVESTIGATION UNDER JURISDICTION OF SO.VIETNAM GOVT.

Aircraft

Registration
N9444
Reported as
Pilatus PC-6C
Category
Airplane
Engine
reciprocating
Damage
Substantial 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.