NTSB investigations · 2
Matched to this aircraft by N52502 and the event date: after June 8, 1970, when the previous aircraft’s registration ended, through this one’s cancellation.
NTSB CHI99LA040Accident · Minor injuriesLimited investigationFinal reportBrainerd, 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 reportFieldon, ILPartial failure (deterioration) of the #1 piston pin plug, which resulted in contamination of the lubricating system and failure of the #3 connecting rod.
FAA incident reports · 2
FAA accident and incident reports matched to this aircraft by N52502 and the event date: after June 8, 1970, when the previous aircraft’s registration ended, through this one’s cancellation.
Accident 19981127032431ALevel Off Touchdown · 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 19930916034919AFcd/Prec Ldg From Cruise · Fieldon, ILLosing power en route. Engine quit on approach to a field. Engine had broken connecting rod and worn piston pin.
Other aircraft with N52502 · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N52502 now.