MKC68F0208

NTSB accident investigation · Piper PA-14 · Bemidji, MN · August 24, 1967

Accident · No injuriesClosed
Date
August 24, 1967
Place
Bemidji, MN · BEMIDJI, MN
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N5158HPiper PA-14
Status
Completed · report December 20, 1967
Report
Brief approved by the director
Case key
113884

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-3727  67/8/24  NR.BEMIDJI,MINN       PIPER PA-14         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 21, 423
        TIME - 0925                    N5158H              PX-  0  0  2  BUSINESS                  TOTAL HOURS, 120 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BEMIDJI
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: CONTROLLED                  TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING
        REMARKS- FLOAT EQUIPPED.WING TIP/FLOAT STRUCK LAKE IN LOW,LEFT CLIMBING TURN.

Aircraft

Registration
N5158H
Reported as
Piper PA-14
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Bemidji

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.