A US military Osprey aircraft crashed off the coast of Japan’s Yakushima Island in southern Kagoshima prefecture on Wednesday, with eight people on board, according to a spokesperson from the Japan Coast Guard.
I always thought these had a reputation for being a real life version of the fallout vertibird and unfortunately they seem to have lived up to that here.
While the Osprey is the best of both worlds in terms of range, speed, and operational flexibility, it’s the worst of both worlds in terms of engine-out survivability. It doesn’t have enough wing area to glide like a plane to a safe landing, and the rotors don’t have enough inertia to preform an autorotation landing like a helicopter, unless the aircraft was already configured for vertical flight. Training pilots is also difficult, as you basically need someone who’s skilled in both helicopter and fixed-wing flight.
Because they're complicated and prone to failure and aerodynamic issues. But they fill a niche of a VTOL C-2, or a Chinook with twice the range and half again as much velocity so they're not going anywhere.
I read that the rotors share a common drive shaft that runs all the way across to keep them locked in sync and so one engine can power both equally. I guess they feather the blades differentially to control bank angle?
I'm not able to find it in the video linked below right now, but if I remember correctly, helicopter programs are pretty deadly in general. The Apache and other helicopters had a bunch of crashes when they were introduced, they just have had much longer to work out all the problems. But I don't remember what the exact failure rate comparison is, especially since you'd need to adjust for fight hours. The Osprey is definitely pretty complex with it's folding wings and rotors.
One of my college professors was involved in the development program for ~4 years, and said it was (one of?) the most stressful experiences of his life.
Major General Craig Olson, he (and his wife) are some of the most caring people I've met, I'm sure the weight of managing a program like that was a lot to bear. Looks like he left the program shortly after the March 2006 accident. He presented on some of the engineering challenges they faced and solved in the program (especially failure modes), but my memory is hazy.