DIA69A0061

NTSB accident investigation · Lockheed 18 · Gaithersburg, MD · May 2, 1969

Accident · No injuriesClosed
Date
May 2, 1969
Place
Gaithersburg, MD · GAITHERSBURG, MD
Injuries
2 uninjured
Damage
Destroyed
Phase of flight
Takeoff
Aircraft
N221PLockheed 18
Status
Completed
Report
Brief approved by the director
Case key
183009

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-1268   69/5/2    GAITHERSBURG,MD     LOCKHEED 18         CR-  0  0  2  MISCELLANEOUS             COMMERCIAL, AGE 39, 1223
        TIME - 1421                    N221P               PX-  0  0  0  FERRY                     TOTAL HOURS, 27 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MONTGOMERY COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
         FIRE AFTER IMPACT

Aircraft

Registration
N221P
Reported as
Lockheed 18
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Montgomery 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.