Aircraft that carried N80357 · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N80357 now.
NTSB investigations on N80357 · 2
Of this N-number, whichever aircraft carried it.
NTSB CHI99LA040Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Brainerd, MNThe visual lookout not obtained/maintained by the pilot of the other aircraft. Contributing factors were the unicom frequency not selected and the traffic advisory not issued by the pilot of the other aircraft. An additional factor was the aircraft moving on…NTSB MKC89LA186Accident · No injuriesLimited investigationFinal reportCessna 172 · Clear Lake, MNThe pilot's improper decision in attempting to land with inadequate visual cues which precluded identification of a correct runway alignment. A suitable alternative airport was readily available.
FAA incident reports on N80357 · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 19981127032452ACessna 172M · Brainerd, MNAcft was on final when another Cessna landed on top of it. (.19)narrative - same as CHI99LAO40B(N80357) on November 27, 1998, at 1201N central standard time, a Cessna 172P, N52502, piloted by a private pilot, received subatantial damage in collision with a…Accident 19890822031489ACessna 172M · Clear Lake, MNTried to land on a sod strip with only two lights at end of strip. Landed on side of strip in soft ground. Nosed overIncident 19830905065399ICessna 172M · Des Moines, IARan out of fuel on final approach. Landed in a vacant lot. No pilot or medical certificate with him.