Aircraft that carried N65484 · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N65484 now.
NTSB investigations on N65484 · 3
Of this N-number, whichever aircraft carried it.
NTSB MIA93LA100Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Orlando, FLVisual lookout not maintained by the pilot-in-command while taxiing the airplane. Contributing to the accident was the failure of the driver of the vehicle to advise the ground controller that he had stopped the vehicle on the taxiway.NTSB MIA87LA058Accident · No injuriesLimited investigationFinal reportCessna 152 · Orlando, FLThe acft skidded off the end of the wet grassy runway after touching down about midway down the rwy. The plt stated that in the future, all available rwy should be used. The plt received his private certificate just prior to the accident.NTSB MIA84LA257Accident · No injuriesLimited investigationFinal reportCessna 152 · Orlando, FLThe flt experienced eng failure and made a forced landing in a field, substantially damaging the aircraft. Post crash examination of the engine revealed the number three connecting rod separated from the crankshaft when the connecting rod bolts failed.…
FAA incident reports on N65484 · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 19930412009069ACessna 152 · Orlando, FLCollided with stopped airport vehicle while taxiing for takeoff. Driver failed report stop. Tower failed to note.Accident 19861224072219ACessna 152 · Orlando, FLThe aircraft skidded off the end of the wet grass runway. The pilot landed the aircraft midway down the runway.Accident 19840921052739ACessna 152 · Orlando, FLLost engine power and trailed smoke. Landed in orange grove with wingtip damage. Connecting rod bolts failed.