FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA003 · Beech S35

7 Oct 2015 · Knoxville, TN, United States Narrative disagrees

Beech S35 · Accident: VFR encounter with IMC during initial climb

From Knoxville Downtown Island Airport (DKX) to Morristown Regional Airport (MOR)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ERA16LA003
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
0 · 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
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

Beech S35

Aircraft type
Beechcraft 35
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
N449CT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Knoxville Downtown Island Airport (DKX), Knoxville, TNTo Morristown Regional Airport (MOR), Morristown, TN
Aircraft age
About 50 years (built 1965)
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
Initial climb
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
VFR encounter with IMC
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The airplane had been topped off with fuel the day before the accident flight. Early the following day, the pilot arrived at the airport for the visual flight rules flight and completed a preflight inspection, then he and his passenger boarded the airplane. According to the pilot, while taxiing to the runup area for the runway, he listened to the automated weather observation system (AWOS) at the airport and thought he heard that the ceiling was about 200 ft, even though he could "look up at the sky and see stars." He also stated that this was also not compatible with his weather briefings from the night before or earlier the morning of the accident. According to the passenger, the morning of the accident was dark and foggy, and he could not see the sky. He remembered asking the pilot about instrument procedures as he believed the pilot was instrument qualified. The pilot and passenger could only remember the preflight, the engine warmup, the takeoff, and the landing gear retraction. After departure, the airplane impacted trees and vegetation about 10 ft above ground level about 600 ft from the departure end of the runway. The airplane then impacted in an open field in a level attitude with the wing flaps retracted and the landing gear in the up position. Both the pilot and passenger were seriously injured during the impact sequence.

The airport's line service manager arrived at the airport about 20 minutes after the accident occurred and stated that he could not see anything and that it was "zero/zero." The traffic patrol pilot for the local radio station tried to take off to try to locate the airplane, but the visibility was too bad.

There was no record of the pilot receiving a formal weather briefing. Review of the weather conditions before the accident revealed that the National Weather Service had been forecasting fog and low clouds for at least 5 hours before the time of the accident, the AWOS had been reporting 1/4 mile visibility for at least 15 minutes before the accident, and the sun had not yet risen. If the pilot had delayed his departure until midmorning, he would have been able to depart in visual meteorological conditions.

Postaccident examination of the airframe, engine, and recorded engine data did not reveal any preimpact failures or malfunctions that would have precluded normal operation. Examination of the accident site and airplane revealed that the impact with the ground was at high speed with the engine at takeoff power, indicative of the pilot not climbing the airplane after takeoff. It is likely that, during the takeoff from the well-lit runway into a dark sky with no ambient light, the pilot experienced a somatogravic illusion in which he likely sensed that the sudden linear acceleration of the airplane created a pitch-up sensation, when instead the airplane was not climbing or climbing shallowly. It is likely that, with no other visual cues, the pilot became spatially disoriented and pushed the nose down to avoid what he sensed was pitching up too high and impacted the trees at the end of the runway.

Probable cause

The pilot's inadequate preflight weather planning and his improper decision to attempt a visual flight rules flight in night instrument metrological conditions, which resulted in spatial disorientation and subsequent collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA003
Event ID
20151007X51551
Case number
ERA16LA003
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: 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: 1e410b92048611a8a406097d087bc7d35b4d260882f528e8af96f504a53b8693; retrieved 2026-09-16T02:52:09.609Z.