UNK64X3773

NTSB accident investigation · Piper PA28 · Kingston, OK · September 4, 1964

Accident · No injuriesClosed
Date
September 4, 1964
Place
Kingston, OK · KINGSTON, OK
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8702WPiper PA28
Status
Completed · report November 6, 1964
Report
Brief approved by the director
Case key
182037

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-2763   64/9/4    KINGSTON OKLA       PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 50 TOTAL
        TIME - 1745                    N8702W              PX-  0  0  0  BUSINESS                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - LAKE TEXOMA PARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           MISCELLANEOUS - EVASIVE MANEUVER TO AVOID COLLISION
        REMARKS- HORSE RAN ONTO RUNWAY.

Aircraft

Registration
N8702W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lake Texoma Park

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.