MIA90FA049 · Lockheed L1329
Lockheed L1329 · Accident: airframe, component or system failure during takeoff
From an unrecorded airport to Dallas Love Field (DAL)
Event
- NTSB case
- MIA90FA049
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Lockheed L1329
- Aircraft type
- Lockheed L1329
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N96GS
- Operator
- Tokoph, David · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Dallas Love Field (DAL), Dallas, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff · roll/run
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Abort above v1, performed
Approximate · Estimated position: the centre of Miami, FL, the place the record names. Not the accident site.
NTSB narrative
FLT WAS A 3-ENG FERRY WITH THE #4 ENG SHUT DOWN. DURING TAKEOFF ROLL AT V1 THE #2 ENG OVERHEAT LIGHT CAME ON. ACCORDING TO THE COPILOT THE PILOT REDUCED THROTTLE SLIGHTLY AND CONTINUED THE TAKEOFF. AFTER LIFT-OFF THE PILOT ABORTED THE TAKEOFF. THE AIRPLANE COULD NOT BE STOPPED ON THE REMAINING RUNWAY AND COLLIDED WITH ANTENNAS, APPROACH LIGHTS AND A CONSTRUCTION SITE 1,180 FT FROM THE DEPARTURE END OF THE RUNWAY. POST-CRASH EXAM OF THE 3 OPERATING ENGS DID NOT REVEAL ANY EVIDENCE OF MECHANICAL FAILURE OR MALFUNCTION. A FAILED RESISTOR WAS FOUND IN THE #2 ENG ELECTRONIC ENGINE CONTROL (EEC). THIS WOULD CAUSE THE UNIT TO OVER-SCHEDULE FUEL TO THE ENG RESULTING IN HOTTER ENG OPERATING TEMPERATURES. RETARDING THE THROTTLE WOULD REDUCE FUEL FLOW TO WITHIN NORMAL RANGES FOR ENG OPERATION. UNDER CONDITIONS THAT EXISTED AT THE TIME OF THE ACCIDENT, THE AIRPLANE WOULD HAVE A 3-ENG RATE-OF-CLIMB OF 1,398 FPM, AND A 2-ENG RATE-OF-CLIMB OF 350 FPM.
Probable cause
THE PILOT'S IMPROPER DECISION TO REJECT THE TAKEOFF AFTER THE AIRPLANE HAD PASSED V1 SPEED AND LIFTED OFF THE RUNWAY. A FACTOR WAS A MALFUNCTIONING #2 ENGINE ELECTRONIC ENGINE CONTTROL WHICH CAUSED THE UNIT TO OVER-SCHEDULE FUEL TO THE ENGINE RESULTING IN HOTTER OPERATING TEMPERATURES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA90FA049
- Event ID
- 20001212X22448
- Case number
- MIA90FA049
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 0505e7044b185a427e82eb276a25f4b033dd339a001b26b9b2e5acf6c590727a; retrieved 2026-09-21T03:02:57.157Z.