NYC69D0260

NTSB accident investigation · Luscombe 8F · Pluckimen, NJ · December 1, 1968

Accident · No injuriesClosed
Date
December 1, 1968
Place
Pluckimen, NJ · PLUCKIMEN, NJ
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N805BLuscombe 8F
Status
Completed · report January 23, 1969
Report
Brief approved by the director
Case key
107332

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-4178   68/12/1   PLUCKIMEN,NJ        LUSCOMBE 8F         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 54, 724
        TIME - 1600                    N805B               PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SOMERSET
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           TAXI: FROM LANDING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF POWERPLANT & POWERPLANT CONTROLS
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT SHOULDERS
        REMARKS- HIT SOFT GRND EDGE OF INTERSECTION OF RNWY AND TAXIWAY.TAXIING TOO FAST.

Aircraft

Registration
N805B
Reported as
Luscombe 8F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Somerset

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.