FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07FA045 · Beech A36

22 Dec 2006 · Chattanooga, TN, United States

Beech A36 · Accident: in flight collision with object on approach

From Gainesville Regional Airport (GNV) to Chattanooga Metropolitan Airport (Lovell Field) (CHA)

Report a problem

Event

NTSB case
CHI07FA045
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
4 · 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
Visual Meteorological Cond

Beech A36

Aircraft type
Beechcraft 36
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
N3704B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gainesville Regional Airport (GNV), Gainesville, FLTo Chattanooga Metropolitan Airport (Lovell Field) (CHA), Chatanooga, 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
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 › Altitude/clearance, not maintained
  • Pilot in command › Proper climb rate, not obtained/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

The airplane, piloted by an instrument rated private pilot, was destroyed on impact with trees and terrain while being vectored on a missed approach. An instrument flight plan was on file and was activated. Night visual meteorological conditions prevailed at the destination airport at the time of the accident. However, instrument conditions were reported at approach altitudes. In a transmission with the air traffic controller during the flight, the pilot stated he was "disorientated" and he confirmed that the "trouble" was not with the airplane. Plotted radar data showed that the airplane descended below altitudes the airplane was being vectored on and below published altitudes for the precision approach. The air traffic controller cancelled the approach clearance and gave a missed approach clearance to climb. The data showed that the airplane did an undirected 360-degree turn while being vectored and another undirected turn near the accident site. The pilot had accumulated 366 hours of total flight time. He had accumulated 29.1 hours of night flight time, 54.1 hours of simulated instrument flight time, and 14.3 hours of actual instrument flight time. He logged 3.9 hours of actual instrument flight time and four instrument approaches in the six months prior to the accident. The pilot's logbook did not contain an instrument competency check. The recorded weather at the destination was: Wind 210 degrees at 6 knots; visibility 9 statute miles; sky condition few clouds 500 feet, overcast 1,800 feet; temperature 16 degrees C; dew point 14 degrees C; altimeter 29.95 inches of mercury; remarks drizzle began about 27 minutes before the accident and ended about 16 minutes before the accident. An on-scene investigation was conducted and no airframe or engine pre-impact anomalies were detected.

Probable cause

The pilot's reported spatial disorientation which lead to not maintaining altitude/clearance from terrain and not obtaining/maintaining a proper climb rate during the missed approach. Factors were the night, the clouds encountered on approach, and trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07FA045
Event ID
20061227X01848
Case number
CHI07FA045
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 2006-12-23.
  • API snapshot SHA-256: 57d7267746f1951fdf50e90c79ffa3e29b8885a7045566bdf821f5bd34c6ddf1; retrieved 2026-09-20T16:56:45.394Z.