FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA03FA135 · Cessna 414

26 Jun 2003 · N. Fort Myers, FL, United States

Cessna 414 · Accident: total loss of engine power (non-mechanical) on approach

From Palm Beach County Park Airport (KLNA) to Pine Shadows Airpark (94FL)

Report a problem

Event

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

Cessna 414

Aircraft type
Cessna 414
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
N749AA
Operator
John E. Nowicki Jr · private individual
Onboard fatalities
Unknown
Route
From Palm Beach County Park Airport (KLNA), West Palm Beach, FLTo Pine Shadows Airpark (94FL), Fort Myers, 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
Approach · VFR pattern turn to base
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
Total loss of engine power (non-mechanical)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Fuel starvation; Stall; Tree(s)
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

  • Pilot in command › Airspeed(vs), not maintained

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

NTSB narrative

The pilot reported visually checking the main fuel tanks during his preflight inspection of the airplane and later reported there was enough fuel for the intended flight which would be less than 1 hour, plus a 45-minute reserve amount of fuel. He estimated the fuel level in the main fuel tanks was 2-3 inches from the top. He also reported that before the accident flight he had never flown the accident make and model airplane, and that he had not had any flight training in the airplane. The passengers were boarded, the flight departed and climbed to between 4,500 and 6,500 feet msl. He leaned the mixture during cruise, and the flight continued. He began descending when the flight was 12 miles from the destination airport, and he performed the pre landing checks when the flight was 3 miles from the destination airport. The flight entered left downwind where he lowered the landing gear and turned on the fuel pumps. When abeam the landing point he reduced power, lowered the flaps 10 degrees, and turned onto base leg. During the base leg while rolling out of the turn and flying at 600 feet, "the right engine suddenly came to a stop...." He banked to the left to maintain zero sideslip, pushed the mixture, propeller, and throttle controls full forward, and identified the right engine had failed. He reportedly pulled the right propeller control to the feather position but during the postaccident investigation, the right propeller blades were not in the feather position and there was no evidence of preimpact failure or malfunction of the propeller. The pilot further reported that while pulling the right propeller control to the feather position, the airplane, "began to yaw right and simultaneously bank right...." He moved the left throttle control to idle, and they were on the ground in a span of 6 seconds from the time the right engine quit. No fuel leakage was noted at the scene, and no fuel contamination was noted in a nearby pond. Additionally, only residual fuel was noted in the fuel lines in each engine compartment. A total of 4.0 and 1.5 gallons of fuel were drained from the left and right auxiliary fuel tanks, respectively. No evidence of preimpact flight control failure or malfunction was noted. Neither propeller was at or near the feather range at the time of impact. Both engines were removed from the airplane, placed on a test stand with a "club" propeller, and both engines were noted to operate normally during the engine run. Examination of the right seat in the third row of the airplane revealed the seat frame was bent down on the left side, and all seat feet were in position but distorted; no fracture of the seat feet were noted. Examination of the seat of the passenger who sustained minor injuries (left seat in the third row) revealed the seatpan was compressed down, and the lapbelt was unbuckled. The inboard arm rest was bent inward, and the outboard arm rest was bent outward. The seat frame indicated displacement to the left. The seat back was twisted counter clockwise, and the left forward seat foot was in place. The seat and attach structure was certificated for a maximum forward g loading of 9 g's, and a maximum sideward g loading of 1.5 g's. This does not include a 1.33 margin of safety factor. The seat and attach structure was tested to ultimate loads in a combined forward, sideward, and upward directions in accordance with CAR 3.390-2. The same loads were also applied in a downward direction by itself. The empennage was separated just aft of the aft pressure bulkhead but remained secured by flight control cables. According to personnel from the airplane manufacturer, the tested load (150 percent limit) for the empennage in negative shear translates to 14.0 g loading. Based on Cessna Engineering rough calculations, they believe the empennage is capable of sustaining an additional 30 percent beyond what it was tested to, or an estimated 18.2 g's in negative shear loading.

Probable cause

The failure of the pilot to maintain airspeed (Vs) following a total loss of engine power from the right engine due to fuel starvation, resulting in an inadvertent stall, uncontrolled descent, and in-flight collision with trees and terrain. Factors in the accident was the failure pilot to feather the right propeller following the total loss of engine power, and his lack of total experience in the accident make/model of aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA03FA135
Event ID
20030702X01005
Case number
MIA03FA135
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, 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: 0124b4a4ac2deba05467ab134f0cf2034525ef8351d3f0f202dd720a38ea47c2; retrieved 2026-09-20T19:06:58.775Z.