# Accident 19970705017679A: Piper PA34200, Mackinac Island, MI, July 5, 1997

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 5, 1997, 12:00 local time
- Place: Mackinac Island, MI
- Airport: Mackinac Island Airport
- Damage: Substantial damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 45.8491° N, 84.6196° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=45.8491&lon=-84.6196&mi=10
- Aircraft: N56676, registered now (https://openairdocs.org/aircraft/N56676) (OpenAirDocs)
- Registry model: Piper PA-34-200 (registry code 7103405, https://openairdocs.org/model/piper-pa-34-200) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: PIPER PA34200
- Reported engine: LYC IO360C1E6
- People aboard: 5
- Fatal injuries: 0
- Pilot flight hours: 363 total, 23 in this make and model, 10 in the last 90 days
- NTSB investigation: [NTSB CHI97LA206](https://openairdocs.org/ntsb/CHI97LA206) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19970705017679A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

AIRCRAFT FLARED HIGH AND STALLED. (.4)THE PILOT SAID THAT ON SHORT FINAL APPROACH, THE AIRPLANE ENCOUNTERED TURBULENCE AND THAT HE HELD THE AIRPLANE OFF THE RUNWAY TO ALLOW AIRSPEED TO DECREASE.  THE AIRPLANE THEN BOUNCED ONE TIME AND LANDED HARD.            (-23) PILOT STATED THAT HE HAD FLARED HIGH AND THEN AIRCRAFT LANDED HARD, BOUNCED BACK INTO THE AIR AND THEN LANDED HARD ON NOSE WHEEL.  NOSE WHEEL WAS PUSHED UP INTO FORWARD BAGGAGE AREA AND BOTH PROPS WERE DAMAGED BY GROUND CONTACT. NO INJURIES REPORTED.

## The NTSB's investigation of this event (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 CHI97LA206](https://openairdocs.org/ntsb/CHI97LA206), Jul 5, 1997: Piper PA-34-200 (N56676), Mackinac Island, MI, substantial damage. Probable cause: the pilot's improper flare and improper recovery from a bounced landing, which resulted in a hard landing. Turbulence on short final was a related factor.

## Other reports on N56676 (5)

Matched to the same aircraft by N-number and date.

- [Incident 20260608005409I](https://openairdocs.org/incident/20260608005409I), Jun 8, 2026: Piper PA-34-200 (N56676), Fort Pierce, FL, Minor damage. On June 8, 2026, I was conducting a commercial multi-engine training flight with a student in a Piper PA-44 seminole. During the flight, the landing gear was…
- [Incident 20250509004119I](https://openairdocs.org/incident/20250509004119I), May 9, 2025: Piper PA-34-200 (N56676), Vero Beach, FL, Minor damage. On 05/09/2025 aircraft, [privacy data omitted], was being operated for instruction. During the landing at Vero Beach regional airport (vrb) the aircraft…
- [Accident 19991108039169A](https://openairdocs.org/incident/19991108039169A), Nov 8, 1999: Piper PA34200 (N56676), Olive Branch, MS, Substantial damage. (.4)The CFI and private -rated student pilot were conducting to uch-and-go landings. After touch down the dual student retracted the flaps and reached for the…
- [Incident 19990809024189I](https://openairdocs.org/incident/19990809024189I), Aug 9, 1999: Piper PA34200 (N56676), Olive Branch, MS, Minor damage. Instructor stated that the student was fast on downwind, base, final and on landing. Student landed on nose gear, went airborne and came back down striking…
- [Incident 19920604022979I](https://openairdocs.org/incident/19920604022979I), Jun 4, 1992: Piper PA34200 (N56676), Allentown, PA, Minor damage. Right main gear collapsed on landing rollout. Found a broken stud assembly.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.