NYC72FHM34

NTSB accident investigation · Piper PA-28 · Teterboro, NJ · March 2, 1972

Accident · No injuriesClosed
Date
March 2, 1972
Place
Teterboro, NJ · TETERBORO, NJ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N5467SPiper PA-28
Status
Completed · report November 9, 1972
Report
Brief approved by the director
Case key
165826

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-0645   72/3/2    TETERBORO,NJ        PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             PRIVATE, AGE 30, 146
        TIME - 1645                    N5467S              PX-  0  0  0  TRAINING                  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - TETERBORO
        DEPARTURE POINT             INTENDED DESTINATION
          TETERBORO,NJ                LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: PARKED AIRCRAFT                           TAXI: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER STARTING PROCEDURES
        REMARKS- STRUCK BELLANCA N7330V,SUBSTANTIAL DMG.THROTTLE FULL OPEN.

Aircraft

Registration
N5467S
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Teterboro

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.