MIA67D0282

NTSB accident investigation · Cessna 172 · Jasper, AL · October 19, 1966

Accident · No injuriesClosed
Date
October 19, 1966
Place
Jasper, AL · JASPER, AL
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5372RCessna 172
Status
Completed · report January 16, 1966
Report
Brief approved by the director
Case key
120884

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-3383  66/10/19   JASPER ALA          CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 41, 264
        TIME - 1850                    N5372R              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - WALKER COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: TREES                                     LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- AIRCRAFT CONTINUED FLIGHT LANDING WITH NO FURTHER DAMAGE.

Aircraft

Registration
N5372R
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Walker County

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.