FTW67F0247

NTSB accident investigation · Piper PA-24 · Oklahoma City, OK · October 13, 1966

Accident · No injuriesClosed
Date
October 13, 1966
Place
Oklahoma City, OK · OKLAHOMA CITY, OK
Injuries
5 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7483PPiper PA-24
Status
Completed · report December 1, 1966
Report
Brief approved by the director
Case key
121281

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-2848  66/10/13   OKLAHOMA CITY OKL   PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 52, 1200
        TIME - 1550                    N7483P              PX-  0  0  4  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 900 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - EXPRESSWAY JUNCTN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - ELECTRICAL FAILURE
        REMARKS- ALTERNATOR FAILED, BATTERY DEPLETED.

Aircraft

Registration
N7483P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Expressway Junctn

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.