First off, at over 390 pages, this is not light reading.
Different people will have different takes.
Is this the Marine Corps and a dedicated set of companies, lobbyists and politicians fighting for, and ultimately winning, a battle to bring next-gen aerospace tech into being?
Or is this a hideous case of pork-barrel spending, long-term, writ large?
A reader could take either from this book. Because, quite frankly, it's at the intersection of both.
I remember reading about Bell's XV-15 back when I was a kid (I was 9 when it first flew). I remember how it going was "going to revolutionize small airports" because it didn't need a runway. It could takeoff and land like a helicopter but it could "transition" to flying like an airplane. The history actually goes back much further than that; people were trying to create various types of "convertiplanes" back before WW II. And, indeed, Bell had an earlier aircraft (XV-3; look it up on Wikipedia) which could do this. But none of them did it well. What was needed was a combination of lightweight materials tech and high-power-density engine tech to mature, in parallel, until you could make something small enough with powerful-enough engines to do it.
Seems kinda obvious in retrospect. That's a common characteristic about "retrospect" which no one sees "looking forward."
Pretty sure there's only one XV-15 left in the world, sitting in the Udvar-Hazy annex of the Smithsonian Air and Space Museum (shaded under the wing of a Concorde, IIRC). Been there, done that, got the t-shirt (no, seriously, I have a t-shirt from that place), have pictures of the plane. In that place, I was like a kid in a candy store. So much interesting stuff to see. So much interesting history. But I digress.
I learned a lot about how the modern military procurement process works. So I understand what it means when they say the F-35 is in LRIP status. If you compare it to software:
* alpha testing = prototypes (there were ... 6 of these; many of them demolished)
* LRIP = beta testing (military flying them, flushing out bugs the mfrs didn't find, still lots of manual labor involved in building so still very expensive)
* full production = shipped (still fixing bugs but that's largely behind them; mass production in progress so price starts coming down)
Yes, there were some nasty accidents with these birds. You will get names, some pictures, lots of bio info on the major people involved in said accidents. I'd never heard of vortex ring state until I read this book (that's what took out one of the LRIP models, killing 2 pilots, 2 crew chiefs and 15 Marine infantrymen). It's kinda like wing vortex issues on a fixed wing plane, but applied to helicopter rotors. And about as unexpected and unwelcome. Some people considered the fact that the V-22 has two rotors to be a lethal, un-fix-able flaw; if one of them goes into ring vortex state, you lose lift on one side and the plane flips (which is exactly what happened). How do you fix that? You can't, they argued, therefore it has a fatal flaw. Well, you can't get entirely rid of it but all helicopter pilots are trained in vortex ring state (also known as settling with power), how to avoid it, how to detect it, how to get out of it. Once testing made that a known quantity, the fly-by-wire flight controls and the well-trained pilots have been able to avoid it.
There were so many corners cut, so many things "skipped" along the way. It did NOT go into full production until they had, at long last, exhaustively tested the aircraft and its flight envelope. In the end, it did pass those tests. But a lot of money was spent and a lot of lives lost while trying to "shortcut" their way through. There have been considerably fewer incidents since the exhaustive testing was actually done and all found issues fixed.
In software development, there's an (unfortunate) adage: we never have time to do it right, so we have to find time to do it over. Anytime you're developing something, there will be pressure to "just get it done." As a result, all too often, the "1.0 version" will have some serious issues and you may have to wait for the 2.x version (not just the 1.1) before it gets good (Windows didn't get decent until 3.0). Sad to say, that's not the case JUST in software development. And yes, it was the V-22B (second major version) which finally passed the tests and went into production.
I'm a fan of the plane. So I wanted to see it "win." And, ultimately, it does.
Can't say as it will revolutionize civil aviation; the high-power-density turboprops are pretty expensive. Presumably, it would be possible to do something like an XV-3 (engine in the fuselage, shafts through the wings driving the props) but that would be mechanically complex (it was in the XV-3) and, consequently, fragile. And it making anything bigger than a 2-seater would require a pretty potent engine. The smaller your rotor(s), the more horsepower you need, per pound, to takeoff vertically and hover. Piston-powered helicopters typically have a 2-bladed rotor (keeping it as simple as possible) with a wide span, so as to minimize power : weight needed. A General Aviation tiltrotor would likely end up with a props / rotors smaller than a helicopter and the wing would have to have enough wingspan that the props / rotors wouldn't hit the fuselage in the middle.
That was a problem with the Osprey, compounded by the fact that it had to be able to maneuver on the deck of a Marine assault craft without hitting the "island" with a spinning rotor and without sending the landing gear, on the other side, over the side of the deck. That imposed a very definite maximum rotor- and wing-span. Which, in turn, meant it needed more powerful engines. Which are heavier. Which means you need stronger (heavier) wings. Which means you need more powerful engines ....
The author does not play fast 'n loose here. The book is the culmination of a lot of personally-witnessed events (he was a correspondent who got to be embedded with a V-22 squadron, along with various, prior experiences with the bird) and a lot of interviews with the people involved.