FTW67F0659

NTSB accident investigation · Piper PA-12 · Kilgore, TX · May 27, 1967

Accident · Serious injuriesClosed
Date
May 27, 1967
Place
Kilgore, TX · KILGORE, TX
Injuries
1 serious
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N3040MPiper PA-12
Status
Completed · report September 20, 1967
Report
Brief approved by the director
Case key
116839

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-0404  67/5/27    KILGORE,TEX         PIPER PA-12         CR-  0  1  0  MISCELLANEOUS             COMMERCIAL, FL.INSTR.,
        TIME - 0828                    N3040M              PX-  0  0  0  FERRY                     AGE 28, 1500 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            UNK/NR IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - KILGORE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           FIRE OR EXPLOSION: IN FLIGHT                             TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT.

Aircraft

Registration
N3040M
Reported as
Piper PA-12
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Kilgore

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.