FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI07FA046 · Rockwell International 114

26 Dec 2006 · Jasper, TN, United States

Rockwell International 114 · Accident: in flight encounter with weather during an uncontrolled descent

From Ottawa Executive Airport (Z98) to Marion County Airport - Brown Field (APT)

Report a problem

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

Event

NTSB case
CHI07FA046
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
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

Rockwell International 114

Aircraft type
Rockwell 114
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
N55MB
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Ottawa Executive Airport (Z98), Zeeland, MITo Marion County Airport - Brown Field (APT), Jasper, 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
Uncontrolled descent
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
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
Substantial

Cause areas

  • Pilot in command › Flight into known adverse weather, continued

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 was established at a cruise altitude of 12,000 feet and the pilot did not report any problems during the en route portion of the flight. Upon initial clearance to descend from cruise altitude, the pilot advised the controller that he might have to stay higher due to ice. The pilot was subsequently cleared to 7,000 feet, instead of the initial 4,000 feet. About 15 miles from the destination airport, the pilot was cleared for a Global Positioning System (GPS) approach and instructed to maintain 3,900 feet until reaching the initial approach fix. The pilot subsequently inquired about descending lower and was cleared to 3,600 feet. The pilot commented that the airplane was "picking up some ice here, so we're trying to be real careful." Track data indicated that the airplane continued toward the airport, descending as low as 3,200 feet. However, about 2.25 miles from the airport, the pilot declared a missed approach, stating: "We're picking up too much ice." The flight was cleared to an alternate airport and instructed to climb to 5,000 feet. However, the airplane was unable to climb above 4,500 feet and the pilot reported that the airplane was still picking up ice. The pilot subsequently stated that he was unable to maintain altitude because of "more ice." He requested vectors out of the icing conditions, but the controller was not aware of any area being better regarding icing. The pilot noted he was "losing altitude now pretty good." The pilot selected an intermediate airport that was closer to his present position. The controller cleared the flight as requested and instructed the pilot to maintain 4,000 feet. The pilot replied, "All I can do is 4,000." Track data indicated that the flight was established on an east-southeasterly course, and passed about 0.6 miles south of the intermediate airport. It entered a left turn to a northeast course and passed the airport, apparently intending to return for landing. The airplane impacted trees and terrain about 1.75 miles northeast of the intermediate airport. A witness stated that the airplane came through the treetops, "nose dived into the ground" and spun around, before coming to rest. GPS altitude data revealed a steadily increasing descent rate after reaching 4,500 during the diversion to the alternate. Airmen's Meteorological Information (AIRMET) advisories for moderate icing were in effect. The AIRMET coverage area included the destination and alternate airports. The pilot obtained two pre-flight weather briefings during which he was advised of the AIRMET. Although, the AIRMET was updated after the briefings, the predicted icing intensity and geographical coverage area remained the same. A post accident inspection of the airplane did not reveal any anomalies consistent with a pre-impact failure or malfunction. Several ice fragments, consistent in appearance to rime ice, were observed on the ground at the accident site by initial responders. The fragments exhibited a contour approximately matching the profile of the wing leading edge. The Pilot's Operating Handbook stated that the airplane was not certified for flight into known icing conditions. The handbook advised that in the case of an inadvertent icing encounter, "evasive action should be initiated immediately when icing conditions are first encountered."

Probable cause

The pilot's inability to maintain altitude due to excessive airframe ice accretion, resulting in an in-flight collision with trees and terrain. Additional causes were the pilot's continued flight in icing conditions once they had been encountered, and his failure to promptly initiate evasive action in order to exit the icing conditions. A contributing factor was the pilot's pre-flight decision to operate into an area of forecast moderate icing conditions in an aircraft not equipped with in-flight icing protection.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI07FA046
Event ID
20070110X00036
Case number
CHI07FA046
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: 00504ca3b53cff8e9cfddc7bb224440fbf53c239573cf874ec9b2835d421ffa9; retrieved 2026-09-20T16:56:29.622Z.