ATL92FA091 · Cessna 310R
CFF Air Cessna 310R · Accident: in flight encounter with weather en route
From 6A0 · Cartersville, GA to Greeneville Municipal Airport (GCY)
Event
- NTSB case
- ATL92FA091
- 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
- General aviation
- 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 310R
- Aircraft type
- Cessna 310
- 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
- N3221M
- Operator
- CFF Air
- Onboard fatalities
- Unknown
- Route
- From 6A0 · Cartersville, GATo Greeneville Municipal Airport (GCY), Greeneville, TN
- 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 91: General Aviation
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Proper altitude, not attained
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE INSTRUMENT-RATED COMMERCIAL PILOT WAS MAKING A PERSONAL, CROSS COUNTRY FLIGHT. THERE WAS NO FLIGHT PLAN FILED, NOR WERE THERE ANY RADIO COMMUNICATIONS WITH THE FLIGHT PRIOR TO THE ACCIDENT. THE AIRCRAFT COLLIDED WITH THE SIDE OF A MOUNTAIN NEAR CLINGMANS DOME, TN, AT AN ALTITUDE OF ABOUT 5,800 FEET. THE WRECKAGE WAS SCATTERED UPHILL, AND DAMAGE TO TREES WAS INDICATIVE OF A CLIMBING, WINGS LEVEL ATTITUDE AT IMPACT. NO EVIDENCE OF MECHANICAL FAILURE OR MALFUNCTION WAS FOUND DURING THE WRECKAGE EXAMINATION. A MEMBER OF THE LOCAL CAP SQUADRON REPORTED THAT THE AREA OF THE CRASH SITE WAS OBSCURED IN CLOUDS AND FOG AT THE TIME OF THE ACCIDENT.
Probable cause
THE PILOT'S CONTINUED VFR FLIGHT INTO IMC, AND HIS FAILURE TO ATTAIN A PROPER ALTITUDE OVER HIGH, MOUNTAINOUS TERRAIN. FACTORS WERE THE HIGH TERRAIN, AND THE FOG, CLOUDS, AND OBSCURATION AT THE ACCIDENT SITE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92FA091
- Event ID
- 20001211X14368
- Case number
- ATL92FA091
- 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: d7dcb1ba7ecde32063e5a74394af6ee28159b502ccb4ced3ec35d9ebb5bf7a9a; retrieved 2026-09-21T01:14:15.116Z.