SEA67D0310

NTSB accident investigation · Piper PA-28 · Horsebend, ID · April 24, 1967

Accident · Minor injuriesClosed
Date
April 24, 1967
Place
Horsebend, ID · HORSEBEND, ID
Injuries
3 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N7512RPiper PA-28
Status
Completed · report September 7, 1967
Report
Brief approved by the director
Case key
117036

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-1330  67/4/24    HORSEBEND,ID        PIPER PA-28         CR-  0  0  3  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1600                    N7512R              PX-  0  0  0  DUAL                      AGE 25, 930 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            475 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           MISCELLANEOUS ACTS,CONDITIONS - FLEW INTO BLIND CANYON

Aircraft

Registration
N7512R
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.