NYC65F0133

NTSB accident investigation · Cessna 172 · Gaithersburg, MD · April 4, 1965

Accident · No injuriesClosed
Date
April 4, 1965
Place
Gaithersburg, MD · GAITHERSBURG, MD
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7883XCessna 172
Status
Completed · report May 28, 1965
Report
Brief approved by the director
Case key
179075

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-0714   65/4/4    GAITHERSBURG MD     CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 26, 65 TOTAL
        TIME - 1445                    N7883X              PX-  0  0  0  PRACTICE                  HOURS, 4 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MONTGOMERY AIR PK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7883X
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Montgomery Air Pk

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.