Aircraft that carried N64182 · 2
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N64182 now.
NTSB investigations on N64182 · 3
Of this N-number, whichever aircraft carried it.
NTSB ERA12FA483Accident · 1 fatalField investigationFinal reportCessna 172P · Plainville, CTThe pilot's failure to maintain the proper glidepath during final approach in visual meteorological conditions, resulting in collision with a berm.NTSB NYC91LA106Accident · No injuriesLimited investigationFinal reportCessna 172P · Burlington, CTThe failure of the pilot to maintain directional control during the landing. Factors related to the accident were: improper use of the flight controls by the pilot, his lack of recent experience and total time, and the crosswind.NTSB NYC85LA017Accident · No injuriesLimited investigationFinal reportCessna 172P · Andes, NYAccording to the plt, he encountered deteriorating visibility due to haze & he elected to land in an unimproved field. The 1st approach was aborted; however, the acft touched down on the 2nd approach. After touching down, the plt realized the field was too…
FAA incident reports on N64182 · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20120726015889ACessna 172P · Plainville, CTOn the second approach to land on runway 20 at 4B8, the aircraft undershot the runway and impacted downsloping terrain prior to the runway threshold. Eyewitness statements report that the aircraft flew directly into the downsloping terrain prior to the runway…Accident 19910406009089ACessna 172P · Burlington, CTLost control landing in crosswind. Ran off runway into rocks and trees.Accident 19841101059469ACessna 172P · Andes, NYAttempted precautionary landing in grass field. Went around. But struck trees. Weather was deteriorating.