SEA69D0231

NTSB accident investigation · Piper PA-28R · Friday Harbr, WA · April 26, 1969

Accident · No injuriesClosed
Date
April 26, 1969
Place
Friday Harbr, WA · FRIDAY HARBR, WA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N9448NPiper PA-28R
Status
Completed · report June 24, 1969
Report
Brief approved by the director
Case key
189209

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-1082  69/4/26    FRIDAY HARBR,WASH   PIPER PA-28R        CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 184
        TIME - 1900                    N9448N              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 55 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BLAKELY ISLAND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: ANIMALS                                   TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
          MISC-DEER JUMPED INTO WG.
           MISCELLANEOUS - EVASIVE MANEUVER TO AVOID COLLISION
        REMARKS- PLT PULLED ACFT OFF GRND WHEN DEER RAN ONTO RWY.

Aircraft

Registration
N9448N
Reported as
Piper PA-28R
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Blakely Island

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.