MIA04LA124 · Cessna 550
Cessna 550 · Accident: undershoot on approach
From Treasure Coast International Airport (KFPR) to Venice Municipal Airport (KVNC)
Event
- NTSB case
- MIA04LA124
- 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
- 0 · 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 550
- Aircraft type
- Cessna 550
- 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
- N792MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Treasure Coast International Airport (KFPR), Ft. Pierce, FLTo Venice Municipal Airport (KVNC)
- 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 final
- 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
- Undershoot
- 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/mush
- 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, not maintained
- Pilot in command › Distance/altitude, misjudged
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 and copilot stated that during the flight and approach to the airport several cells of thunderstorms were observed of which one was a few miles from the airport. There was light rain after the accident landing and about 30 minutes later heavy showers were observed. The pilot stated the final approach was well established with no major correction for speed or attitude, gear down and full flaps were selected. At last glance to the airspeed, there was an indication of 105 knots. While approaching the threshold, there was a sensation that a tailwind or a downdraft was occurring, at which time the sink rate dramatically increased and before any correction was possible the airplane had already touchdown about 30 feet short of the runway. The airplane traveled another 1,500 feet down the runway before coming to a stop. At the time, he believed the main tires had blown due to him still having directional control of the airplane during the landing roll on the runway. Following the accident landing, an exterior inspection of the accident airplane revealed the flaps had been damaged. The left and right main landing gear had punctured through the top of the wings and the belly of the airplane had been dragged while the nose landing gear stayed partially intact. A witness stated he saw the aircraft on final approach low and slow at an almost level flight attitude, no flare or very little flare. The airplane landed hard and solid. A loud noise and smoke followed as the airplane slid down the runway. The data retrieved from the DFDR indicated that the airplane was descending through an indicated altitude of 1,450 feet, on an indicated heading of 226 degree, and an indicated airspeed of 146 knots. The airplanes heading changed to 135 degree as the airplane descended through 225 feet, and the indicated airspeed read 95 knots. As the airplane descended, the indicated airspeed was between 95 to 90 knots for about 15 seconds. The last five seconds of the flight, the indicated airspeed decreased to 83 knots. The last recorded data on the DFDR read that the airplane was on an indicated heading of 137 degree, indicated airspeed of 83 knots, and recorded a vertical acceleration of 4 g. At the time of the accident the airplane had several interior items removed. The weight and balance calculation sheet for that flight was not submitted for the investigation by the operator of the airplane. The pilot stated the airplane had 3,600 pounds of fuel on board at time of departure. Reference to Cessna's Section IV-Performance Standard Charts for stall speeds for the model 550, with full flaps and landing gear extended, a non-banked stall speed at 12,000 pounds gross weight is 80 knots calibrated airspeed.
Probable cause
The pilot's failure to maintain adequate airspeed which resulted in a stall and undershoot of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA04LA124
- Event ID
- 20040902X01346
- Case number
- MIA04LA124
- 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: 57c4d46fb9e3dae02876b97f74193017606fade1dcc72f453981dd1659b7bde3; retrieved 2026-09-22T06:50:50.963Z.