Mid Atlantic Freight Cessna 208B accident
Cessna 208B · Accident: loss of control in flight en route
From Mobile Downtown Airport (BFM) to Montgomery Regional (Dannelly Field) Airport (MGM)
Event
- NTSB case
- ATL03FA008
- 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
- 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 208B
- Aircraft type
- Cessna 208
- 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
- N76U
- Operator
- Mid Atlantic Freight
- Onboard fatalities
- Unknown
- Route
- From Mobile Downtown Airport (BFM), Spanish Fort, ALTo Montgomery Regional (Dannelly Field) Airport (MGM), Montgomery, AL
- 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 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
- 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
- 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
- Pilot in command › Spatial disorientation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
!! NOTE: THIS REPORT WAS MODIFIED ON JANUARY 10, 2006. !!
The airplane was destroyed by impact forces. There was no evidence of fire. Wreckage examinations and all recovered wreckage from the impact area revealed no evidence of an in-flight collision or breakup, or of external contact by a foreign object. An examination of the engine and the propeller indicated that the engine was producing power at impact. The recovered components showed no evidence of preexisting powerplant, system, or structural failures.
Wreckage examinations showed crushing and bending consistent with a moderate angle of descent and a moderate right-wing-down attitude at impact. The amount of wreckage recovered indicates that all parts of the airplane were at the crash site. The wreckage was scattered over an area of about 600 feet.
An examination of radar and airplane performance data indicated that the accident airplane initiated a descent from 3,000 feet immediately after the accident pilot was given a second traffic advisory by air traffic control. The pilot reported that the traffic was above him. At the time the pilot stated that he needed to deviate, data indicate that the accident airplane was in or entering an uncontrolled descent.
Radar data indicated that, after departure from the airport, the closest identified airplane to the accident airplane was a DC-10, which was at an altitude of about 4,000 feet. The horizontal distance between the two airplanes was about 1.1 nautical miles, and the vertical distance between the airplanes was about 1,600 feet. The accident airplane was never in a location at which wake turbulence from the DC-10 would have intersected the Cessna's flightpath (behind and below the DC-10's flightpath). Given the relative positions of the accident airplane and the DC-10, wake turbulence was determined to not be a factor in this accident.
Although the DC-10 was left of the position given to the pilot by Mobile Terminal Radar Approach Control, air traffic controllers do not have strict angular limits when providing traffic guidance.
The Safety Board's airplane performance simulation showed that, beginning about 15 seconds before the time of the pilot's last transmission ("I needed to deviate, I needed to deviate"), his view of the DC-10 moved diagonally across the windscreen from his left to straight in front of the Cessna while tripling in size. The airplane performance simulation also indicated that the airplane experienced high bank and pitch angles shortly after the pilot stated, "I needed to deviate" (about 13 seconds after the transmission, the simulation showed the airplane rolling through 90° and continuing to roll to a peak of about 150° 3 seconds later) and that the airplane appeared to have nearly recovered from these extreme attitudes at impact. Performance data indicated that the airplane would had to have been structurally/aerodynamically intact to reach the point of ground impact from the point of in-flight upset.
There was no evidence of any other aircraft near the accident airplane or the DC-10 at the time of the accident. Soon after the accident, U.S. Coast Guard aircraft arrived at the accident scene. The meaning of the pilot's statement that he needed to deviate could not be determined. A review of air traffic control radar and transcripts revealed no evidence of pilot impairment or incapacitation before the onset of the descent and loss of control.
A sound spectrum study conducted by the Safety Board found no evidence of loud noises during the pilot's last three radio transmissions but found that background noise increased, indicating that the cockpit area was still intact and that the airspeed was increasing. The study further determined that the overspeed warning had activated, which was consistent with the performance study and extreme fragmentation of the wreckage.
Radar transponder data from the accident airplane were lost below 2,400 feet. The signal loss was likely caused by unusual attitudes, which can mask transponder antenna transmissions. A garbled transponder return recorded near the DC-10 was likely caused by the accident airplane's transponder returns masking the DC-10's returns (since the accident airplane was projected to be in line between the DC-10 and the ground radar) or by other environmental phenomena.
Red transfer or scuff marks were observed on many pieces of the airplane wreckage, and these marks were concentrated on the lower airframe skin forward of the main landing gear and the nose landing gear area. The Safety Board and four laboratories compared the red-marked airplane pieces to samples of red-colored items found in the wreckage. These examinations determined that most of the red marks were caused by parts of the airplane, cargo, and items encountered during the wreckage recovery. The marks exhibited random directions of motion, and none of the marks exhibited evidence of an in-flight collision with another aircraft. A small piece of black, anodized aluminum found embedded in the left wing was subsequently identified as a fragment from a cockpit lighting dimmer.
The accident occurred at night, with the moon obscured by low clouds. Instrument meteorological conditions prevailed, although visual conditions were reported between cloud layers. The terminal aerodrome forecast reported a possible cloud layer at 3,000 feet. Weather data and observations by the DC-10 pilot indicated that, after flying about 100 to 500 feet above the cloud layer and soon after sighting the DC-10, the accident airplane would have entered clouds.
A number of conditions were present on the night of the accident that would have been conducive to spatial disorientation. For example, no visible horizon references existed between the cloud layers in which the pilot was flying because of the night conditions. In addition, to initiate a visual search and visually acquire the DC-10, varying degrees of eye and head movements would have accompanied the pilot's shifting of attention outside the cockpit. Once the DC-10 was visually acquired by the pilot, it would have existed as a light source moving against an otherwise featureless background, and its relative motion across and rising in the Cessna's windscreen could have been disorienting, especially if the pilot had fixated on it for any length of time. Maneuvering the airplane during this search would likely have compounded the pilot's resultant disorientation.
Probable cause
the pilot's spatial disorientation, which resulted in loss of airplane control. Contributing to the accident was the night instrument meteorological conditions with variable cloud layers.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03FA008
- Event ID
- 20021029X05400
- Case number
- ATL03FA008
- 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 2002-10-24.
- API snapshot SHA-256: c37c69b87722748b13a50eec2dea7cb295f6849c36f86e474f2db7fee684f541; retrieved 2026-09-18T13:03:50.338Z.