NYC68I0033

NTSB incident investigation · Cessna 172 · Flushing, NY · August 28, 1967

Incident · No injuriesClosed
Date
August 28, 1967
Place
Flushing, NY · FLUSHING, NY
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N8819UCessna 172
Status
Completed · report November 7, 1967
Report
Brief approved by the director
Case key
113417

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.

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
----------------------------------------------------------------------------------------------------------------------------
5-0006  67/8/28    FLUSHING,NY         CESSNA 172          CR-  0  0  1  COMMERCIAL                COMMERCIAL, AGE 29, 210
        TIME - 1535                    N8819U              PX-  0  0  2  AIR TAXI-PASSG            TOTAL HOURS, 40 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        CLASSIFIED AS INCIDENT
        NAME OF AIRPORT - LAGUARDIA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           TURBULENCE                                               TAXI: FROM LANDING
           NOSE OVER/DOWN                                           TAXI: FROM LANDING
        REMARKS- N8819U ENCOUNTERED JET-BLAST OF TAXIING BOEING 727. PLT N8819U DID NOT SEE 727 PRIOR TO ENCOUNTER.

Aircraft

Registration
N8819U
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Laguardia

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.