Aircraft that carried N4216V · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N4216V now.
NTSB investigations on N4216V · 3
Of this N-number, whichever aircraft carried it.
NTSB ERA14LA050Accident · No injuriesLimited investigationFinal reportCessna 170 · Ridgely, MDA total loss of engine power for reasons that could not be determined based on the available evidence.NTSB CHI94LA332Accident · No injuriesLimited investigationFinal reportCessna 170 · St. Anne, ILEngine failure due to an inadequately reconditioned cylinder.NTSB UNK64X2302Accident · No injuriesClosedCessna 150 · Sanger, CA
FAA incident reports on N4216V · 2
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20131008023699ACessna 170 · Ridgely, MDPilot stated he was going to conduct touch and goes at Ridgely airpark, MD. He conducted a normal preflight but after takeoff experienced engine failure. Made off airport emergency landing resulting in substantial structural damage to the aircraft.Accident 19940918028139ACessna 170 · St Anne, ILLoud engine knock and loud bang. Cowling separated. Hit pole landing on road. NR2 cyl had fractured. Recent annual.