MIA04FA037 · Cessna 441
Cessna 441 · Accident: loss of control in flight en route
From Boca Raton Airport (BCT) to PBI · West Palm Beach, FL
Event
- NTSB case
- MIA04FA037
- 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
Cessna 441
- Aircraft type
- Cessna 441
- 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
- N111RC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boca Raton Airport (BCT), Boca Raton, FLTo PBI · West Palm Beach, 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 · cruise
- 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
- Loss of control in flight
- 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
- Stall/spin
- 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
- Pilot in command › Aircraft control, 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 airplane, flown by an airline transport pilot, departed in day visual meteorological conditions for an 18-nautical mile flight from the home base airport to another airport where the pilot planned to conduct a practice instrument approach. The pilot contacted approach control and requested a practice ILS approach. The controller instructed the pilot to proceed northwest bound and maintain 2,500 feet msl. Radar indicated the airplane tracked a northerly heading instead of a northwesterly heading as instructed. The airplane continued on a northerly heading until 1113:48 when it was about 5 miles southwest of the destination airport at 1,900 feet msl with a ground speed of 172 knots. At this point, the controller instructed the pilot to turn southbound and remain clear of Class C airspace. Radar coverage for the next 50 seconds was intermittent. At 1114:29, radar picked up the airplane about 4 miles southwest of the destination airport at 1,800 feet msl, a ground speed of 106 knots, and a heading of 101 degrees. The airplane continued heading east-southeast for about 30 seconds and its ground speed continued to decay. At 1114:58, it entered an abrupt descent, going from 1700 feet to 200 feet in 15 seconds. The last radar return was recorded at 1115:13 and showed the airplane at 200 feet msl, a ground speed of 64 knots, and a heading of 093 degrees. Several witnesses observed the airplane descend in a "flat spin" and impact a shallow canal in a residential area. Examination of the accident site revealed that the airplane impacted the canal in a nearly flat and level attitude. No evidence of any pre-impact mechanical discrepancies with the airframe or engines was found that would have prevented normal operation. Testing of the electronic engine controls revealed that both units were functional, but under some conditions would trip to manual mode. Further investigation determined that the units tripping to manual mode was due to an electrical overstress that failed the same thermistor within each unit. The reason for the electrical overstress or when it occurred could not be determined; however, it is probable it occurred at impact when the units were submerged in water. Even if the units tripped to manual mode in flight, this would only result in the loss of the torque and temperature limiting and propeller synchrophaser systems, meaning the pilot would have to manually adjust the power levers as required to maintain the proper torque and exhaust gas temperature. Post accident toxicology testing of the pilot's blood revealed chlorpheniramine, an over-the-counter sedating antihistamine, at more than ten times higher than the level expected with a typical maximum over-the-counter dose. It is probable that the pilot's performance and judgment were substantially impaired by his very high blood level of chlorpheniramine.
Probable cause
The pilot's failure to maintain aircraft control, which resulted in an inadvertent stall/spin and subsequent uncontrolled descent into a canal. A factor was the pilot's impairment by the drug chlorpheniramine.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA04FA037
- Event ID
- 20040105X00013
- Case number
- MIA04FA037
- 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: 5801f3c704cbfacf1b4c19e78e0214702cbddb9e23877f0879a8b3bde1945161; retrieved 2026-09-20T18:40:06.275Z.