MIA67F0104

NTSB accident investigation · Piper PA-22 · Lake City, FL · March 17, 1966

Accident · Serious injuriesClosed
Date
March 17, 1966
Place
Lake City, FL · LAKE CITY, FL
Injuries
1 serious, 3 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N7619DPiper PA-22
Status
Completed · report September 29, 1966
Report
Brief approved by the director
Case key
174184

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
----------------------------------------------------------------------------------------------------------------------------
2-0293  66/3/17    LAKE CITY FLA       PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 130
        TIME - 1900                    N7619D              PX-  0  1  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 25 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - BECAME LOST/DISORIENTED
           TERRAIN - HIGH OBSTRUCTIONS
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING OFF AIRPORT
                                  LOW ON FUEL
                                  APPROACHING DARKNESS

Aircraft

Registration
N7619D
Reported as
Piper PA-22
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.