DIA69F0080

NTSB accident investigation · Piper PA-31 · Fredericksburg, VA · October 3, 1968

Accident · No injuriesClosed
Date
October 3, 1968
Place
Fredericksburg, VA · FREDERICKSBURG, VA
Injuries
7 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9054YPiper PA-31
Status
Completed · report June 24, 1969
Report
Brief approved by the director
Case key
192187

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-4901   68/10/3   FREDERICKSBURG,VA   PIPER PA-31         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 52, 6307
        TIME - 0710                    N9054Y              PX-  0  0  6  CORP/EXEC                 TOTAL HOURS, 104 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SHANNON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT
        REMARKS- DOOR LATCH NOT FUNCTIONING PROPERLY.

Aircraft

Registration
N9054Y
Reported as
Piper PA-31
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Shannon

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.