FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southern Seaplane Cessna 210L accident

14 Feb 2014 · Clay, AL, United States

Cessna 210L · Accident: loss of control in flight on approach

From Jackson-Medgar Wiley Evers International Airport (JAN) to Birmingham-Shuttlesworth International Airport (BHM)

Report a problem

Event

NTSB case
ERA14FA120
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
Charter & commuter
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 210L

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
N732EJ
Onboard fatalities
Unknown
Route
From Jackson-Medgar Wiley Evers International Airport (JAN), Jackson, MSTo Birmingham-Shuttlesworth International Airport (BHM), Birmingham, AL
Aircraft age
About 38 years (built 1976)
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 135: Air Taxi & Commuter
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 · IFR initial approach
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot departed on the first leg of a revenue flight after the end of civil twilight but diverted to another airport because of adverse weather at the intended destination. Once the weather conditions improved, the pilot departed and proceeded to the first destination where he landed uneventfully; at that time, the pilot had been on duty for about 14 hours. After landing, the pilot did not call the company's director of operations as he was reportedly instructed to do when the flight was dispatched. One witness at the airport reported that the pilot seemed anxious, which the individual attributed to his being late and not because of the weather.

The pilot obtained weather information for the second destination from a friend (who was a flight instructor) and subsequently departed on the visual flight rules (VFR) flight to his second destination. At the time of departure, the destination forecast was a ceiling of 1,500 ft and visibility of 6 miles. After establishing contact with the approach controller, the pilot was informed that the airport was operating under instrument flight rules (IFR). The controller asked the pilot his intention, and the pilot replied that he wanted an IFR clearance. The pilot confirmed with the controller that he was capable and qualified for IFR flight and was provided an IFR clearance.

The pilot was instructed to turn right to intercept the localizer at a 30-degree angle and was cleared for the instrument landing system runway 24 approach. (Postaccident examination confirmed that one navigation receiver was set to that approach.) The airplane then banked left, and, during portions of the turn, the bank rate was three times greater than a standard banked turn, and the pilot began flying in an east-northeasterly direction while descending. The bank angle reduced and was changing at the end of the radar data. About 2 seconds after the last radar return, the pilot stated, "say again for two echo Juliet." This response likely indicated that he was not prepared for the approach clearance instructions or was distracted by cockpit duties. The controller immediately instructed the pilot to level the wings and climb, but there was no reply.

A performance study indicated that the airplane made a left bank of about 60 degrees (a rate of turn of about 11 degrees per second) during the last seconds of flight before it crashed about 0.3 mile from the last radar target. The airplane was fragmented after impacting trees and terrain on a magnetic heading of about 284 degrees. Postaccident examination of the airplane revealed that the flaps and landing gear were retracted, and there was no evidence of preimpact failure or malfunction of the airframe, flight controls, or engine. There were no reported issues with the localizer at the airport following the accident.

Although one witness reported hearing a sputtering sound coming from the engine likely about the time that the flight was being vectored by the air traffic controller on the downwind leg, the pilot did not advise the controller of any problems during that or any subsequent portion of the flight. Additionally, a witness who was located less than 1/2 nautical mile from the accident site reported that the engine sound was steady. Further, a cut portion of tree made by the propeller was consistent with the engine developing power.

Although windshear advisories were in effect and windshear was reported from a flight crew about 29 minutes after the accident, the wind encountered by the airplane at the time of the accident likely would not have caused the pilot to turn in a direction opposite that instructed by the controller. The pilot was reportedly in good health, and his communications with the controller indicated that he likely was not impaired at the time of the accident.

Although the autopilot programmer/computer was too badly damaged to functionally test, the steeply banked turn opposite that instructed by the air traffic controller was likely the result of pilot input and not the result of an autopilot malfunction. The roll servo was tested, and the lowest reported override force was slightly less than the lowest limit. Thus, if the autopilot had commanded greater than 90 percent of a standard-rate turn, the pilot would have been able to easily override the roll servo.

It could not be determined if the engine-driven vacuum pump was operating or the standby vacuum system was engaged; however, the electrically driven instruments, such as the turn coordinator, and flight instruments consisting of the airspeed indicator, altimeter, and vertical speed indicator would have provided the pilot with roll and pitch information.

Although the pilot was instrument-rated and had recently passed his instrument proficiency check, he was only qualified to fly VFR in revenue operations. He was also not current to fly at night, which was unknown to company personnel at the time of dispatch. In addition, although the flights could have been completed within the pilot's duty day if there were no delays, company personnel should have recognized that weather was causing delays and that the pilot was continuing to fly beyond his duty day. Thus, the company's dispatch procedures were lacking in that they allowed the pilot to fly in night, instrument meteorological conditions beyond his duty day, and company personnel were seemingly unaware that he initiated the flight and was not current to fly at night.

Probable cause

The pilot's failure to maintain control of the airplane while being vectored to intercept the localizer during night instrument meteorological conditions (IMC). Contributing to the accident was the operator's inadequate dispatch procedures, which did not prevent the pilot from flying beyond his duty day, flying at night for which he was not current, or flying in IMC for which he was not qualified by the company.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA120
Event ID
20140215X74539
Case number
ERA14FA120
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2014-02-15.
  • API snapshot SHA-256: 854324d05db271e9c18ee75f68c6b32dda7009bf9674b775287bfbabc800cc46; retrieved 2026-09-14T16:10:31.434Z.