MKC66F0208

NTSB accident investigation · Piper PA-28 · Brainerd, MN · August 24, 1965

Accident · FatalClosed
Date
August 24, 1965
Place
Brainerd, MN · BRAINERD, MN
Injuries
1 fatal, 1 serious, 1 minor
Damage
Destroyed
Phase of flight
Landing
Aircraft
N8248WPiper PA-28
Status
Completed · report December 2, 1965
Report
Brief approved by the director
Case key
176354

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-0631  65/8/24    BRAINERD MINN       PIPER PA-28         CR-  1  1  0  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1300                    N8248W              PX-  0  0  1  DUAL                      AGE 60, 3000 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            UNK/NR IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - CROW WING COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIRAL                                            LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           DUAL STUDENT - IMPROPER LEVEL OFF
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N8248W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Crow Wing County

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.