MKC68A0072

NTSB accident investigation · Piper PA-22 · Topeka, KS · June 18, 1968

Accident · FatalClosed
Date
June 18, 1968
Place
Topeka, KS · TOPEKA, KS
Injuries
2 fatal, 1 serious
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N1535PPiper PA-22
Status
Completed · report September 16, 1968
Report
Brief approved by the director
Case key
109985

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-2172  68/6/18    TOPEKA,KANS         PIPER PA-22         CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 42, 250
        TIME - 2045                    N1535P              PX-  2  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PHILIP BALLARD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               IN FLIGHT: LOW PASS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
        FACTOR(S)
           TERRAIN - HIGH OBSTRUCTIONS
        REMARKS- STRUCK POWER LINES 60 FT ABOVE RIVER AT DUSK.

Aircraft

Registration
N1535P
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Philip Ballard

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.