DEN66F0003

NTSB accident investigation · Pitts Specl · Longmont, CO · May 15, 1965

Accident · Serious injuriesClosed
Date
May 15, 1965
Place
Longmont, CO · LONGMONT, CO
Injuries
1 serious
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N1142Pitts Specl
Status
Completed · report August 19, 1965
Report
Brief approved by the director
Case key
178069

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
----------------------------------------------------------------------------------------------------------------------------
2-0322  65/5/15    LONGMONT COLO       PITTS SPECL         CR-  0  1  0  NONCOMMERCIAL             AIRLINE TRANSPORT, AGE
        TIME - 1500                    N1142               PX-  0  0  0  PLEASURE/PERSONAL TRANSP  32, 4500 TOTAL HOURS, 0
                                       DAMAGE-DESTROYED    OT-  0  0  0                            IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - LONGMONT MUN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: CONTROLLED                  IN FLIGHT: ACROBATICS
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS
          MISC-RESTRICTED USE OF CONTROLS DUE TO PLT SIZE

Aircraft

Registration
N1142
Reported as
Pitts Specl
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Longmont 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.