OAK66F0200

NTSB accident investigation · Cessna 170A · Merced, CA · February 18, 1966

Accident · No injuriesClosed
Date
February 18, 1966
Place
Merced, CA · MERCED, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9222ACessna 170A
Status
Completed · report March 28, 1966
Report
Brief approved by the director
Case key
173835

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-0291  66/2/18    MERCED CALIF        CESSNA 170A         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 47, 35 TOTAL
        TIME - 1430                    N9222A              PX-  0  0  0  PRACTICE                  HOURS, 4 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MERCED
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING

Aircraft

Registration
N9222A
Reported as
Cessna 170A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Merced

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.