MIA69A0065

NTSB accident investigation · Bellanca 17-30 · Daytona Beach, FL · April 12, 1969

Accident · FatalClosed
Date
April 12, 1969
Place
Daytona Beach, FL · DAYTONA BEACH, FL
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Approach
Aircraft
N4868VBellanca 17-30
Status
Completed · report June 9, 1969
Report
Brief approved by the director
Case key
191050

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-0774  69/4/12    DAYTONA BEACH,FLA   BELLANCA 17-30      CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 0102                    N4868V              PX-  1  0  0  PLEASURE/PERSONAL TRANSP  AGE 30, 2000 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            350 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - DAYTONA BEACH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER IFR OPERATION
        REMARKS- PLT DESCENDED BELOW MIN ALT DURING VOR INST APCH TO RNWY.

Aircraft

Registration
N4868V
Reported as
Bellanca 17-30
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Daytona Beach

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.