MKC66D0585

NTSB accident investigation · Cessna 172 · Camdenton, MO · May 21, 1966

Accident · No injuriesClosed
Date
May 21, 1966
Place
Camdenton, MO · CAMDENTON, MO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5597RCessna 172
Status
Completed · report October 14, 1966
Report
Brief approved by the director
Case key
171892

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-2219  66/5/21    CAMDENTON MO        CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 31, 55 TOTAL
        TIME - 0815                    N5597R              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 1 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CAMDENTON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N5597R
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Camdenton

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.