OAK73OJA02

NTSB accident investigation · Cessna 150G · Clark Afbase, RP · April 11, 1972

Accident · No injuriesClosed
Date
April 11, 1972
Place
Clark Afbase, RP · CLARK AFBASE, Philippines
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3843SCessna 150G
Status
Completed · report April 24, 1973
Report
Brief approved by the director
Case key
166808

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-0067  72/4/11    CLARK AFBASE,PI     CESSNA 150G         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 25, 28 TOTAL
        TIME - 0910                    N3843S              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CLARK AFB
        DEPARTURE POINT             INTENDED DESTINATION
          CLARK AFBASE,PI             LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        REMARKS- INVEST UNDER JURISDICTION OF GOVT OF PHILLIPINES

Aircraft

Registration
N3843S
Reported as
Cessna 150G
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Clark Afb

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.