DIA67F0070

NTSB accident investigation · Cessna 172 · Richmond, VA · April 2, 1967

Accident · Minor injuriesClosed
Date
April 2, 1967
Place
Richmond, VA · RICHMOND, VA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4348LCessna 172
Status
Completed · report August 31, 1967
Report
Brief approved by the director
Case key
117449

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-1065   67/4/2    RICHMOND,VA         CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 56, 697
        TIME - 0745                    N4348L              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 48 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PARNELL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           PILOT IN COMMAND - MISUSED OR FAILED TO USE FLAPS

Aircraft

Registration
N4348L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Parnell

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.