Aircraft that carried N3210A · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N3210A now.
NTSB investigations on N3210A · 3
Of this N-number, whichever aircraft carried it.
NTSB GAA17CA116Accident · No injuriesData collectionFinal reportCessna 170 · Coeur D'Alene, IDThe pilot’s failure to maintain an appropriate descent rate during approach, which resulted in landing short of the runway threshold.NTSB WPR14CA380Accident · No injuriesData collectionFinal reportCessna 170B · Portland, ORThe pilot's failure to maintain directional control of the airplane during the landing.NTSB CEN09CA293Accident · No injuriesData collectionFinal reportCessna 170B · Roswell, NMThe pilot's failure to maintain directional control while landing.
FAA incident reports on N3210A · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20170114000069ACessna 170B · Coeur D Alene, IDPilot landed short of the runway in the snow. Aircraft flipped over on its back. Pilot and passengers were not injured. Aircraft sustained damage to both wings, wing struts, vertical stabilizer, fuselage, cowling, firewall and boot cowl.Accident 20140919017269ACessna 170B · Hillsboro, ORThe pilot in command ground looped his CEO-170 during landing roll out on runway 31 at portland Hillsboro Airport. The reported weather at the time indicated the pilot landed with a quartering left tail wind from 080 degrees at 6 knots.Accident 20090513006359ACessna 170B · Roswell, NMOn April 13, 2009, the pilot/owner of N3210 departed from his base in artesia, new Mexico (kats) and a VFR flight to Roswell, new mexio (krow). No flight plan was filed. The pilot received ATIS information and, at 1432Z, was cleared to land on runway 35 while…