Aircraft that carried N91620 · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N91620 now.
NTSB investigations on N91620 · 3
Of this N-number, whichever aircraft carried it.
NTSB SEA03TA060Accident · No injuriesFinal reportMcDonnell Douglas 369E · Plentywood, MTAircraft control was not maintained during a hovering turn. High wind conditions and excessive remedial action were factors.NTSB FTW84LA018Accident · No injuriesLimited investigationFinal reportCessna 182M · Aline, OKBefore departing norman, OK, the plt obtained a wx briefing from the Oklahoma city fss. During that briefing, he was advised that VFR flt was not recommended. He then took off for dodge city, KS without filling a flt plan. However, en route, he encountered wx…NTSB LAX76AL095Accident · 1 fatalClosedCessna 182 · Santa Barbara, CA
FAA incident reports on N91620 · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Accident 20030411007399AHughes 369E · Plentywood, MT(-23) After being hit by a gust of wind while making a pedal turn during a hover, a public use helicopter operated by the U.S. Border patrol experienced a tail rotor strike. During the subsequent rollover, the aircraft received substantial damage. The…Accident 19831007053769ACessna 182M · Aline, OKDue to worsening weather pilot landed in a field en route. Soft mud caused a flipover. VFR flight not recommended.Accident 19760920035909ACessna 182M · Santa Barbara, CARecovered on mtn slope 9/21/76.