# Accident 19850914045049A: Maule M5235C, Bloomington, IN, September 14, 1985

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 14, 1985, 10:55 local time
- Place: Bloomington, IN
- Airport: Monroe Co
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 39.1596° N, 86.5195° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=39.1596&lon=-86.5195&mi=10
- Aircraft: N56349, a cancelled registration (https://openairdocs.org/deregistered/N56349-1998-03-23) (OpenAirDocs)
- Registry model: Maule M-5-235C (registry code 5460135, https://openairdocs.org/model/maule-m-5-235c) (OpenAirDocs)
- Reported make and model: MAULE M5235C
- Reported engine: LYC O540J1A5
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 293 total, 69 in this make and model, 0 in the last 90 days
- NTSB investigation: [NTSB CHI85LA380](https://openairdocs.org/ntsb/CHI85LA380) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19850914045049A

## Narrative

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

VEERED ON ROLLOUT DURING CROSSWIND LANDING. RIGHT MAIN GEAR COLLAPSED AND AIRCRAFT NOSED OVER.

## 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 CHI85LA380](https://openairdocs.org/ntsb/CHI85LA380), Sep 14, 1985: Maule M-5-235C (N56349), Bloomington, IN, substantial damage

## Other reports on N56349 (1)

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

- [Accident 19950402010009A](https://openairdocs.org/incident/19950402010009A), Apr 2, 1995: Maule M5235C (N56349), Rush City, MN, Destroyed, 1 fatal. Impacted ground and burned. (-23) all aircraft records were consumed in the fire during the impact. The airworthiness, airman competence and any FAR violation…

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.