No fatalities

Runway Overrun and Fence Impact Due to Brake Anomaly (N80310)

Harbor Springs, MI, US

On August 17, 2000, a Cessna 172M (registration N80310) operated by Bear River Aviation, Inc. was involved in an aviation accident near Harbor Springs, MI. No fatalities were reported. Investigators recorded the probable cause as: The pilot's inability to stop the aircraft within the runway limits due to brakes not responding normally during landing rollout. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-06-19Data APIEditorial standards

The aircraft failed to stop within the runway limits during landing rollout due to perceived brake issues, resulting in a fence impact with no reported injuries.

What happened

During the landing rollout phase, the pilot reported that the airplane's braking system did not exhibit its normal response characteristics. As the aircraft approached the end of the runway, the pilot applied significant pressure to the brake pedals in an attempt to decelerate the aircraft effectively. Despite this heavy pedal application, the airplane was unable to stop within the paved surface boundaries.

The aircraft continued past the runway threshold, crossed a split-rail fence, and eventually came to a halt beyond the airfield perimeter. Examination of the runway surface revealed tire marks that began approximately 600 feet from the departure end of the runway. These marks traveled left off the runway, then right across the runway, terminating at the very end of the paved area.

The investigation

A thorough mechanical examination of the airplane was conducted following the incident. Investigators found no anomalies or mechanical defects that would explain the reduced braking performance. The aircraft systems appeared to be functioning within normal parameters based on the post-accident inspection.

Findings

The primary factor in this incident was the brakes not responding normally during the critical landing rollout phase. The pilot's observation of diminished brake effectiveness, combined with the inability to stop the aircraft before reaching the runway end, led to the overrun and subsequent fence impact. No mechanical failures were identified during the post-accident examination.

Safety message

Pilots should remain vigilant regarding braking performance during landing operations. Any deviation from normal brake response should be considered seriously, and go-around procedures or alternative stopping strategies may need to be evaluated in real-time if braking efficiency is compromised.

Probable cause

The pilot's inability to stop the aircraft within the runway limits due to brakes not responding normally during landing rollout.

Frequently asked questions

What happened in the 17 Aug 2000 Cessna 172M accident near Harbor Springs, MI?

The aircraft failed to stop within the runway limits during landing rollout due to perceived brake issues, resulting in a fence impact with no reported injuries.

Were there any fatalities in the 17 Aug 2000 Cessna 172M accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 17 Aug 2000 involved a Cessna 172M, registration N80310, operated by Bear River Aviation, Inc., at Harbor Springs, MI.

What was the probable cause of the accident?

The pilot's inability to stop the aircraft within the runway limits due to brakes not responding normally during landing rollout.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001212X21681. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.