FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Baron Aviation Services Cessna 208B accident

5 Mar 1998 · Clarksville, TN, United States

Cessna 208B · Accident: in flight encounter with weather en route

From Frederick W. Smith International Airport (MEM) to Bowling Green Warren County Regional Airport (BWG)

Report a problem

Event

NTSB case
MIA98FA091
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
0
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
N840FE
Onboard fatalities
Unknown
Route
From Frederick W. Smith International Airport (MEM), Memphis, TNTo Bowling Green Warren County Regional Airport (BWG), Bowling Green, KY
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
In flight encounter with weather
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
Stall
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 › Stall, inadvertent

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

NTSB narrative

The flight was in radio contact with air traffic controllers at the FAA Memphis Air Route Traffic Control Center (ARTCC), and was level at 9,000 feet, when the pilot checked in on frequency. The last radio contact with the flight was at 0447. At 0520, radar contact was lost. The airplane impacted in rough terrain, at a steep angle of impact. Two other company pilots flying in trail of the accident aircraft said, they had radio contact with the pilot of N840FE about 5 minutes before the accident. They said he sounded fine and did not say anything about any problems. Radar data showing the flight's ground speed indicated that at 0512, the ground speed was 158 knots (182 mph). The ground speed then decreased to 153 (176 mph), 143 (165 mph), 138 (159 mph), and 132 (152 mph), until at 0519:40, when the ground speed of the flight was 125 knots (144 mph). After the radar read out at 0519:40, the next radar hit was coast (no information), and then the flight disappeared from the radar scope. The airplane's heading and altitude did not change during the decrease in ground speed. According to the NTSB Radar Data Study, calculated flight parameters indicated the airplane "...experienced a slow reduction of airspeed in the final 8 minutes of flight at altitude, and then abruptly exhibited a sharp nose down pitch attitude with a rapid increase in airspeed." About the time of the reduction in airspeed, pitch angle began to slowly increase also. When radar contact was lost, the calculated airspeed had reduced to less then 102 knots [118 mph], and calculated body angle of attack [AOA] had increased to 8.8 degrees. A large reduction in pitch angle, angle of attack, and flight path angle as the airspeed increases after peak AOA was reached. Examination of the engine Power Analyzer and Recorder (PAR) revealed that no exceedences were in progress at the time power was removed from the PAR. It was determined that no caution timing events were in progress. The PAR computer appeared to be operating correctly until power was removed at impact. Examination of the airplane's autopilot were not conclusive due to impact damage. Determination of whether the autopilot was engaged or not engaged at the time of the accident could not be determined. The NTSB Meteorological Factual Report revealed that at 0515, about 7 minutes before the flight was lost on radar, the radiative temperature in an area centered at Clarksville (4 kilometer resolution data), showed that the Mean Radiative Temperature was -6.26 degrees C (21F). The Minimum Radiative Temperature was -6.66 degrees C (19F). The Maximum Radiative Temperature was -6.06 degrees C (21F). According to the Archive Level II Doppler weather radar tape for a beginning sweep time of 0508:10, showed that N840FE had tracked into a weather echo from 0510:34, to 0516:28. The Doppler Weather Radar data, revealed that N840FE, had entered a weak weather echo about the same time that the airspeed of the airplane started to decrease, at an altitude of about 9,000 feet, and the airplane was in the weak weather echo for a few minutes. Based on the weather data, it was determined that in-flight airplane icing conditions were encountered by N840FE. Cessna Aircraft Company Airworthiness Directive (AD) 96-09-15; Amendment 39-9591; Docket No. 96-CE-05-AD, applicable to this airplane and complied with by the company, on December 12, 1996, stated: "...to minimize the potential hazards associated with operating the airplane in severe icing conditions by providing more clearly defined procedures and limitations associated with such conditions...operators must initiate action to notify and ensure that flight crewmembers are apprised of this change...revise the FAA-approved Airplane Flight Manual (AFM) by incorporating the following into the Limitation Section of the AFM. This may be accomplished by inserting a copy of this AD in the AFM...." The airplane was equipped with leading edge deicing boots on the wings, elevators, struts, and had a cargo pod deicing capability. Lights were installed to illuminate the leading edge of the wings, to aid the pilot in detecting ice on the leading edges of the wings during night operations. The airplane was not equipped with an ice detection device.

Probable cause

the pilot did not maintain control of the airplane due to undetected airframe ice, resulting in an inadvertent stall, and subsequent impact with the ground. Factors in this accident were; flight into clouds, below freezing temperatures, and the inability of the pilot to detect ice, due to the lack of an ice detection system to determine ice build up on portions of the airframe that are not visible from the cockpit.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA98FA091
Event ID
20001211X09730
Case number
MIA98FA091
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. 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: 3104c30d2785da3273ce74f742245897644c1505ffbbb6b71e8b5cdc81d4aa3b; retrieved 2026-09-18T13:25:33.019Z.