CHI69F0262

NTSB accident investigation · Piper PA-28 · Burgin, KY · September 3, 1968

Accident · Serious injuriesClosed
Date
September 3, 1968
Place
Burgin, KY · BURGIN, KY
Injuries
1 serious, 1 minor
Damage
Destroyed
Phase of flight
Approach
Aircraft
N7016RPiper PA-28
Status
Completed · report November 27, 1968
Report
Brief approved by the director
Case key
107758

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-3380   68/9/3    BURGIN,KY           PIPER PA-28         CR-  0  1  0  NONCOMMERCIAL             COMMERCIAL, AGE 32, 242
        TIME - 0920                    N7016R              PX-  0  0  1  PRACTICE                  TOTAL HOURS, 82 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - SIMULATED CONDITIONS
           MISCELLANEOUS ACTS,CONDITIONS - AIRCRAFT CAME TO REST IN WATER
        REMARKS- PRACTICING EMERG LDGS.

Aircraft

Registration
N7016R
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.