Aircraft that carried N350SW · 1
The FAA can assign a mark to another aircraft once a registration is cancelled. No aircraft carries N350SW now.
NTSB investigations on N350SW · 2
Of this N-number, whichever aircraft carried it.
NTSB SEA05IA040Incident · No injuriesIncident investigationFinal reportBoeing 737-3H4 · Seattle, WAThe flight crew's failure to maintain an adequate visual lookout while on final for a visual approach. Factors include the failure of both airport operations personnel and the local FAA Airports Inspector to insure that some form of identification marking was…NTSB CHI93IA354Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · St. Louis, MOa failure of the left outboard foreflap due to the loss of the bolts that hold the inboard sequencing carriage to the foreflap attach lug.
FAA incident reports on N350SW · 3
Filed on this N-number, whichever aircraft carried it. Each report names the aircraft it was matched to.
Incident 19961031039939IBoeing 7373H4 · Salt Lake City, UTNarrative: on October 31, 1996, aircraft 350SW, southwest flight #411, from phoenix, AZ enroute to Salt Lake City, UT declared an emergency at FL350 due to a gradual loss of pressurization. Aircraft made an uneventful landing at Salt lake international…Incident 19930908036619IBoeing 7373H4 · St Louis, MOMade go around due to traffic. Left trailing edge flaps failed. Parts of flaps hanging loose. Landed safely.Incident 19900913049159IBoeing 7373H4 · Burbank, CAAft cargo door warning on climb. Returned. Sensor assembly was repositioned to proper place.