MIA78FKG38

NTSB accident investigation · Piper PA-22 · Loganville, GA · April 23, 1978

Accident · Serious injuriesClosed
Date
April 23, 1978
Place
Loganville, GA · LOGANVILLE, GA
Injuries
2 serious, 1 minor, 1 uninjured
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N69PKPiper PA-22
Status
Completed · report July 7, 1978
Report
Brief approved by the director
FAA report
19780423010949A
Case key
142424

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-1116  78/4/23    LOGANVILLE,GA       PIPER PA-22         CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 35, 243
        TIME - 1315                    N69PK               PX-  0  1  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 143 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BAY CREEK
        DEPARTURE POINT             INTENDED DESTINATION
          LOGANVILLE,GA               GWINNETT COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
         FIRE AFTER IMPACT

Aircraft

Registration
N69PK
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Bay Creek

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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.