Event CEN12LA452

Factual narrative

On June 12, 2012, at 0958 central daylight time, a Mikoyan Gurevich Mig 21MF, was substantially damaged when it over ran the runway while landing at Flying Cloud Airport (FCM), Minneapolis, Minnesota. The airline transport pilot sustained minor injuries. The airplane was registered to and operated by the pilot. An instrument flight rules flight plan was filed for the flight that departed from Ann Arbor Municipal Airport (ARB), Ann Arbor, Michigan, about 0630. Visual meteorological conditions prevailed for the personal flight conducted under 14 Code of Federal Regulations Part 91. The pilot stated the airplane was going to be part of an exhibition being held at Flying Cloud airport that weekend. On final approach to runway 10R, he established a speed of 165 knots and landed approximately 300 feet down the 5,000-foot-long runway. Upon landing, the pilot brought the throttle to idle and deployed the drag chute. Since there was a delay in slowing the airplane down before the chute opened, the pilot said he initiated maximum braking. When the airplane did not slow down, he thought that he did not hit the button that deployed the chute hard enough and tried several more times before he realized he "had no chute." When the pilot knew that the airplane would go off the runway, he maneuvered it to the left and onto the grassy area adjacent to the runway to avoid crossing a state highway. The airplane struck a berm and a chain link fence before it came to rest upright. The left main landing gear collapsed and the right wing and fuselage were substantially damaged. The nose cone of the airplane and the left wing were also damaged. Several Federal Aviation Administration (FAA) inspectors were at the airport and witnessed the accident. According to one inspector, when the airplane was approximately halfway down the runway, the drag chute deployed. Before the chute fully opened, it departed the airplane and landed on the runway. The airplane continued down the runway at a high rate of speed before it veered left near the east end of the runway. The inspector said it looked like the airplane went up on its nose and then landed back down on its belly before it came to a rest near the edge of a highway. The pilot said he tested the drag chute approximately three weeks before the accident in preparation for this particular flight and there were no malfunctions of the system. He also said that he had successfully deployed the drag chute about 6 or 7 times prior to this accident without incident. A review of performance data for the airplane revealed the pilot had sufficient runway length to land without the drag chute. The pilot established an appropriate speed during the approach and landed about 300 feet down the 5,000-foot-long runway. Within seconds of touching down, the pilot brought the throttle control to idle and deployed the drag chute. However, when the chute deployed, it did not fully inflate and then separated from the airplane. The pilot was not immediately aware the drag chute had failed and continued to try to deploy the chute. The pilot said that he used maximum braking to slow the airplane but was unable to stop the airplane on the runway. The pilot swerved to the left to avoid crossing a state highway, and the airplane struck a berm and a fence before it stopped. The pilot said that he had successfully tested the drag chute in preparation for this particular landing and had no previous problems deploying the chute before the accident. A review of performance data revealed that the pilot had sufficient runway length to land without use of the drag chute had he applied the wheel brakes immediately upon landing. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

• C Aircraft-Aircraft systems-Equipment/furnishings-(general)-Failure - C
• C Aircraft-Aircraft systems-Landing gear system-Brake-Incorrect use/operation - C
• C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C