UNK64X1786

NTSB accident investigation · Stinson 108-3 · Burlington, IA · May 16, 1964

Accident · No injuriesClosed
Date
May 16, 1964
Place
Burlington, IA · BURLINGTON, IA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6103MStinson 108-3
Status
Completed · report September 22, 1964
Report
Brief approved by the director
Case key
183960

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-1294  64/5/16    BURLINGTON IOWA     STINSON 108-3       CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 1050
        TIME - 2330                    N6103M              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 20 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BURLINGTON MUN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - BECAME LOST/DISORIENTED
           MISCELLANEOUS ACTS,CONDITIONS - LANDED AT WRONG AIRPORT
           MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA

Aircraft

Registration
N6103M
Reported as
Stinson 108-3
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Burlington Mun

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.