UNK66X0160

NTSB accident investigation · Cessna 180 · Simunjan Sarawak, Malaysia · August 3, 1966

Accident · No injuriesClosed
Date
August 3, 1966
Place
Simunjan Sarawak, Malaysia · SIMUNJAN SARAWAK, Malaysia
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3685CCessna 180
Status
Completed · report April 25, 1967
Report
Brief approved by the director
Case key
121398

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-0056   66/8/3    SIMUNJAN SARAWAK    CESSNA 180          CR-  0  0  1  NONCOMMERCIAL             CERTIFICATE UNKNOWN, AGE
        TIME - 1530                    N3685C              PX-  0  0  1  BUSINESS                  UNK/NR, UNK/NR TOTAL
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            HOURS, UNK/NR IN TYPE,
                                                                                                   NOT INSTRUMENT RATED.
        NAME OF AIRPORT - KAMPONG MALANJOK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        REMARKS- INVESTIGATION UNDER THE JURISDICTION OF THE GOVERNMENT OF SARAWAK.

Aircraft

Registration
N3685C
Reported as
Cessna 180
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Kampong Malanjok

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.