CHI67D0308

NTSB accident investigation · Piper PA-24 · Danville, KY · October 21, 1966

Accident · No injuriesClosed
Date
October 21, 1966
Place
Danville, KY · DANVILLE, KY
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N6176PPiper PA-24
Status
Completed · report February 1, 1967
Report
Brief approved by the director
Case key
120330

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-3573  66/10/21   DANVILLE KY         PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 65, 923
        TIME - 1530                    N6176P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 173 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - GOODALL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- PILOT WAS OVER CAUTIOUS SINCE SHE HAD PREVIOUSLY OVERSHOT THIS RUNWAY.

Aircraft

Registration
N6176P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Goodall

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.