# NTSB CHI00LA259: Cessna 172M, N80310, Harbor Springs, MI, August 17, 2000

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: August 17, 2000, 10:45 local (14:45 UTC)
- Place: Harbor Springs, MI
- Coordinates: 45.430629, -84.979171 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=45.4306&lon=-84.9792&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report May 18, 2001
- Report: Approved by Office Director
- NTSB case key (mKey): 50065
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI00LA259
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/50065/pdf
- Page: https://openairdocs.org/ntsb/CHI00LA259

## Probable cause

the pilot's long touchdown, and inadequate braking to stop on the runway.  Factors relating to this accident were the pilot's improper in-flight planning and decision resulting in the long touchdown, and the fence.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Overrun, landing
  - touchdown - improper, pilot in command (cause)
  - brakes(normal) - inadequate, pilot in command (cause)
  - in-flight planning/decision - improper, pilot in command (contributing factor)
- On ground/water collision with object, landing - roll
  - object - fence (contributing factor)

## Analysis

The pilot said that during landing roll out, the airplane's brakes did not seem to have the 'normal response.'  The pilot said he applied 'heavy pedal' just before reaching the end of the runway.  The airplane went through a split-rail fence and stopped.  An examination of the airplane revealed no anomalies.  An examination of the runway showed tire marks, beginning approximately 600 feet from the departure end of the runway.  The tire marks proceeded left off of the runway, then right, across the runway, until ending at the end of the runway.

## Factual narrative

On August 17, 2000, at 1045 eastern daylight time (edt), a Cessna 172M, N80310, operated by a private pilot, sustained substantial damage when during landing, the airplane departed runway 28 (4,157 feet by 75 feet, dry asphalt), at Harbor Springs Municipal Airport, Harbor Springs, Michigan, and struck a fence.  Visual meteorological conditions prevailed at the time of the accident.  The personal flight was being conducted under 14 CFR Part 91.  A flight plan was not on file.  The pilot reported no injuries.  The local flight originated at Harbor Springs, Michigan, at 1030 edt.

In his written statement, the pilot said that during landing roll out, the airplane's brakes did not seem to have the "normal response."  The pilot said he applied "heavy pedal" just before reaching the end of the runway.  The airplane went through a split-rail fence and stopped.

Federal Aviation Administration inspectors examined the airplane at the Harbor Springs Municipal Airport.  The airplane's right strut was bent inward.  An upward bulge was observed in the top skin of the right wing, above the right strut attach point, at the forward spar.  One propeller blade was bent aft at the tip.  The right horizontal stabilizer was bent upward.  Flight control continuity was confirmed.  An examination of the airplane's engine and other systems revealed no anomalies.

Tire marks were observed beginning approximately 600 feet from the departure end of the runway (3,500 feet down from the approach end of the runway).  The marks progressed left off of the runway, then went right, across the runway, until ending at the end of the prepared surface of runway 28.  A 4 foot tall fence post in the airport's perimeter fence, just off the end of runway 28, was broken.

## Aircraft

- Registration: [N80310](https://openairdocs.org/deregistered/N80310-2013-12-12), registration cancelled 2013-12-12, S/N 17266512, built 1975 (OpenAirDocs)
- Reported make and model: Cessna 172M
- Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17266512
- Engines: Lycoming O-320-E2A 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Bear River Aviation, Inc.
- Registered owner: Miller Aircraft, Inc.
- Airworthiness certificate: Standard, Normal
- Departed: D87
- Airport: D87, Harbor Springs Municipal, runway 28, 4,157 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 83; private; airplane ratings: single-engine sea, single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 342 total, 200 as pilot in command, 1 in the last 90 days, 1 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 170° at 6 knots
- Visibility: 10 statute miles
- Lowest ceiling: 6,000 ft broken
- Temperature: 57 °F, dew point 55 °F
- Altimeter: 30.00 inHg
- Observed at: PLN, 10 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20000817037259A](https://openairdocs.org/incident/20000817037259A), Aug 17, 2000: Cessna 172M, Harbor Springs, MI, No damage. (-23) He made two passes around the field. The first one resulted in a normal landing. The second one resulted in the accident. Mr. Sarto stated that he landed…

## Other investigations on N80310 (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB MKC79DCD02](https://openairdocs.org/ntsb/MKC79DCD02), Oct 10, 1978: Cessna 172 (N80310), Williams, IA, substantial damage

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
