FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17LA015 · Milholland Kelly D

7 Oct 2016 · Livingston, TX, United States

Milholland Kelly D · Accident: powerplant system/component malfunction/failure on approach

From Sport Flyers Airport (27XS) to OOR · Livingston, TX

Report a problem

Event

NTSB case
CEN17LA015
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
Unknown
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

Milholland Kelly D

Aircraft type
Milholland KELLY
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
N522LM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sport Flyers Airport (27XS), Brookshire, TXTo OOR · Livingston, TX
Aircraft age
About 24 years (built 1992)
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
Approach
Defining eventThe 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
Powerplant system/component malfunction/failure
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot reported that, while on approach for landing in the experimental amateur-built airplane, the engine experienced a total loss of power. The pilot performed a forced landing to a field, during which the airplane sustained substantial damage. An examination of the engine revealed that the left magneto was not producing spark. Further examination of the left magneto revealed signatures consistent with failure of the magneto capacitor. Although the failure of a single magneto would likely result in a partial loss of engine power, the reason for the total loss of engine power experienced on the accident flight could not be determined based on the available information.

Probable cause

A total loss of engine power for reasons that could not be determined based on the available information.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17LA015
Event ID
20161012X54219
Case number
CEN17LA015
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: 599dd66bd00e3118e3e2ba7a273fa5035ee3fc30542f386f1a46e2ca070e3518; retrieved 2026-09-16T04:23:14.174Z.