NYC65I0104

NTSB incident investigation · Lockheed 18 · Wheeling, WV · February 14, 1965

Incident · No injuriesClosed
Date
February 14, 1965
Place
Wheeling, WV · WHEELING, WV
Injuries
7 uninjured
Damage
No damage
Phase of flight
Enroute
Aircraft
N678LLockheed 18
Status
Completed · report April 6, 1965
Report
Brief approved by the director
Case key
179713

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-0002  65/2/14  NR.WHEELING W VA      LOCKHEED 18         CR-  0  0  2  NONCOMMERCIAL             COMMERCIAL, AGE UNK/NR,
        TIME - 2027                    N678L               PX-  0  0  5  CORP/EXEC                 4500 TOTAL HOURS, 400 IN
                                       DAMAGE-NONE         OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        CLASSIFIED AS INCIDENT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           FIRE OR EXPLOSION: IN FLIGHT                             IN FLIGHT: NORMAL CRUISE
        COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT.

Aircraft

Registration
N678L
Reported as
Lockheed 18
Category
Airplane
Engine
reciprocating
Damage
No damage
Airport
Wheeling-Ohio Co

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.