DIA68F0055

NTSB accident investigation · Cessna 310 · Fletcher, NC · September 1, 1967

Accident · No injuriesClosed
Date
September 1, 1967
Place
Fletcher, NC · FLETCHER, NC
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N421MCessna 310
Status
Completed · report November 28, 1967
Report
Brief approved by the director
Case key
114140

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-3098   67/9/1    FLETCHER,NC         CESSNA 310          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 58, 2200
        TIME - 0920                    N421M               PX-  0  0  1  BUSINESS                  TOTAL HOURS, 450 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: MISSED APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER IFR OPERATION
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - INSTRUMENTS-MISREAD OR FAILED TO READ
        REMARKS- GOT OFF CRS DURING ADF APCH.PROCEEDED VFR ON TOP TO CHARLOTTE,NC,LANDED WITHOUT FURTHER DAMAGE.

Aircraft

Registration
N421M
Reported as
Cessna 310
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Asheville

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.