MIA68F0046

NTSB accident investigation · Cessna 210 · Atlanta, GA · June 17, 1967

Accident · No injuriesClosed
Date
June 17, 1967
Place
Atlanta, GA · ATLANTA, GA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3755YCessna 210
Status
Completed · report September 27, 1967
Report
Brief approved by the director
Case key
116167

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-2073  67/6/17    ATLANTA,GA          CESSNA 210          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 34, 353
        TIME - 0918                    N3755Y              PX-  0  0  2  BUSINESS                  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FULTON COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR
        FACTOR(S)
           AIRFRAME - LANDING GEAR: LANDING GEAR WARNING AND INDICATING COMPONENTS
        REMARKS- LNDG GEAR WARNING HORN INOPERATIVE.

Aircraft

Registration
N3755Y
Reported as
Cessna 210
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fulton County

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.