Aircraft that carried N52502 · 2
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N52502 now.
NTSB investigations on N52502 · 3
Of this N-number, whichever aircraft carried it.
NTSB CHI99LA040Accident · Minor injuriesLimited investigationFinal reportCessna 172P · 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 CHI93LA364Accident · No injuriesLimited investigationFinal reportCessna 172P · Fieldon, ILPartial failure (deterioration) of the #1 piston pin plug, which resulted in contamination of the lubricating system and failure of the #3 connecting rod.NTSB FTW68F0122Accident · Serious injuriesClosedTaylorcraft DCO-65 · Bonita, LA
FAA incident reports on N52502 · 2
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 19981127032431ACessna 172P · Brainerd, MNAcft was on final and landed on top of N80357. (.19) on November 27, 1998, at 1201 central standard time, a Cessna 172P, N52502, piloted by a private pilot, received substantial damage, on collision with a Cessna 172M, N80357, during touchdown on runway 23…Accident 19930916034919ACessna 172P · Fieldon, ILLosing power en route. Engine quit on approach to a field. Engine had broken connecting rod and worn piston pin.