FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05FA044 · Cessna 210N

31 Dec 2004 · Weston, FL, United States

Cessna 210N · Accident: in flight collision with terrain/water en route

From Orlando Executive Airport (ORL) to Miami-Opa Locka Executive Airport (OPF)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's operator. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
MIA05FA044
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
Instrument Meteorological Cond

Cessna 210N

Aircraft type
Cessna 210
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
N6195N
Operator
Unknown Possible conflict
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (ORL), Orlando, FLTo Miami-Opa Locka Executive Airport (OPF), Opa Locka, 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 · descent
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
In flight collision with terrain/water
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

A witness who was driving a car westbound on Interstate 75, stated that he observed the lights of an airplane in the night sky, and noted that the airplane descended at a steep descent angle, while proceeding from north to south, and it disappeared below his horizon. The witness further stated at that time it was raining intensely, was very windy, and the visibility had been greatly reduced. Emergency personnel responded, and the wreckage was found in about 3 feet of swamp water and sawgrass. At 1958:28, the pilot communicated with the Fort Lauderdale North Departure Controller, stating, "flight express one zero six level three thousand golf at Opa Locka." At 1957:28, the controller responded, "flight express one oh six fly heading one ah nine zero vectors for Opa Locka." At 1957:32, the pilot acknowledged, saying, "one nine zero degrees express one zero six." At 1959:33, the controller stated "flight express oh one zero six descend and maintain two thousand", and the pilot responded " down to two thousand flight express one oh six." At 2001:15, the controller stated " flight express one zero six contact Miami approach on one two five point five", and at 2001:19, the pilot responded, "twenty five five flight express one oh six." At 2001:51, the pilot stated, "Miami approach flight express one zero six level two thousand", and at 2001:56, the Miami South Departure Radar Controller responded, "flight express one oh six Miami approach good evening." At 2005:27, the controller stated "flight express one oh six Miami, and there was no response. Subsequent attempts by the controller to communicate with the flight yielded negative results. Radar data showed that after receiving instructions to descend and maintain 2000 feet, the pilot maintained 2,000 feet for about 9 seconds. The data then showed the airplane at an altitude of 1,900 feet for about 2 minutes and 25 seconds, after which the data showed the airplane to be in a gradual descent. At 2005:15 the last reliable radar data showed the airplane at 800 feet. The radar data also showed the pilot to be on a near steady southerly heading during the flight leg. The debris field was about 100 yards long, oriented on a southerly direction, and the sawgrass had been slashed consistent with a descent to the northern-most impact point. After recovery from the swamp, postcrash examination of the airframe, flight controls, and engine did not reveal any preaccident anomalies. A weather study conducted by the NTSB showed that at about the time of the accident, cloud bases were near 1,600 feet, and cloud tops were above 7,000 feet, with higher clouds above. The flight visibility was 0 miles in clouds and about 10 miles below the lowest cloud base. Conditions were also determined to be conducive to light turbulence below 5,000 feet, and the weather radar displayed echoes consistent with light rain being present.

Probable cause

The pilot's failure to maintain his assigned altitude, and allowed the airplane to descend for undetermined reasons resulting in an in-flight collision with terrain. Factors in the accident were clouds, rain, and the dark night.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05FA044
Event ID
20050106X00020
Case number
MIA05FA044
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-01-01.
  • API snapshot SHA-256: c1651990918eda933b22c96a2d8ff8b23dfd8146e0caadd83886cc55ab3e702a; retrieved 2026-09-20T18:09:55.896Z.