No fatalities

7 Sep 2009: CESSNA 172S (N568ND) — University of North Dakota — Duluth, MN

Duluth, MN, United States

On 7 Sep 2009, a CESSNA 172S (registration N568ND) operated by University of North Dakota was involved in an aviation accident near Duluth, MN. No fatalities were reported. Investigators recorded the probable cause as: The pilot's failure to maintain aircraft control during landing, resulting in a hard landing and a propeller strike with the ground. This summary draws on records from NTSB; 17 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards

On September 7, 2009, a Cessna 172S (N568ND) operated by the University of North Dakota sustained propeller and firewall damage. The pilot was uninjured. The damage was discovered during maintenance.

Accident Overview

On September 7, 2009, a Cessna 172S, registration N568ND, operated by the University of North Dakota, sustained substantial damage during a flight. The aircraft was found with a damaged propeller and engine firewall. The private pilot, who was the sole occupant, was not injured. The flight was conducted under 14 Code of Federal Regulations Part 91. The exact location and time when the damage occurred were not determined.

Flight Sequence

The flight departed Grand Forks International Airport (GFK), Grand Forks, North Dakota, at 1340 central daylight time. It landed at St. Cloud Regional Airport (STC), St. Cloud, Minnesota, around 1600. After refueling, the airplane departed STC at 1640 and arrived at Duluth International Airport (DLH), Duluth, Minnesota, at 1750. The airplane departed DLH at 1830 and arrived back at GFK at 2045. The flight was conducted in visual meteorological conditions, and a flight plan was filed.

Pilot Reports

The pilot reported that he performed a normal landing at STC. He stated that the airplane ballooned during the flare, so he released back pressure and flared again. After landing, he taxied to the ramp and refueled. At DLH, the pilot performed a normal cross-wind landing and taxied to the ramp. No fuel was added, and about 40 minutes later, he taxied out for departure. While taxiing to runway 09, he taxied over a rough area and heard a loud "bing!" He checked his instruments, which appeared normal, and continued to taxi. He departed DLH and climbed to 8,500 feet. He reported that the airplane was shaking slightly, but engine and flight instruments were normal, so he continued the flight to GFK. The landing at GFK was normal, and his post-flight inspection was brief; he did not inspect the propeller during his walk-around.

Discovery of Damage

An instructor pilot who had provided flight instruction in the airplane prior to the accident flight stated that only two landings were made during that instructional flight, and he was confident that no hard landing damage had occurred. The lineman at GFK reported that while fueling the airplane, he noticed the propeller appeared to have struck the ground, with about 1-2 inches bent backwards. He notified dispatch, who informed him that the damage had not been reported by a flight crew. An inspection of the airplane revealed damage to the propeller and the engine firewall.

Contributing factors

Causes

Landing flare — Not attained/maintainedPilot

Other contributing factors

Damaged/degraded