NYC65F0076

NTSB accident investigation · Piper PA-18 · Essex, MD · March 4, 1965

Accident · Serious injuriesClosed
Date
March 4, 1965
Place
Essex, MD · ESSEX, MD
Injuries
1 serious
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N253TPiper PA-18
Status
Completed · report April 22, 1965
Report
Brief approved by the director
Case key
179789

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
----------------------------------------------------------------------------------------------------------------------------
2-0103   65/3/4    ESSEX MD            PIPER PA-18         CR-  0  1  0  MISCELLANEOUS             COMMERCIAL, AGE 31, 867
        TIME - 1355                    N253T               PX-  0  0  0  TEST                      TOTAL HOURS, 300 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - EASTERN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIRAL                                            IN FLIGHT: CLIMB TO CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INCAPACITATION
           PERSONNEL - MAINTENANCE,SERVICING,INSPECTION: INADEQUATE MAINTENANCE AND INSPECTION
          PILOT-FAILED TO ASSURE EXHAUST LEAK WAS ELININATED
        REMARKS- CARBON MONOXIDE INCAPACATION OF PILOT.

Aircraft

Registration
N253T
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Eastern

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.