SEA69F0040

NTSB accident investigation · Piper PA-28 · Friday Harbr, WA · June 23, 1968

Accident · Serious injuriesClosed
Date
June 23, 1968
Place
Friday Harbr, WA · FRIDAY HARBR, WA
Injuries
2 serious
Damage
Destroyed
Phase of flight
Approach
Aircraft
N6308RPiper PA-28
Status
Completed · report December 13, 1968
Report
Brief approved by the director
Case key
118658

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-3539  68/6/23    FRIDAY HARBR,WASH   PIPER PA-28         CR-  0  1  0  NONCOMMERCIAL             COMMERCIAL, AGE 49, 1225
        TIME - 0940                    N6308R              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FRANK GUARD STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: UNMARKED OBSTRUCTIONS

Aircraft

Registration
N6308R
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Frank Guard Strip

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.