IAD70D0121

NTSB accident investigation · Cessna 172 · Monroe, NC · December 29, 1969

Accident · No injuriesClosed
Date
December 29, 1969
Place
Monroe, NC · MONROE, NC
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5775ACessna 172
Status
Completed · report May 28, 1970
Report
Brief approved by the director
Case key
146409

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-4641  69/12/29   MONROE,NC           CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 28, 222
        TIME - 1745                    N5775A              PX-  0  0  2  PRACTICE                  TOTAL HOURS, 94 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          MONROE,NC                   MONROE,NC
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        REMARKS- PRACTICE LDG ON FARM FIELD.

Aircraft

Registration
N5775A
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.