Zone

Crash of a Mitsubishi MU-2B-40 Solitaire in Bunnell: 2 killed

Date & Time: Aug 25, 2006 at 1308 LT
Type of aircraft:
Registration:
N171MA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Kalamazoo – Bloomington – Governor’s Harbour
MSN:
431
YOM:
1980
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3800
Captain / Total hours on type:
1700.00
Aircraft flight hours:
3802
Circumstances:
The pilot had received an outlook briefing during the morning hours before the accident. The briefing included information regarding widely scattered thunderstorms and rain showers along portions of the pilot's planned route of flight. At the time of the accident, a convective weather significant to the safety of all aircraft (convective SIGMET) was in effect for the pilot's route of flight, and the information about the convective SIGMET was broadcast to the pilot by air traffic control (ATC). Several airplanes in the vicinity of the accident airplane were deviating around weather. Conversations between the accident pilot and the ATC controller were consistent with the accident airplane's weather radar functioning, and the possibility that the accident airplane's weather radar was providing more information than the ATC weather radar. Although the pilot initially declined a deviation query by ATC, he later accepted one. Shortly after, the pilot was unable to maintain his assigned altitude of 28,000 feet msl (FL 280), and the airplane impacted terrain consistent with a vertical descent. At the time of the accident, at FL 280, weak to moderate weather radar echoes existed. Very strong to intense weather radar echoes were seen about FL 200. The ATC facility was equipped with NEXRAD derived weather displays. The weather displays had four settings: below FL 240, between FL 240 and FL 330, above FL 330, and from sea level to FL 600. At the time of the accident, the ATC controller's weather display indicated weak to moderate echoes above FL240. Very strong to intense weather radar echoes existed about FL200; however, the ATC controller did not have his weather display set to that altitude as he was not controlling traffic at that altitude. The investigation could not determine if the pilot was aware of the stronger intensity echoes below his altitude, or if the airplane's weather radar was depicting the stronger echoes. Examination of the wreckage did not reveal any preimpact mechanical malfunctions.
Probable cause:
The pilot's inadvertent encounter with thunderstorms.
Final Report:

Crash of a Cessna 411 in Bloomington

Date & Time: Apr 5, 1986 at 1530 LT
Type of aircraft:
Registration:
N3213R
Flight Type:
Survivors:
Yes
Schedule:
Nashville - Bloomington
MSN:
411-0213
YOM:
1966
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
889
Captain / Total hours on type:
63.00
Aircraft flight hours:
2262
Circumstances:
The pilot reported that while on final approach to runway 35, the aircraft encountered 'extreme windshift' and was blown about 550 feet right of course with a 30 knot loss of airspeed (from 130 to 100 knots). He stated the aircraft lost about 300 feet, then was blown back on course with an additional loss of altitude. Subsequently, the aircraft touched down hard on the approach end of the runway. During touchdown, the right main tire blew out, the right propeller struck the runway 9 times and the right wing was damaged. The surface wind was reported to be from 240° at 10 knots with no gusts. All four occupants escaped uninjured.
Probable cause:
Occurrence #1: hard landing
Phase of operation: landing - flare/touchdown
Findings
1. (f) weather condition - crosswind
2. (f) weather condition - tailwind
3. (f) weather condition - windshear
4. (c) weather condition - unfavorable wind
5. (c) compensation for wind conditions - inadequate - pilot in command
6. Flare - not attained
Final Report:

Crash of a Vickers 835 Viscount in Bloomington

Date & Time: Oct 19, 1985 at 1535 LT
Type of aircraft:
Operator:
Registration:
N923RC
Survivors:
Yes
Schedule:
Lexington - Bloomington
MSN:
320
YOM:
1959
Crew on board:
2
Crew fatalities:
Pax on board:
26
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
27000
Captain / Total hours on type:
6000.00
Aircraft flight hours:
11707
Circumstances:
During an ILS to runway 35, the approach was normal until the aircraft was approximately 100 feet above the decision height, except there was condensation on the windshield. Touchdown was hard. A witness said the aircraft landed approximately 1/3 of the way down the 5,200 feet runway. After landing, with the props in 'ground fine,' braking action was ineffective on the wet runway. The aircraft was not equipped with an anti-skid braking system. Subsequently, the aircraft continued off the runway and went down an embankment into a field. Scrub marks on the runway and reverted rubber on the tires indicated the aircraft was hydroplaning. According to the flight manual, 4,500 feet (plus a 10% factor for no anti-skid) would have been required to stop on a dry runway in the prevailing weather conditions, which included a slight tailwind. Two pax, acting as flight attendants (f/a's), assisted the other pax in evacuating. An investigation revealed the f/a's were not properly trained; the pax were not completely briefed before the flight; and the passenger briefing cards were inadequate. The aircraft was on a business flight to transport an entertainment troupe.
Probable cause:
Occurrence #1: overrun
Phase of operation: landing - roll
Findings
1. (f) weather condition - tailwind
2. (f) weather condition - fog
3. (f) weather condition - rain
4. (f) window, flight compartment window/windshield - dirty (foggy)
5. (c) proper touchdown point - exceeded - pilot in command
6. (c) visual/aural perception - pilot in command
7. (c) in-flight planning/decision - improper - pilot in command
8. (c) missed approach - not performed - pilot in command
9. (f) airport facilities, runway/landing area condition - wet
10. (f) aircraft performance, hydroplaning condition - water
----------
Occurrence #2: on ground/water encounter with terrain/water
Phase of operation: landing - roll
Findings
11. (f) terrain condition - rough/uneven
12. (f) terrain condition - downhill
----------
Occurrence #3: miscellaneous/other
Phase of operation: other
Findings
13. (f) passenger briefing - inadequate - flight attendant
14. (f) inadequate training (emergency procedure(s)) - flight attendant
15. (f) information unclear - company/operator management
Final Report: