FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12LA227 · Emeraude CP-301-A

15 Mar 2012 · Niceville, FL, United States

Emeraude CP-301-A · Accident: loss of engine power (total) en route

From Ruckel Airport (FL17) to Yellow River Airstrip (FD93)

Report a problem

Event

NTSB case
ERA12LA227
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
2 · 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

Emeraude CP-301-A

Aircraft type
Emeraude CP-301
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
N718PP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ruckel Airport (FL17), Niceville, FLTo Yellow River Airstrip (FD93), Holt, FL
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
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 (total)
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

  • Aircraft › Aircraft power plant
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot/owner had been in a previous airplane accident which resulted in traumatic brain injuries. Subsequent to that accident, he acquired an experimental amateur-built airplane, which he would only taxi because of his lack of medical clearance. Anticipating a return to medical status, the pilot asked another pilot to serve as pilot in command and fly with him to another airport for the airplane's condition inspection.There were no witnesses to the engine start, taxi time, or takeoff to the north. An air traffic controller at a nearby air force base was contacted by one of the pilots, who reported that the airplane just departed the airport, as was the custom. The controller then attempted to contact the airplane twice to determine the pilots' intentions but received no response. Radar data indicated a brief, primary (skin paint) return at the time, but no track or altitude could be determined. During the initial climb, a witness saw the airplane when it was about halfway down, and about 300 to 400 feet above the runway, and heard a power reduction. The airplane did not turn to return to the runway, but continued straight ahead over trees, and the witness eventually lost the sound of the engine. A motorist subsequently saw the airplane, gliding south, back toward the departure airport with the propeller stopped, before he lost sight of it behind trees. The airplane later impacted trees, wings level, heading eastbound, just north of a new highway.

Because both pilots were ejected from the airplane, it was not possible to determine which pilot had been in which seat or who was flying. The engine had also separated from the main wreckage, which likely altered the positions of the engine controls, including the carburetor heat. Torsional bending of one of the propeller blades, as well as malleable bending (heating) of the exhaust system indicated that the engine was under some power at impact; an examination of the engine did not reveal any malfunctions or failures that would have precluded normal operation. Dark spark plug electrodes were noted and are consistent with a very rich mixture, either from carburetor icing or carburetor heat, or both. Weather data recorded near the time of the accident indicated an outside air temperature of 82 degrees F and a dew point of 64 degrees. Carburetor icing probability charts indicated the likelihood of serious carburetor icing at glide power for the temperature and dew point conditions. Because one of the pilots made a normal departure call, the effects of carburetor ice were probably first noticed subsequent to that call. At some point, the engine lost power and the pilots attempted to turn back toward the airport. They were then likely able to at least regain at least some power, likely by applying carburetor heat, but were too low to recover.

Probable cause

The pilots’ inadequate use of carburetor heat, which resulted in carburetor icing and a subsequent loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12LA227
Event ID
20120315X35524
Case number
ERA12LA227
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. 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: 85d4e5a07ae25314fa8328f63856dd20ea5139bf7d02039c6db0693957caf80c; retrieved 2026-09-13T22:14:33.650Z.