# Incident 20030607019699I: Beech A24R, Glencoe, MN, June 7, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 7, 2003, 17:05 local time
- Place: Glencoe, MN
- Airport: Glencoe Municipal Airport
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 44.7560° N, 94.0815° W: Placed by OpenAirDocs at GLENCOE MUNI (GYL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.7560&lon=-94.0815&mi=10
- Aircraft: N8043R, registered now (https://openairdocs.org/aircraft/N8043R) (OpenAirDocs)
- Registry model: Beech A24R (registry code 1151252, https://openairdocs.org/model/beech-a24r) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: BEECH A24R
- Reported engine: LYC IO360A1B
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 125 total, 9 in this make and model, 6 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030607019699I

## Narrative

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

(-23) N8043R WAS ENROUTE FROM RST TO HCD ON A VFR PLEASURE FLIGHT. THE PILOT HEARD A LOUD BANG AND THE AIRFRAME VIBRATED VIOLENTLY. THE ENGINE WAS SHUT DOWN AND AN EMERGENCY LANDING WAS MADE IN A PLOWED FIELD (CORN SEEDLINGS) SE OF GLENCOE, MN. THERE WAS NO DAMAGE TO THE AIRCRAFT AND NO INJURIES. THE PISTON CONNECTING ROD APPEARS TO HAVE BROKEN AND THE PISTON CAME THROUGH THE SIDE OF THE ENGINE.

## Other reports on N8043R (1)

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

- [Incident 20040630020769I](https://openairdocs.org/incident/20040630020769I), Jun 30, 2004: Beech A24R (N8043R), Ely, MN, Minor damage. (-23) On landing at Ely Municipal (elo) aircraft bounced once and upon second contact with the runway the nose gear collapsed. Aircraft then skidded to a stop,…

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.