CHI71FEM87

NTSB accident investigation · Piper PA-28 · Riverdale, MI · May 31, 1971

Accident · No injuriesClosed
Date
May 31, 1971
Place
Riverdale, MI · RIVERDALE, MI
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5221LPiper PA-28
Status
Completed · report January 26, 1972
Report
Brief approved by the director
Case key
161393

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-1801  71/5/31    RIVERDALE,MICH      PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 1851
        TIME - 0945                    N5221L              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 5 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LUMBERJACK LAND
        DEPARTURE POINT             INTENDED DESTINATION
          PONTIAC,MICH                RIVERDALE,MICH
        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
        REMARKS- CONTINUED APCH,LNDD.

Aircraft

Registration
N5221L
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lumberjack Land

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.