Aircraft that carried N9332F · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N9332F now.
NTSB investigations on N9332F · 4
Of this N-number, whichever aircraft carried it.
NTSB LAX96LA217Accident · No injuriesLimited investigationFinal reportHughes 269B · Georgetown, CAloss of engine power for undetermined reason(s), while practicing an autorotation, which resulted in a forced landing; and the flight instructor's misjudged landing flare during the emergency autorotation/landing.NTSB ANC87LA008Accident · No injuriesLimited investigationFinal reportHughes 300-269B · Fairbanks, AKThe helicopter exhausted its fuel supply during climbout. During the ensuing autorotation landing, the rotor speed was allosed to decay and the helcopter spun at touchdown. It rolled over and failed the rotor blades.NTSB SEA74FYE43Accident · Serious injuriesClosedHughes 269B · Seattle, WANTSB SEA68A0059Accident · No injuriesClosedHughes 269B · Walla Walla, WA
FAA incident reports on N9332F · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 19960601012369AHughes 269B · Georgetown, CAPractice autorotation reported power was lost. Reported soft forced landing but rocked forward. Rotors hit airframeAccident 19861022049699AHughes 269B · Fairbanks, AKThe engine failed. The hellicopter rolled over on forced landing. Cause of engine failure is undetermined.Accident 19740418009729AHughes 269B · Seattle, WAIp hit on head while dptng heli,m/r still rotating. Ip 6 ft 3 in tall.