Aircraft that carried N9130N · 2
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N9130N now.
NTSB investigations on N9130N · 2
Of this N-number, whichever aircraft carried it.
NTSB NYC07FA009Accident · 2 fatalField investigationFinal reportPiper PA-46-310P · Odenton, MDThe pilot's failure to maintain adequate clearance from terrain during the approach. Contributing was the pilot's self-induced pressure to land the airplane after being informed by air traffic control that he was not operating in compliance with the ADIZ…NTSB LAX96LA313Accident · No injuriesLimited investigationFinal reportPiper PA-46-310P · Redlands, CAthe pilot's improper weather evaluation. The uphill runway condition and weather associated with thunderstorm(s) were related factors.
FAA incident reports on N9130N · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20061019021519APiper PA46310P · Fort Meade, MD(-23) Aircraft departed fme, VFR, transponder code 1200. Upon contacting ptc, the pilot was instructed that he was in violation of adiz airspace procedures and instructed to land immediately at fme. Pilot appears to have over-shot final approach to runway 28…Incident 20010815023809IPiper PA46310P · Cocoa, FL(-23) During night landing, pilot attempted to command airport runway lights on by clicking his mike button on the assigned radio frequency. The runway lights did not respond and the approach was made to an unlit runway. The pilot's approach was not in line…Accident 19960823024079APiper PA46310P · Redlands, CATook off to avoid thunderstorm west. Settled on climbout. Hit prop. Aborted. Ran off into rocks. Variable gusts.