DEN67D0226

NTSB accident investigation · Helio Acft H-295 · Colo.Springs, CO · February 28, 1967

Accident · No injuriesClosed
Date
February 28, 1967
Place
Colo.Springs, CO · COLO.SPRINGS, CO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6338VHelio Acft H-295
Status
Completed · report August 9, 1967
Report
Brief approved by the director
Case key
118453

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-0641  67/2/28    COLO.SPRINGS,COLO   HELIO ACFT H-295    CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 50, 1000
        TIME - 1100                    N6338V              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 10 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PETERSON FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           MISCELLANEOUS - PROP/JET/ROTOR BLAST
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
        REMARKS- LANDED TOO CLOSE BEHIND LANDING JET AIRCRAFT.

Aircraft

Registration
N6338V
Reported as
Helio Acft H-295
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Peterson Field

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.