Casualties unknown

1982-12-30: Cessna 310R (N4055C) — Skytel Aviaton, Inc. — Ft. Lauderdale, FL

Ft. Lauderdale, FL, US

On December 30, 1982, a Cessna 310R (registration N4055C) operated by Skytel Aviaton, Inc. was involved in an aviation accident near Ft. Lauderdale, FL. Investigators recorded the probable cause as: The pilot's failure to maintain control of the aircraft during an attempted return to the airport, resulting in a high-speed, excessive-rate descent that was inconsistent with normal or emergency landing procedures. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 1781061362Data APIEditorial standards

An aircraft crashed shortly after takeoff while the pilot appeared to be attempting an emergency return to the airport. The landing gear was lowered, but no radio calls were made.

What happened

The aircraft departed from the airport and subsequently crashed in close proximity to the departure point. During the flight, the pilot appeared to be attempting to return to the airport for a landing shortly after takeoff. Notably, the landing gear was observed in the lowered position, suggesting an intention to land. However, there is no record of any radio communications being made by the pilot during this period.

The flight path and speed were inconsistent with a controlled approach or a standard emergency procedure. The aircraft exhibited a high airspeed combined with an excessive rate of descent. These parameters do not align with the actions typically taken by a qualified pilot attempting to execute a safe landing, whether under normal conditions or during an emergency situation.

The investigation

Investigators examined the wreckage and the flight dynamics leading up to the impact. A thorough review was conducted to identify any mechanical failures or system discrepancies that could have contributed to the abnormal flight pattern. Despite extensive checks, no malfunctions or mechanical issues were found that would explain the pilot's actions or the aircraft's behavior.

Findings

The primary factors contributing to the accident include the high speed and excessive rate of descent during the attempted return. The absence of radio calls suggests a lack of communication with air traffic control or other aircraft, which is unusual for an emergency situation. The inability to find any mechanical faults points toward pilot error or an unexplained loss of control as the likely cause.

Safety message

Pilots should ensure that all pre-flight checks are completed and that they are fully prepared for any potential emergencies. Clear communication with air traffic control is essential during any abnormal situation to assist in resolving issues safely.

Probable cause

The pilot's failure to maintain control of the aircraft during an attempted return to the airport, resulting in a high-speed, excessive-rate descent that was inconsistent with normal or emergency landing procedures.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20020917X04913. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.