NYC66F0544

NTSB accident investigation · Aero Comdr 500-B · Hagerstown, MD · February 24, 1966

Accident · Minor injuriesClosed
Date
February 24, 1966
Place
Hagerstown, MD · HAGERSTOWN, MD
Injuries
1 minor, 3 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N9388RAero Comdr 500-B
Status
Completed · report June 22, 1966
Report
Brief approved by the director
Case key
172701

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-1037  66/2/24    HAGERSTOWN MD       AERO COMDR 500-B    CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 34, 5600
        TIME - 1800                    N9388R              PX-  0  0  3  CORP/EXEC                 TOTAL HOURS, 3800 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        NAME OF AIRPORT - HAGERSTOWN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           MISCELLANEOUS ACTS,CONDITIONS - AIRFRAME ICE
        REMARKS- WET SNOW ON RIGHT WING NOT REMOVED.

Aircraft

Registration
N9388R
Reported as
Aero Comdr 500-B
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.