LHX Program

[Orionblamblam]

Quite so.

So... someone wanted to do the UH-60 what was done to the UH-1 to make the Cobra.

 

[hesham]

From Army Aviation 1988/1 & 8-9,

who can collect the two pieces ?

 

[hesham]

From Army Aviation 1988/11.

 

[hesham]

Also from Army Aviation 1989/1,3-4,6 & 11 and 1990/ 1,2,3-4

 

[hesham]

Finally,from Army Aviation 1990/ 8-9,10,11,12

 

[Antonio]

Collected from two pieces

 

[yasotay]

Recently on eBay. I'm grading this as pre-LHX as the AAH/S-70 mashup (the S-71) looks significantly different.

Blackhawk, son of Blackhawk ... and grandson of Blackhawk.

 

[hesham]

From Army Aviation 1991/1.

 

[BRTip]

Artist's impression (top) of Bell/McDonnell Douglas "SuperTeam" LHX concept.

Artist's impression (second) of Boeing/Sikorsky "FirstTeam" LHX concept.

Artist's impression (third) of Boeing/Sikorsky "FirstTeam" LHX concept.

Artist's impression (fourth) of Bell/McDonnell Douglas "SuperTeam" LHX concept.

Source:

https://flic.kr/p/3e3CAT

View: http://www.flickr.com/photos/aviatorr727/1460341335/sizes/o/in/photostream

Stingray's Rotorcraft Forum

Discussion forum about helicopters and other rotorcraft - a part of the world's largest rotorcraft archive, "Stingray's List of Rotorcraft"

stingraysrotorforum.activeboard.com

Stingray's Rotorcraft Forum

Discussion forum about helicopters and other rotorcraft - a part of the world's largest rotorcraft archive, "Stingray's List of Rotorcraft"

stingraysrotorforum.activeboard.com

Over the past few months the SuperTeam LHX, and Comanche/aviation in general, have come across as hot questions for me - 35 years after we lost.

Just about everything I'm reading matches precisely with the public marketing materials - and has no relation to the real design or issues.

First, I was Tiger Team capt for the whole thing, sent in to rescue the project because it was failing due to radar cross section being orders of magnitude out of compliance. I had gotten an MS in rotorcraft design from Army CERT and paid for it by working for the GTRI RadLab - analyzing the Bat. They all LOOKED SO COOL and didn't work so well. I reported directly to Sam Hurt and Chuck Landers (MDHC) and Frank Harris (Bell-Textron.)

Starting with the punchline, the Superteam effectively nobid the proposal. Mgt used different wording. Someone in Congress/DOD/Army/DC decided they were tired of being scammed by LCSCs (Lying Cheating Stealing Contractors) and added a Risk Reduction Bonus to the scoring criteria. For budgetary reasons, the army refused to do a "fly before we buy" as the AF did with YF-22/YF23*. If a team put up $750,000,000 of their own money, to show they were serious, they would get a 5 pt bonus on the Management Volume of the proposal. There were three volumes, Tech, Cost and Mgt. The Superteam won Tech and Cost. We concluded that the program was likely to be cancelled after the demonstration phase, because the Iron Curtain had fallen, the Cold War was over and "we (voters)" were closing bases and trying to cash in on the Peace Dividend. We calculated that we would never recover the $3/4 billion, assumed the other guys would make the same decision and refused to fork it over.

Boeing/Sikorsky paid up. That gave them a 5pt edge. Word is we lost the mgt volume by 2 or 3 pts. That's the ultimate cause of the loss.

Because MDHC was in Mesa, AZ, a large number of former AVSCOM staff had relocated because they planned to retire in AZ - so we got a lot of backdoor info. About 3 weeks after project award, the folks at AVSCOM were telling us "we chose the wrong vehicle."

I'm told that somewhere in the congressional record is a quote that "there's not enough polish on earth to make this turd [Comanche] shine." The formal statement was "the vehicle does not do the job it is required to do." As Paul Martin Jr told me a view years ago, Comanche was a Hot Rod! It could fly 160 knotts - in reverse!!!! Unfortunately, that's a cool feature which is not required by army aviation - since no army helicopter has ever been in air to air combat against another rotorcraft, and it's so fast do do a 180 and run away forward at 180 knotts.

