DIA69I0047

NTSB incident investigation · Dornier DO-28D · Baltimore, MD · March 3, 1969

Incident · No injuriesClosed
Date
March 3, 1969
Place
Baltimore, MD · BALTIMORE, MD
Injuries
4 uninjured
Damage
Minor damage
Phase of flight
Enroute
Aircraft
N3180Dornier DO-28D
Status
Completed · report May 13, 1969
Report
Brief approved by the director
Case key
185892

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.

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
----------------------------------------------------------------------------------------------------------------------------
5-0003   69/3/3    BALTIMORE,MD        DORNIER DO-28D      CR-  0  0  2  COMMERCIAL                CERTIFICATE UNKNOWN, AGE
        TIME - 0951                    N3180               PX-  0  0  2  COMMUTER AIR CARRIER      41, UNK/NR TOTAL HOURS,
                                       DAMAGE-MINOR        OT-  0  0  0  AIR TAXI-PASSG S-D        UNK/NR IN TYPE, UNK/NR
                                                                                                   INSTRUMENT RATED.
        CLASSIFIED AS INCIDENT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           MISCELLANEOUS                                            IN FLIGHT: NORMAL CRUISE
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT
                                  UNUSUAL NOISE
        REMARKS- LFT INBOARD FLAP FABRIC SEPARATED.

Aircraft

Registration
N3180
Reported as
Dornier DO-28D
Category
Airplane
Engine
reciprocating
Damage
Minor damage

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.