MKC70D0108

NTSB accident investigation · Piper PA-28 · Bloomfield, NE · July 21, 1969

Accident · No injuriesClosed
Date
July 21, 1969
Place
Bloomfield, NE · BLOOMFIELD, NE
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3670KPiper PA-28
Status
Completed · report September 18, 1969
Report
Brief approved by the director
Case key
170029

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-2351  69/7/21    BLOOMFIELD,NEBR     PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 36, 82 TOTAL
        TIME - 2045                    N3670K              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  HOURS, 16 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BLOOMFIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: RUNWAY OR APPROACH LIGHTS                 LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N3670K
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Bloomfield

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.