MIA66F0491

NTSB accident investigation · Luscombe 8A · Clearwater, FL · April 12, 1966

Accident · No injuriesClosed
Date
April 12, 1966
Place
Clearwater, FL · CLEARWATER, FL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N45523Luscombe 8A
Status
Completed · report May 10, 1966
Report
Brief approved by the director
Case key
172566

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-0666  66/4/12    CLEARWATER FLA      LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 54, 371
        TIME - 1400                    N45523              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 26 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CLEARWATER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: BUILDING(S)                               TAXI: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - STARTED ENGINE WITHOUT PROPER ASSISTANCE/EQUIPMENT
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - TIEDOWN LINES SNAPPED
        REMARKS- HAND PROPPED ENGINE WITH AIRCRAFT UNOCCUPIED

Aircraft

Registration
N45523
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Clearwater

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.