UNK64X4047

NTSB accident investigation · Cessna 172 · Hagerstown, MD · September 19, 1964

Accident · Minor injuriesClosed
Date
September 19, 1964
Place
Hagerstown, MD · HAGERSTOWN, MD
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N3703SCessna 172
Status
Completed · report November 12, 1964
Report
Brief approved by the director
Case key
181211

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-2951  64/9/19    HAGERSTOWN MD       CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 39, 39 TOTAL
        TIME - 1100                    N3703S              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HAGERSTOWN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: ABORTED
           GEAR COLLAPSED                                           TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3703S
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Hagerstown

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.