NYC65F0067

NTSB accident investigation · Cessna 172 · Bolton, CT · February 1, 1965

Accident · No injuriesClosed
Date
February 1, 1965
Place
Bolton, CT · BOLTON, CT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7771UCessna 172
Status
Completed · report April 5, 1965
Report
Brief approved by the director
Case key
180192

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-0325   65/2/1    BOLTON CONN         CESSNA 172          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 44, 40 TOTAL
        TIME - 1720                    N7771U              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - CONTINUED VFR FLIGHT INTO ADVERSE WEATHER CONDITIONS
           PERSONNEL - FLIGHT INSTRUCTOR: INADEQUATE SUPERVISION OF FLIGHT
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT
                                  LOW ON FUEL

Aircraft

Registration
N7771U
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.