CHI67D0390

NTSB accident investigation · Piper PA-23 · Gladwin, MI · November 16, 1966

Accident · No injuriesClosed
Date
November 16, 1966
Place
Gladwin, MI · GLADWIN, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4264PPiper PA-23
Status
Completed · report March 16, 1967
Report
Brief approved by the director
Case key
119739

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-3896  66/11/16   GLADWIN MICH        PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 32, 389
        TIME - 0100                    N4264P              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 55 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GLADWIN MUNI.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR
           MISCELLANEOUS ACTS,CONDITIONS - CHECKLIST-FAILED TO USE
        REMARKS- ACFT WAS OBSERVED TO MAKE 3-PASSES OVER FIELD BEFORE LANDING.

Aircraft

Registration
N4264P
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Gladwin Muni.

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.