CEN16FA241 · Boeve Earl SEAWIND
Boeve Earl SEAWIND · Accident: loss of engine power (partial) en route
From Lake County Airport (LXV) to Central Colorado Regional Airport (AEJ)
Event
- NTSB case
- CEN16FA241
- 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
- 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
Boeve Earl SEAWIND
- Aircraft type
- Boeve Earl SEAWIND
- 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
- N46EB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake County Airport (LXV), Leadville, COTo Central Colorado Regional Airport (AEJ), Buena Vista, CO
- Aircraft age
- About 10 years (built 2006)
- 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 · cruise
- 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
- Loss of engine power (partial)
- 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
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
- Personnel issues › Task performance
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 was making a personal flight in the experimental amateur-built airplane. A witness at the destination airport reported hearing the pilot declare a "mayday" on the airport's common traffic advisory frequency, but the pilot did not state the nature of the emergency. Witnesses near the accident site reported hearing the airplane's engine running extremely rough and seeing the airplane's wings rocking back and forth. The accident site was in an open, flat field with sparse vegetation and ample area in which to make a forced landing. Examination of the wreckage indicated that the airplane impacted the ground and nosed over, and a fire then erupted which consumed most of the airplane. Fire damage precluded a complete examination of the airframe, engine, and systems; however, the examinations that were performed did not reveal any preimpact anomalies. Based on the available evidence, it is likely that the airplane's engine lost partial power for a reason that could not be determined due to the extent of the fire damage, and the pilot did not maintain control of the airplane during the ensuing forced landing.
Probable cause
The pilot's failure to maintain control of the airplane during a forced landing following a partial loss of engine power, which resulted in a hard landing and nose over. The reason for the loss of engine power could not be determined due to the severity of the postimpact fire damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16FA241
- Event ID
- 20160704X70314
- Case number
- CEN16FA241
- 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: eb3b7eeeddf22ef55a6814e813d572530df3f28b08d6e4f10cdaddfd6550e462; retrieved 2026-09-14T21:52:29.000Z.