Zone

Crash of a Cessna 441 Conquest II in Saint Louis: 2 killed

Date & Time: Nov 22, 1994 at 2203 LT
Type of aircraft:
Operator:
Registration:
N441KM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Saint Louis - Iron Mountain
MSN:
441-0196
YOM:
1981
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7940
Captain / Total hours on type:
2060.00
Circumstances:
During the takeoff roll on runway 30R, the MD-82, N954U, collided with the Cessna 441, N441KM, which was positioned on the runway waiting for takeoff clearance. The pilot of the Cessna acted on an apparently preconceived idea that he would use his arrival runway, runway 30R, for departure. After receiving taxi clearance to back-taxi into position and hold on runway 31, the pilot taxied into a position at an intersection on runway 30R, which was the assigned departure runway for the MD-82. The ATIS current at the time the Cessna pilot was operating in the Lambert-St. Louis area listed runways 30R and 30L as the active runways for arrivals and departures; there was no mention of the occasional use of runway 31. Air traffic control personnel were not able to maintain visual contact with the Cessna after it taxied from the well lighted ramp area into the runway/taxiway environment of the northeast portion of the airport. An operational ASDE-3, particularly ASDE-3 enhanced with AMASS, could be used to supplement visual scan of the northeast portion of the airport.
Probable cause:
The Cessna 441 pilot's mistaken belief that his assigned departure runway was runway 30R, which resulted in his undetected entrance onto runway 30R, which was being used by the MD82 for its departure. Contributing to the accident was the lack of Automatic Terminal Information Service and other air traffic control (ATC) information regarding the occasional use of runway 31 for departure. The installation and utilization of Airport Surface Detection Equipment (ASDE-3), and particularly ASDE-3 enhanced with the Airport Movement Area Safety System (AMASS), could have prevented this accident.
Final Report:

Crash of a Beechcraft H18 in Iron Mountain: 1 killed

Date & Time: Oct 17, 1974 at 0151 LT
Type of aircraft:
Operator:
Registration:
N72FA
Flight Type:
Survivors:
No
Schedule:
Lansing - Iron Mountain
MSN:
BA-631
YOM:
1962
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
12345
Captain / Total hours on type:
4000.00
Circumstances:
During a night approach to Iron Mountain Airport, the pilot descended below the MDA when the twin engine airplane struck tree tops and crashed in a wooded area located few hundred yards short of runway threshold. The aircraft was destroyed and the pilot, sole on board, was killed.
Probable cause:
Collision with trees on a night approach following improper IFR operation. The following contributing factors were reported:
- Instruments misread or failed to read,
- High obstructions,
- Descended below clearance limit of 3,000 feet.
Final Report:

Crash of a Beechcraft H18 in Iron Mountain: 1 killed

Date & Time: Jul 3, 1974 at 0145 LT
Type of aircraft:
Operator:
Registration:
N73FA
Flight Type:
Survivors:
No
Schedule:
Lansing - Iron Mountain
MSN:
BA-649
YOM:
1963
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6070
Circumstances:
On a night approach to Iron Mountain-Ford Airport, the pilot encountered poor weather conditions and very limited visibility. On final, he failed to realize his altitude was too low when the airplane struck a dirt bank and crashed in flames. The aircraft was destroyed and the pilot, sole on board, was killed.
Probable cause:
Improper in-flight decisions on part of the pilot who continued VFR flight into adverse weather conditions. The following contributing factors were reported:
- Failed to initiate a go-around,
- Incorrect altimeter setting,
- Not aligned with runway,
- Weather considerably worse than forecast,
- Heavy fog.
Final Report:

Crash of a Beechcraft H18S in Lansing

Date & Time: Dec 23, 1970 at 0059 LT
Type of aircraft:
Operator:
Registration:
N2345Z
Flight Type:
Survivors:
Yes
Schedule:
Iron Mountain - Lansing
MSN:
BA-626
YOM:
1962
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6267
Captain / Total hours on type:
2535.00
Circumstances:
While on a night approach to Lansing Airport, the crew encountered poor weather conditions with a reduced visibility due to freezing rain and fog. On final, the twin engine airplane stalled and crashed few hundred yards short of runway. Both pilots were seriously wounded and the aircraft was destroyed. It was completing a cargo flight from Iron Mountain.
Probable cause:
Failure of the crew to maintain flying speed while completing an approach in icing conditions including freezing rain and fog. The following factors were reported:
- Airframe ice,
- Low ceiling, fog and freezing rain,
- Stalled on ILS approach due to airframe icing.
Final Report:

Crash of a Beechcraft Queen Air 65 in Iron Mountain

Date & Time: Jul 27, 1965 at 2005 LT
Type of aircraft:
Registration:
N575K
Flight Type:
Survivors:
Yes
Schedule:
Iron Mountain - Iron Mountain
MSN:
LC-173
YOM:
1965
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9402
Captain / Total hours on type:
52.00
Circumstances:
On final approach to Iron Mountain-Ford Airport, while on a local training mission, the crew voluntarily shut down one engine to simulate a failure. Due to insufficient speed, the airplane stalled and crashed in a field located few miles short of runway. While both occupants were slightly injured, the airplane was damaged beyond repair.
Probable cause:
The crew failed to maintain a sufficient speed on approach.
Final Report: