NTSB investigations · 3
Matched to this aircraft by N3210A and the event date: up to this one’s cancellation.
NTSB GAA17CA116Accident · No injuriesData collectionFinal reportCoeur 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 reportPortland, ORThe pilot's failure to maintain directional control of the airplane during the landing.NTSB CEN09CA293Accident · No injuriesData collectionFinal reportRoswell, NMThe pilot's failure to maintain directional control while landing.
FAA incident reports · 3
FAA accident and incident reports matched to this aircraft by N3210A and the event date: up to this one’s cancellation.
Accident 20170114000069ALanding: Touchdown · 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 20140919017269ALanding: Rollout · 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 20090513006359ALanding · 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…