MIA68F0354

NTSB accident investigation · Cessna 172 · High Springs, FL · January 2, 1968

Accident · No injuriesClosed
Date
January 2, 1968
Place
High Springs, FL · HIGH SPRINGS, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5064ACessna 172
Status
Completed · report February 23, 1968
Report
Brief approved by the director
Case key
114959

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-0189   68/1/2    HIGH SPRINGS,FLA    CESSNA 172          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 43, 21 TOTAL
        TIME - 1300                    N5064A              PX-  0  0  0  SOLO                      HOURS, 19 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SKY ROAD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: OBJECT                                    LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        REMARKS- STRUCK WIND DIRECTION INDICATOR.

Aircraft

Registration
N5064A
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sky Road

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.