You cannot evalute new army rotorcraft without studying past failures - particularly AH-56 Cheyenne (https://en.wikipedia.org/wiki/Lockheed_AH-56_Cheyenne) The Cheyenne is, arguably, the most impressive rotorcraft ever built, but the delays and cost overruns were so high - the army decided the Vietnam war would be over before Cheyenne was deployed, and Bell came in with the AH-1, modified from the UH-1 at 1/4 to 1/3 the cost. There was specific direction during AH-64 selection - "we DO NOT want another Cheyene. Minimal risks. Minimal speed." This attitude prevails to this day. The army is concerned that pushing the tech envelope will result in another, embarrasing, failed "bridge too far."

Another issue was that around 1976, I was told at a dinner party, the US Dept of Commerce had concluded that McDonnell Douglas was going to go out of business and Fed Gov should avoid doing business with them. That was on top of the DC-10 fiascos (latter section of this article https://www.linkedin.com/pulse/what...on-anwcc/?trackingId=UTgvINBmRBG9EB9OgC2pnw==). Insider info is that the army Source Selelection and Evaluation Board (SSEB) for Apach had been told "try not to select Hughes," but the the Boeing proposal had unfixable red flags and the Bell proposal has a 4' span, two bladed, teetering rotor. The Apache didn't so much win as the other guys lost.

The Bat!! Imagine a V-280 Valor, with radar reduction chines and a midwing. They are the same configuration, except V-280's engines don't rotate, the gearbox does - and it's bigger.

There is a shopping list of issues each of which could be a chapter in a book. Col Dan Schrage, retired Cmdr AVSOCOM and professor of rotorcraft design, is currenlty writing those books.

IMO, the biggest issue is that "you need a cool, new, glamorous feature" to convince congress you're different enough to justify one trillion dollars in taxpayer money. For LHX it was radar stealth and reduced risk of tail rotor strikes on ground crews. I was lead on radar stealth at MDHC and there was no record of an army helicopter being downed by a radar guided missile or gun. It may be possible to make low flying rotorcraft undetectable on radar, but flying in the canyons and below tree line is nearly as effective - for a fraction of the cost and complexity. While tailrotor strikes accounted for about 1/2 of ground crew deaths, and are horrific, ground crew deaths themselves are almost unheard of. NOTAR was based on a nerly non-existant requierment. They key differentiators were not powerful enough to justify such an expensive program.

Ultimately, LHX (and whatever the upcoming effort will be called) was intended to replace the OH-58 Kiowa (Bell Jet Ranger.) OH-58 has an empty weight of 1,500 lbs. LHX had a target weight of 10,000 lbs, in order to hold all the cool new avionics, guns and missiles. The orginal proposal included an air ambulance and transport version. I did my MS thesis on that one. That was dropped before I graduated in 1991.

If you build a 10,000 lb vehicle, which does ten times what OH-58 does at 50 times the cost - you still need OH-58s for the majority of jobs, because it's cheap, easy and you need about 3,000 of them.

Whatever the army does in the future, they need about 3,000 light weight, cheap, utility rotorcraft to fill the existing role of the OH-58. Otherwise, it's like buying a Ferrari to use as commuter car to take the kids to school. It does the new job GREAT, but can't do the old, boring, utility job. This is a root problem with B-1, B-2, B-22 and B-3. The B-52 does a lot of old, slow, boring things SO MUCH BETTER than the new super planes, that they can't make it obsolete.

The roll call -

Vehicle - first flight
B-52 - 1952
C-130 - 1954
UH-1 - 1956
707 - 1957
* I was born
OH-58 - 1962
OH-6 - 1962
AH-1 - 1965
AH-56 - 1967
737 - 1967
C-5 - 1968
747 - 1969
Hawker Harrier - 1968
F-14 - 1970
A-10 - 1972
F-15 - 1973
* I started high school
F-16 - 1974
AH-64 - 1975
F-18 - 1978 * I graduated high school
767 - 1981
757 - 1982
777 - 1984
* I graduated with an MS in aircraft/rotorcraft design
YF-22/YF-23 - 1990
V-22 - 1989
C-17 - 1991
* I left the industry because it was obvious there was going to be no major work in design
F-35 - 2006
787 - 2009

Since I graduated, we have fielded one new rotorcraft. Since I left the industry, there have been no new, deployed, large rotorcraft programs.

I go to this length, because this is a fundamental problem of our age - from aviation to energy. Replacing a well engineered, widely adopted product, which is driven by capability, not appearance, is extraordinarily expensive and difficult!!! A retired VP of Lockheed Skunkworks told me a few years ago "If we had to replace everything we have from scratch - we couldn't do it." We've lost out institutional memory and skillset to execute such large programs from scratch. More importanlty, our need is not desperate enough to justify the cost and risk.

And we desperately need breakthrough innovations - right quick.

Bob Tipton
Cofounder [Howard] Hughes Skunkworks

 

[yasotay]

One of the best post. Thank you. The machinations' of the federal government can be supremely frustration. I was a young aviator with visions of BATS going through my head at the time. I was going to fly LHX in my career. Alas.

Thank you.

 

[Dew]

Over the past few months..

Great post; thank you

 

[DWG]

Vehicle - first flight
...
777 - 1984

Nitpicking, doesn't affect the overall point, 777 first flight was 12 June 19_9_4. I was still at uni in '84, rather than working on the programme.

 

[overscan (PaulMM)]

One of the best post. Thank you. The machinations' of the federal government can be supremely frustration. I was a young aviator with visions of BATS going through my head at the time. I was going to fly LHX in my career. Alas.

Thank you.

Concur - nothing beats a view from the inside.

 

[BRTip]

Nitpicking, doesn't affect the overall point, 777 first flight was 12 June 19_9_4. I was still at uni in '84, rather than working on the programme.

Thanks for catching the typo "8"4 instead of "9"4. I just spotted that myself.

 

[BRTip]

One of the best post. Thank you. The machinations' of the federal government can be supremely frustration. I was a young aviator with visions of BATS going through my head at the time. I was going to fly LHX in my career. Alas.

Thank you.

I fully understand and sympathize with your viewpoint, but it's much more complicated than that. The real reasons behind this are part of my daily life, because my income depends on the answers.

Ultimately, congress does what the electorate wants them to do. Since the nation is so divided and can't agree on anything, neither can congress. Every time I've dug deeply into this, I've found about 90% of the people on the decision making end are trying to do what "someone" believes is best.

Good place to fill in the "*" YF-22/YF-23. I was called in on that one for some specialized materials consulting, but I worked with Denny Elking and Gerry McClellen who were on the lead design team with Northrup folks like Lu Ping. No one thought losing BOTH LHX and ATF at the same time was possible. After all, MDC was the world's largest, longest lived aerospace defense contractor - but we lost both. Six months later MDC was gone and part of Boeing.

The rumor mill was that we'd lost YF-23 6 months before contract award because the AF softened the RCS requirement on the broadside of the vehicle. We were passing with margin, so the only logical reason to do that was so the other guys could win and someone wanted them to win. The leading explanations were "Northrup/MDC wouldn't create as many jobs in California as Lockheed/Boeing, so the CA delegation wanted Yf-22 to win" and "the AF was grateful to Lockheed for all their stunning black project work and wanted them to get a big win."

On a more practical, and infuriating, note. The AF had not written an air-to-air combat test into the contract. Lockheed/Boeing did one at their expense. MDC kept pushing to do the same, but Northrup took the position that "if it's not required in the contract, we're not doing it" and we never did the dogfight test. On paper, YF-23 was a better dogfighter, even without vectored thrust, but since we never flew the tests, we'll never know.

One thing I've learned during my life is that to really screw something up, there must be multiple mistakes at the same time and most people are about 90% right. That 10% wrong is what kills these things.

A more controversial issue is careerism and self promotion. So long as our livelihoods are intimately tied to the results of these large competitions - we will never choose the best system on it's technical merits.

 

[fightingirish]

I don't know, if this video has been posted before.

BT 3581 Superteam LHX Technology Evolution

View: https://youtu.be/ufceBkRaLgo?si=-LkNNrpcGI9IynHb

 

[ZacYates]

Thank you so much for your posts Bob.

 

[jalles]

Does anyone know a source for three view drawings or blueprints of the MDC/Hughes NOTAR high-speed LHX?

 

[sferrin]

I fully understand and sympathize with your viewpoint, but it's much more complicated than that. The real reasons behind this are part of my daily life, because my income depends on the answers.

Ultimately, congress does what the electorate wants them to do. Since the nation is so divided and can't agree on anything, neither can congress. Every time I've dug deeply into this, I've found about 90% of the people on the decision making end are trying to do what "someone" believes is best.

Good place to fill in the "*" YF-22/YF-23. I was called in on that one for some specialized materials consulting, but I worked with Denny Elking and Gerry McClellen who were on the lead design team with Northrup folks like Lu Ping. No one thought losing BOTH LHX and ATF at the same time was possible. After all, MDC was the world's largest, longest lived aerospace defense contractor - but we lost both. Six months later MDC was gone and part of Boeing.

The rumor mill was that we'd lost YF-23 6 months before contract award because the AF softened the RCS requirement on the broadside of the vehicle. We were passing with margin, so the only logical reason to do that was so the other guys could win and someone wanted them to win. The leading explanations were "Northrup/MDC wouldn't create as many jobs in California as Lockheed/Boeing, so the CA delegation wanted Yf-22 to win" and "the AF was grateful to Lockheed for all their stunning black project work and wanted them to get a big win."

On a more practical, and infuriating, note. The AF had not written an air-to-air combat test into the contract. Lockheed/Boeing did one at their expense. MDC kept pushing to do the same, but Northrup took the position that "if it's not required in the contract, we're not doing it" and we never did the dogfight test. On paper, YF-23 was a better dogfighter, even without vectored thrust, but since we never flew the tests, we'll never know.

One thing I've learned during my life is that to really screw something up, there must be multiple mistakes at the same time and most people are about 90% right. That 10% wrong is what kills these things.

A more controversial issue is careerism and self promotion. So long as our livelihoods are intimately tied to the results of these large competitions - we will never choose the best system on it's technical merits.

Another good example of this is the F-111. The USAF said, "we want Boeing". McNamara said, "no, you want General Dynamics. My boss even said so."

 

[hesham]

From Army Aviation magazine 1980 .

From Army Aviation 2003/12.