FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA350 · Wilderoder GREAT LAKES 2TIA

23 Jul 2014 · Lillian, AL, United States

Wilderoder GREAT LAKES 2TIA · Accident: loss of engine power (total) while maneuvering

From Roscoe Field (82J) to Roscoe Field (82J)

Report a problem

Event

NTSB case
ERA14FA350
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

Wilderoder GREAT LAKES 2TIA

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
N47149
Operator
Dean J Legidakes Sr · private individual
Onboard fatalities
Unknown
Route
From Roscoe Field (82J), Pensacola, FLTo Roscoe Field (82J), Pensacola, FL
Aircraft age
About 36 years (built 1978)
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
Maneuvering · low-altitude flying
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
  • Environmental issues › Conditions/weather/phenomena

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

NTSB narrative

The pilot of the experimental, amateur-built airplane completed one 15-minute local flight with a passenger onboard. During a second 15-minute local flight with a different passenger, two witnesses near the accident site observed the airplane flying about 500 ft above ground level. They did not notice anything unusual about the flight and diverted their attention. The airplane was subsequently reported overdue and located about 6 hours later.

The airplane impacted wooded swampy terrain in a level attitude on a heading consistent with the closest airport. A strong smell of fuel at the accident site indicated the presence of fuel at impact. There was no evidence of pilot incapacitation. Examination of the wreckage did not reveal any preimpact mechanical malfunctions with the exception of the left magneto, which would not produce spark. Although records indicated the magnetos were overhauled within 2 years of the accident, laboratory examination of the left magneto revealed that its internal components were worn and near their life limit, which was not consistent with an overhaul during the previous 2 years. The points also did not make contact when closed. The investigation was unable to determine if the pilot performed a preflight check of the magnetos before departing on the accident flight or the preceding flight.

Additionally, the mechanic who maintained the airplane stated that about 6 months before the accident, the left exhaust manifold was sent out for repair due to cracking. To prevent further cracking, the repair facility installed ball joints; however, the carburetor heat shroud had to be reduced by about half-size to facilitate the modification. The reduced carburetor heat shroud would have resulted in a corresponding reduction in carburetor heat capability. A review of a carburetor icing chart revealed that, for the given temperature and dew point, atmospheric conditions were conducive to the formation of "serious icing" at engine glide power settings. The previous passenger reported that part of the scenic flight included a reduction in engine power to idle and a gliding descent. The carburetor heat control was found in the "ON" position. It was likely that an inoperative magneto and possible carburetor ice accumulated while gliding that the carburetor heat system was unable to melt resulted in a loss of engine power and forced landing into the swamp.

Probable cause

A loss of engine power due to an inoperative magneto and possible carburetor ice, which resulted in a forced landing into unsuitable terrain. Contributing to the accident was an inadequate magneto overhaul by unknown personnel and the modification to the carburetor heat system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA350
Event ID
20140723X03322
Case number
ERA14FA350
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: 050cba10343fd46feeda5477efaf4ca348667831cb722b8a10b271b6928562e6; retrieved 2026-09-14T17:22:21.824Z.