- Date
- March 15, 2017
- Place
- Manitouwadge, Canada
- Damage
- Substantial damage
- Phase of flight
- Unknown
- Aircraft
- N230TXCessna 172P
- Defining event
- Unknown: Unknown or undetermined
- NTSB office
- Central Region
- Lead agency
- Other
- Parties
- Federal Aviation Administration, TSB, Canada
- Case key
- 94880
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Factual narrative
On March 15, 2017, at an unknown time, a Cessna 172P airplane, N230TX, owned and operated by the University of Michigan Flyers Inc. was substantially damaged when it collided with wooded terrain near Manitouwadge, Ontario, Canada. No pilot or occupant was found in the wreckage. The flight originated from the Ann Arbor Municipal Airport, near Ann Arbor, Michigan, about 1912 eastern daylight time and was destined for the Harbor Springs Airport, near Harbor Springs, Michigan. The accident investigation is under the jurisdiction and control of the Canadian Transportation Safety Board. This report is for informational purposes only and contains only information released by or obtained from the Canadian government. Further information pertaining to this accident may be obtained from: Transportation Safety Board of Canada 200 Promenade du Portage, Place du Centre, 4th Floor Gatineau, Quebec K1A 1K8 Web: http://www.tsb.gc.ca Occurrence Number: A17O0045
Aircraft
- Registration
- N230TX
- Reported as
- Cessna 172P (P)
- Category
- Airplane
- Serial number
- 17276171
- Engine
- Lycoming O-320 SERIES, reciprocating
- Damage
- Substantial damage
- Flight
- Non-U.S., non-commercial
- Operator
- University Of Michigan Flyers Inc
- Registered owner
- University Of Michigan Flyers Inc
- Airworthiness certificate
- Standard, Normal
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.