MKC66D0365

NTSB accident investigation · Cessna 172 · Trimont, MN · January 1, 1966

Accident · No injuriesClosed
Date
January 1, 1966
Place
Trimont, MN · TRIMONT, MN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7694TCessna 172
Status
Completed · report May 3, 1966
Report
Brief approved by the director
Case key
173986

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-0567   66/1/1    TRIMONT MINN        CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 26, 243
        TIME - 1715                    N7694T              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 88 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - RIGENHAGEN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY

Aircraft

Registration
N7694T
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Rigenhagen

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.