FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02FA037 · Cessna 208B

1 Dec 2001 · Bessemer, AL, United States

Cessna 208B · Accident: in flight collision with object on approach

From Bill & Hillary Clinton National Airport/Adams Field (LIT) to Bessemer Airport (KEKY)

Report a problem

Event

NTSB case
MIA02FA037
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 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
N499BA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bill & Hillary Clinton National Airport/Adams Field (LIT), Little Rock, ARTo Bessemer Airport (KEKY), Bessemer, 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
Approach · IFR missed approach
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 object
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
Tree(s)
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 › IFR procedure, initiated
  • Pilot in command › In-flight planning/decision, poor
  • Weather condition › Below approach/landing minimums

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

NTSB narrative

The flight departed from Little Rock, Arkansas, about 2356 cst, and approximately 49 minutes after takeoff, the FAA approved un-augmented Automated Weather Observing System (AWOS-3) installed at the destination airport began reporting the visibility as 1/4 statute mile; the visibility continued to be reported as that value for several hours after the accident. Title 14 CFR Part 135.225 indicates no pilot may begin an instrument approach procedure to an airport with an approved weather reporting facility unless the latest weather report issued by that weather reporting facility indicates that weather conditions are at or above the authorized IFR landing minimums for that airport. The listed minimums for the ILS approach to runway 05 was in part 3/4 mile visibility. A METAR taken at the destination airport approximately 2 minutes after the accident indicated overcast clouds existed at 100 feet, the temperature and dew point were 4 and 2 degrees Celsius, respectively, and the altimeter setting was 30.16 inHg. No precipitation was present across Arkansas, Mississippi, or Alabama, and no radar echoes were noted along the accident airplane's route of flight. The freezing level near the departure and destination airports at the nominal time of 0600 (4 hours 17 minutes after the accident) was 12000 and 14,500 feet mean sea level, respectively. A witness at the airport reported the fog was the thickest he had seen since working at the airport for the previous year. The flight was cleared for an ILS approach to runway 05, and the pilot was advised frequency change was approved. The witness waiting at the airport reported hearing a sound he associated with a shotgun report. Radar data indicated that between 0138:47, and 0142:11, the airplane was flying on a northeasterly heading and descended from 2,400 feet msl, to 900 feet msl. At 0142:11, the airplane was located .43 nautical mile from the approach end of runway 05. The next recorded radar target 24 seconds later indicated 1,000 feet msl, and was .20 nautical mile from the approach end of runway 05. The touchdown zone elevation for runway 05 is 700 feet msl. The airplane crashed in a wooded area located approximately 342 degrees and .37 nautical mile from the approach end of runway 05; the wreckage was located approximately 4 hours after the accident. Examination of trees revealed evidence the airplane was banked to the left approximately 24 degrees, and the descent angle from the trees to the ground was calculated to be approximately 22 degrees. All components necessary to sustain flight were either attached to the airplane or in close proximity to the main wreckage. There was no evidence of post crash fire and a strong odor of fuel was noted at the scene upon NTSB arrival. A 8-inch diameter pine tree located near the initial ground impact sight exhibited black paint transfer and a smooth cut surface that measured approximately 46 inches in length. The bottom portion of the cut was located 4 feet above ground level. The flap actuator was found nearly retracted; examination of the components of the flap system revealed no evidence of preimpact failure or malfunction. Examination of the flight control system for roll, pitch, and yaw revealed no evidence of preimpact failure or malfunction. Examination of the engine and engine components with TSB of Canada oversight revealed no evidence of preimpact failure of the engine or engine components. Examination of the propeller with FAA oversight revealed no evidence of preimpact failure or malfunction. Examination of the components of the autopilot system, selected avionics and flight instruments from the airplane with FAA oversight revealed no evidence of preimpact failure or malfunction. The pilot's attitude indicator had been replaced on October 14, 2001, and according to FAA personnel, the mechanic and facility that performed the installation did not have the necessary equipment to perform the operational checks required to return the airplane to service. The FAA flight checked the ILS approach to runway 05 two times after the accident and reported no discrepancies.

Probable cause

The poor in-flight planning by the pilot-in-command for his initiation of the ILS approach to runway 05 with weather conditions below minimums for the approach contrary to the federal aviation regulations, and the failure of the pilot to maintain control of the airplane during a missed approach resulting in the in-flight collision with trees then terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02FA037
Event ID
20011210X02372
Case number
MIA02FA037
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: 24fbc64fc1cfa999159551186867b1488730a730975818e68eed6bbcb488cad5; retrieved 2026-09-18T13:08:07.862Z.