NYC00LA114 · Loomis SIDEWINDER
Loomis SIDEWINDER · Accident: loss of engine power en route
From Cincinnati Municipal Airport Lunken Field (LUK) to Capital City Airport (FFT)
Event
- NTSB case
- NYC00LA114
- 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
- 0 · 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
Loomis SIDEWINDER
- Aircraft type
- Loomis SIDEWINDER
- 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
- N13545
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cincinnati Municipal Airport Lunken Field (LUK)To Capital City Airport (FFT), Frankfort, KY
- 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
- En route · climb to cruise
- 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
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot aborted his first takeoff attempt due to 'engine problems.' He taxied back to the ramp and inspected the brakes, fuel, oil, and the engine. About 15 minutes later, after he could not find any anomalies, he attempted a second takeoff. During the second takeoff, about 200 feet in the air, the engine lost partial power and the airplane impacted terrain. The pilot did not know the flight time, or date of manufacture of the accident engine. He purchased the airplane in 1984 without any records on the engine. According to the engine manufacturer, it was originally produced as a ground power unit for the military, and not certificated for aircraft use. Specifically, the FAA noted that pistons, piston rings, and the connecting rod assembly were ineligible for use in certificated engines. Examination of the engine by a FAA inspector did not reveal the cause of the partial power loss.
Probable cause
A partial power loss for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA114
- Event ID
- 20001212X20902
- Case number
- NYC00LA114
- 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: 41796e907ae2e413dd7255b350f6c84766f435a79b49b34c32de87a3f7d42107; retrieved 2026-09-22T12:58:19.451Z.