# Accident 19950826025969A: Cessna 172G, Put In Bay, OH, August 26, 1995

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 26, 1995, 14:40 local time
- Place: Put In Bay, OH
- Airport: Put In Bay Airport
- Damage: Substantial damage
- Phase of flight: Go Round (Aborted VFR)
- Operating rules: General operating rules (Part 91)
- Location: 41.6397° N, 82.8192° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=41.6397&lon=-82.8192&mi=10
- Aircraft: N3680L, a cancelled registration (https://openairdocs.org/deregistered/N3680L-1996-03-12) (OpenAirDocs)
- Registry model: Cessna 172G (registry code 2072420, https://openairdocs.org/model/cessna-172g) (OpenAirDocs)
- Reported make and model: CESSNA 172G
- Reported engine: CONT O300D
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 283 total, 235 in this make and model, 6 in the last 90 days
- NTSB investigation: [NTSB BFO95LA088](https://openairdocs.org/ntsb/BFO95LA088) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19950826025969A

## Narrative

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

TOO FAST ON DOWNWIND LANDING. BEGAN GO AROUND. LEFT WING STRUCK TREE ON CLIMBOUT. WIND ADVISORY GARBLED ON UNICOM. (-23) PILOT ATTEMPTED GO-AROUND AFTER DECIDING THE AIRCRAFT WAS TOO HIGH AND FAST FOR LANDING AND STALLED AIRCRAFT OVER TREES AND CRASHED INTO TREES CAUSING THE AIRCRAFT TO BECOME DESTROYED.

## 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 BFO95LA088](https://openairdocs.org/ntsb/BFO95LA088), Aug 26, 1995: Cessna 172G (N3680L), Put-In-Bay, OH, substantial damage. Probable cause: THE PILOT'S DELAY IN ABORTING THE LANDING AFTER SELECTING THE WRONG RUNWAY. FACTORS RELATING TO THE ACCIDENT WERE: GARBLED RADIO TRANSMISSIONS ON THE UNICOM FREQUENCY, AND THE RESULTANT TAILWIND FOR…

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.