UNK65X0256

NTSB accident investigation · Volaire 10 · Diggs, VA · October 12, 1964

Accident · No injuriesClosed
Date
October 12, 1964
Place
Diggs, VA · DIGGS, VA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N6663DVolaire 10
Status
Completed · report November 25, 1964
Report
Brief approved by the director
Case key
181482

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-3206  64/10/12   DIGGS VA            VOLAIRE 10          CR-  0  0  1  COMMERCIAL                COMMERCIAL, AGE 37, 15000
        TIME - 0645                    N6663D              PX-  0  0  0  FISH SPOTTING             TOTAL HOURS, 1200 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT -                 Z
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
          PILOT-FAILED TO REMOVE FROST FROM THE WINGS.

Aircraft

Registration
N6663D
Reported as
Volaire 10
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Z

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.