NYC67F0022

NTSB accident investigation · Fairchild KR34 · Dahlgren, VA · May 20, 1966

Accident · No injuriesClosed
Date
May 20, 1966
Place
Dahlgren, VA · DAHLGREN, VA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N30MFairchild KR34
Status
Completed · report August 16, 1966
Report
Brief approved by the director
Case key
171810

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-1586  66/5/20    DAHLGREN VA         FAIRCHILD KR34      CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 837
        TIME - 1415                    N30M                PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NAF DAHLGREN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N30M
Reported as
Fairchild KR34
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Naf Dahlgren

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.