<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>Defense Tech &#187; Trimble on the Case</title> <atom:link href="http://defensetech.org/category/trimble-on-the-case/feed/" rel="self" type="application/rss+xml" /><link>http://defensetech.org</link> <description>The Future of the Military, Law Enforcement and National Security</description> <lastBuildDate>Fri, 12 Mar 2010 18:49:47 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>Sidewinder Ground Missile</title><link>http://defensetech.org/2009/12/14/sidewinder-ground-missile/</link> <comments>http://defensetech.org/2009/12/14/sidewinder-ground-missile/#comments</comments> <pubDate>Mon, 14 Dec 2009 18:23:41 +0000</pubDate> <dc:creator>christian</dc:creator> <category><![CDATA[Missiles]]></category> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://defensetech.org/?p=5208</guid> <description><![CDATA[
Network member Ned Conger sent this one along today that caught me by surprise.
Turns out the Pentagon has been tweaking the software a bit on the AIM-9X  Sidewinder to hit ground targets. Strategy Page reported it but our boy Steve Trimble had it as well — and the StratPage entry calls it the AIM-7x — [...]]]></description> <content:encoded><![CDATA[<p
style="text-align: center;"><a
href="http://defensetech.org/wp-content/uploads//2009/12/F15-sidewinder.jpg"><img
class="size-full wp-image-5209 aligncenter" title="F15-sidewinder" src="http://defensetech.org/wp-content/uploads//2009/12/F15-sidewinder.jpg" alt="F15-sidewinder" width="440" height="294" /></a></p><p>Network member Ned Conger sent this one along today that caught me by surprise.</p><p>Turns out the Pentagon has been tweaking the software a bit on the AIM-9X  Sidewinder to hit ground targets. Strategy Page reported it but our boy Steve Trimble <a
href="http://www.flightglobal.com/blogs/the-dewline/2009/12/aim-9x-goes-slumming-with-air-.html" target="_blank">had it as well</a> — and the StratPage entry calls it the AIM-7x — oops… From Flight Global:</p><blockquote><p>The modification allows the same AIM-9X to strike both air and ground targets. Jeff White, Raytheon’s business development manager for AIM-9X, declines to describe the modification in detail, but says it involves only software changes. The AIM-9X infrared seeker, proximity fuse and blast/fragmentation warhead remain unchanged.</p><p>During a 23 September Gulf of Mexico test, a US Air Force <a
href="http://www.flightglobal.com/landingpage/f-15.html">F-15C</a> fired the air-to-surface AIM-9X and hit a speeding “cigar boat”, a type commonly used by drug smugglers. “The missile went right through the boat,” says White.</p><p>The F-15C test follows a previous shot by an <a
href="http://www.flightglobal.com/landingpage/lockheed%20martin%20f-16.html">F-16</a> at a similar target, which also scored a hit on the boat, he adds.</p></blockquote><p>Anyway, seems as if Raytheon has done some rejiggering to allow the F-15C (and F-22) a ground attack role with its compliment of side-shooting Sidewinders. The combination of the helment-mounted cuing systems and highly advanced heat seakers allow the air-to-air missile to plink hot targets on the ground as well.</p><p>Sounds like a darn good idea. I’d be interested to learn what the damage yield is with one of those puppies. A 20 pound blast frag warhead doesn’t seem like much to me, but it sounds like it could be effective against vehicles. And after all, the AGM-114 Hellfire has a nearly 30 pound warhead and has no problem taking out HVTs.</p><p>– Christian</p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2009/12/14/sidewinder-ground-missile/feed/</wfw:commentRss> <slash:comments>51</slash:comments> </item> <item><title>Has the Chinook met its FATE?</title><link>http://defensetech.org/2008/07/29/has-the-chinook-met-its-fate/</link> <comments>http://defensetech.org/2008/07/29/has-the-chinook-met-its-fate/#comments</comments> <pubDate>Tue, 29 Jul 2008 18:17:27 +0000</pubDate> <dc:creator>Ward</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=3976</guid> <description><![CDATA[
The first Boeing CH-47, a 33,000lb machine powered by two 1,640shp Lycoming (now Honeywell) T55 engines, achieved first flight on Sept. 21, 1961.
Nearly 47 years and seven major upgrades later, the CH-47F and MH-47G has doubled in weight to 50,000lb, while the engine shaft horsepower rating has tripled with introduction of the 4,868shp T55-GA-714 powerplant.
With [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="old-47.jpg" src="http://www.defensetech.org/images/old-47.jpg" width="207" height="250" hspace="10" vspace="5"/></p><p>The first Boeing CH-47, a 33,000lb machine powered by two 1,640shp Lycoming (now Honeywell) T55 engines, achieved first flight on Sept. 21, 1961.</p><p>Nearly 47 years and seven major upgrades later, the CH-47F and MH-47G has doubled in weight to 50,000lb, while the engine shaft horsepower rating has tripled with introduction of the 4,868shp T55-GA-714 powerplant.</p><p>With only 10% of the CH-47F delivered, however, Boeing is again proposing to radically increase the size of the airframe. The “growth Chinook” would be stretched and widened to accommodate and up-armored HMMWV (Humvee) inside the cabin. This would increase maximum takeoff weight to around 70,000lbs and demand a much larger engine. Honeywell has already proposed a roughly 6,000shp T55-GA-715.</p><p>It’s still unclear what the army thinks about all this. After all, the army is planning to buy another 400 CH-47Fs. It’s also still debating how much it needs a Joint Heavy Lift rotorcraft that would be more than twice the size of the CH-47F.</p><p>On top of all this, the army has also started a program to replace the venerable T55 with an all new engine in the 6,000shp to 7,000shp range after 2018. Last week, I confirmed that Honeywell, Pratt &amp; Whitney and General Electric are each participating in the earliest stages of the Future Affordable Turbine Engine (FATE) program.</p><p><span
id="more-3976"></span></p><p>All this really means is that no one can predict the future of the army’s heavylift rotorcraft needs after 2015, when the Future Combat System will allegedly be fielded. When the future of FCS is finally settled, the army will have a range of good options for a Chinook replacement.</p><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline/">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/07/29/has-the-chinook-met-its-fate/feed/</wfw:commentRss> <slash:comments>86</slash:comments> </item> <item><title>Code name alert: Is Liberty Ship a new Big Safari?</title><link>http://defensetech.org/2008/07/24/code-name-alert-is-liberty-ship-a-new-big-safari/</link> <comments>http://defensetech.org/2008/07/24/code-name-alert-is-liberty-ship-a-new-big-safari/#comments</comments> <pubDate>Thu, 24 Jul 2008 18:42:12 +0000</pubDate> <dc:creator>Ward</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=3966</guid> <description><![CDATA[
The US Army has Constant Hawk. The US Marine Corps has Angel Fire. Somebody has something called Highlighter.
What the heck are they?
Constant Hawk, Angel Fire and Highlighter are the names of manned, light aircraft that have been invented since the Iraqi occupation began to fight against the scourge of improvised explosive devices.
Public details vary greatly [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="liberty-ship.jpg" src="http://www.defensetech.org/images/liberty-ship.jpg" width="250" height="250" hspace="10" vspace="5"/></p><p
class="MsoNormal">The US Army has Constant Hawk. The US Marine Corps has Angel Fire. Somebody has something called Highlighter.</p><p
class="MsoNormal">What the heck are they?</p><p
class="MsoNormal">Constant Hawk, Angel Fire and Highlighter are the names of manned, light aircraft that have been invented since the Iraqi occupation began to fight against the scourge of improvised explosive devices.</p><p
class="MsoNormal">Public details vary greatly for each of these semi-classified aircraft programs. Thanks to funding and turf wars, we know quite a bit about <a
href="http://www.flightglobal.com/articles/2006/08/22/208557/shorts-360-constant-hawk-system-heads-for-iraqi-theatre.html">Constant Hawk</a> (a modified Shorts C-23B Sherpa) and Angel Fire. [USA Today article is <a
href="http://www.usatoday.com/news/military/2007-10-02-angel-fire_N.htm">here</a>. Great analysis by StrategyPage.com is <a
href="http://www.strategypage.com/htmw/htecm/articles/20071012.aspx">here</a>.]<br
/> <span
class="mt-enclosure mt-enclosure-image" style="DISPLAY: inline"><a
onclick="window.open('http://www.flightglobal.com/blogs/the-dewline/constanthawk.html','popup','width=330,height=330,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false" href="http://www.flightglobal.com/blogs/the-dewline/constanthawk.html"></a></span></p><p
class="MsoNormal">The US Army Material Command was even generous enough to post a photo of Constant Hawk on their <a
href="http://flickr.com/photos/armymaterielcommand/888893870/">Flickr page</a>.</p><p
class="MsoNormal">All I know about Highlighter is that it was invented by the Joint IED Defeat Organization (JIEDDO), and it is an aircraft. (Dear Maj Gen Montgomery Meigs, Thank you for disclosing Highlighter’s existence in a commentary you wrote to “correct” a critical Marine Corps Times editorial on April 16, 2007.)</p><p><span
id="more-3966"></span></p><p
class="MsoNormal">We may — finally — have a clue about how all of these ideas were invented.</p><p
class="MsoNormal">It could be a project office embedded in the Office of the Secretary of Defense [OSD] called “Liberty Ship”.</p><p
class="MsoNormal">Perhaps modelled on the US Air Force’s famed <a
href="http://www.fas.org/irp/program/collect/big_safari.htm">Big Safari</a> project office in Dayton, Ohio, OSD may be using Liberty Ship to skirt around the traps and tripwires of the military’s acquisition system.</p><p
class="MsoNormal">The code word Liberty Ship was first mentioned in a public forum earlier this week by General Norton Schwartz, OSD’s nominee to become the next USAF chief of staff.</p><p
class="MsoNormal">Before his nomination hearing, the Senate armed services committee posed written questions to Schwartz, including one query about how he would address the shortfall of spy aircraft in Iraq.</p><p
class="MsoNormal">Schwartz replied in writing:</p><blockquote><p
class="MsoNormal"><font
style="FONT-SIZE: 0.8em"><font
style="FONT-SIZE: 1.25em">“</font><font
style="FONT-SIZE: 1.25em">By increasing the number of MQ-9 vehicles, pursuing the “Liberty Ship” construct for acquisition of more “light” manned ISR aircraft, and accelerating the development of the Wide Area Airborne Surveillance sensor system, the Air Force is working very hard to get more ISR capability to the combatant commanders in support of on-going operations. If confirmed, this will have my personal attention from day one.“</font></font></p></blockquote><p
class="MsoNormal">For background, here’s an excerpt from the Senate armed services report published in May on the fiscal 2009 defense budget request.</p><blockquote><p
class="MsoNormal"><font
style="FONT-SIZE: 1em">“The Army Constant Hawk and Marine Corps Angel Fire systems are current examples of wide-area collection systems. The DOD leadership requested funds for the Air Force to acquire a combined, enhanced system, currently called Wide-Area Airborne Surveillance (WAAS), to image a larger area than Constant Hawk or Angel Fire, enable night operations, real-time support to ground forces, provide a forensic capability, and support many simultaneous targeting and surveillance missions. It could cue and hand off targets to [full motion video] platforms for prosecution.“</font></p></blockquote><p>Liberty is not a common prefix for a code name. According to William Arkin’s Code Names reference book, there are only two other known Liberty prefix’s in the Pentagon’s classified lexicon:</p><blockquote><ol><li>Liberty Shield, a Department of Homeland Security operation to increase security at the nation’s critical infrastructure</li><li>Libertycap, a National Security Agency program to standardize all signals intelligence software</li></ol></blockquote><p>Clearly, these code names — Angel Fire, Highlighter, Constant Hawk, Liberty Ship — are the barest glimpse into the massive, multi-billion dollar and ambiguous effort to thwart the threat of IED attacks. I can’t wait to read the book someday.</p><p>[[PS: Don’t forget <a
href="http://www.flightglobal.com/blogs/the-dewline/2008/02/green-darts-back-but-still-cla.html">Hunter Green Dart</a>!]]</p><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline/">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/07/24/code-name-alert-is-liberty-ship-a-new-big-safari/feed/</wfw:commentRss> <slash:comments>9</slash:comments> </item> <item><title>Oops! Will the US Air Force lose Joint STARS?</title><link>http://defensetech.org/2008/06/09/oops-will-the-us-air-force-lose-joint-stars/</link> <comments>http://defensetech.org/2008/06/09/oops-will-the-us-air-force-lose-joint-stars/#comments</comments> <pubDate>Mon, 09 Jun 2008 12:00:21 +0000</pubDate> <dc:creator>Ward</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=2895</guid> <description><![CDATA[
I believe I have seen the future replacement for the E-8C Joint STARS fleet (shown pictured), and it’s not going to be a US Air Force aircraft.
The US Navy is preparing to replace the EP-3E ARIES II, an electronic intelligence aircraft, with a new-start acquisition program called EPX.
But the navy’s requirements for EPX call for [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="jstars.jpg" src="http://www.defensetech.org/images/jstars.jpg" width="300" height="195" hspace="10" vspace="5"/></p><p>I believe I have seen the future replacement for the E-8C Joint STARS fleet (shown pictured), and it’s not going to be a US Air Force aircraft.</p><p>The US Navy is preparing to replace the EP-3E ARIES II, an electronic intelligence aircraft, with a new-start acquisition program called EPX.</p><p>But the navy’s requirements for EPX call for an aircraft that would not only spy on enemy electronic signals, like the EP-3E, but also find and track moving targets, like the E-8C.</p><p>Interestingly, the EPX program of record will acquire 19 to 26 aircraft to replace only 11 EP-3Es flying today. At the high end of that range, 26 aircraft would nicely replace all 11 EP-3Es and all 17 E-8Cs in service. (One E-8C is a testbed, and doesn’t count.)</p><p>If the air force can’t pay for an E-8C replacement to appear after 2015, or even to modernize the radar on the current fleet, watch for the navy to steal this mission with the EPX. It’s the roles and missions equivalent of a pick-pocketing.</p><p>And it’s happened before. In 1998, the air force lost the EC-135 Looking Glass mission to the navy’s E-6 take-charge-and-move-out (TACAMO) aircraft. Now, it’s happening again, unless the air force acts very quickly.</p><p>This all became clear to me during my weeklong tour of Boeing’s defense sites based in the Pacific Northwest. Paul Summers, Boeing’s capture lead for EPX, briefed reporters about the navy’s requirements, explaining that the size of the future EPX fleet had grown from 14–19 aircraft to 19–26 aircraft since last year.</p><p>The obvious question later occurred to me: Why does the navy need 26 EPX aircraft to replace 11 EP-3Es. Clearly, the navy has bigger ideas for this fleet.</p><p>Paul also discussed the new radar for the EPX. This in itself is noteworthy. The EP-3E does not have a radar. The aircraft intercepts and maps enemy communications and other electronic transmissions.</p><p>We’ve known for about a year that Boeing and Raytheon have installed the new littoral surveillance radar systems (LSRS) on a subset of the P-3C fleet, giving the navy its own mini-Joint STARS capability.</p><p>It is now clear that the LSRS is the proverbial trojan horse, injecting the navy into the Joint STARS business for the long-term.</p><p>Paul also explained that Boeing will consider the LSRS or another radar for EPX. The only possible alternative is a new variant of Northrop Grumman’s wide area surveillance sensor developed under the multi-platform radar technology insertion program (MP-RTIP).</p><p>This will force Northrop to make a tough choice. Northrop, you see, is the prime contractor the E-8C, so it has everything to lose if the navy takes over the mission. However, if the company decides to join Boeing’s EPX bid, that could be a signal that it believes the air force will never get around to replacing the E-8C.</p><p>The navy has money in the budget beginning next year to launch EPX. The air force has no funds to replace E-8Cs for the foreseeable future, and now faces a potentially disruptive leadership transition.</p><p>I’m not a betting man, but, if I was in Northrop’s position, I know where I’d place my bet.</p><p>The air force has only itself to blame. The folly of the E-10 program, which spectacularly failed to combine an E-8C, and E-3A AWACS and an airborne operations center onto the same platform, has left the air force without a discernible plan to replace its aging fleets of 707-based aircraft.</p><p>The air force’s only hope to stay in the E-8C business may be to observe the adage: if you can’t beat them, join them.</p><p>Establishing a true “joint” partnership to acquire and operate a new fleet of narrowbody-class aircraft to serve all of the specialized missions performed today by 707s looks like the only way back in. (This idea also has the charm of making sense.)</p><p>Indeed, it has been proposed several times in the past. The only difference now is that the air force won’t be calling the shots.</p><p><span
id="more-2895"></span></p><p>The navy, meanwhile, is not in this position merely through good fortune.</p><p>In 2004, the navy picked the Boeing P-8A — based on the 737-800ERX — to replace the P-3C, giving itself a versatile and capable platform to expand into new missions.</p><p>That’s not to say that Boeing won’t have to face challengers to win the EPX contract. The navy is inviting other companies to compete for EPX, but it will be difficult for the Airbus A320 and the Embraer E190 to overcome the incumbent advantages of the P-8A.</p><p>Paul Summers told us that Boeing had to make more than 50 modifications costing $1 billion to simply adapt the basic 737 airframe to meet the navy’s more demanding certification requirements. The A320 and the E190 would face similar costs, possibly killing the chances for holding a fair airframe competition on EPX.</p><p>I expect that the navy will try to level the playing field in other ways. Perhaps, the navy will select the P-8A as the baseline platform and invite bidders — including Boeing, Lockheed Martin and Northrop — to compete for the systems integrator role.</p><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline/2008/06/oops-will-the-us-air-force-los.html">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/06/09/oops-will-the-us-air-force-lose-joint-stars/feed/</wfw:commentRss> <slash:comments>6</slash:comments> </item> <item><title>Growler Day</title><link>http://defensetech.org/2008/06/03/growler-day/</link> <comments>http://defensetech.org/2008/06/03/growler-day/#comments</comments> <pubDate>Tue, 03 Jun 2008 19:00:45 +0000</pubDate> <dc:creator>Ward</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=2884</guid> <description><![CDATA[
In a drizzly ceremony today, we will witness Secretary of the Navy Don Winter accept the delivery of the first EA-18G Growler to the USN’s fleet readiness squadron.
This would be a fairly routine affair except for a couple of very distinguishing facts: first, the event is occurring exactly according to the original schedule and, second, [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="growler.jpg" src="http://www.defensetech.org/images/growler.jpg" width="300" height="192" hspace="10" vspace="5"/></p><p>In a drizzly ceremony today, we will witness Secretary of the Navy Don Winter accept the delivery of the first EA-18G Growler to the USN’s fleet readiness squadron.</p><p>This would be a fairly routine affair except for a couple of very distinguishing facts: first, the event is occurring exactly according to the original schedule and, second, Boeing’s five-year-old development program is not over-budget.</p><p>It’d be nice to think those two facts weren’t so extraordinary, but, in the world of military acquisition, it is.</p><p>To be sure, there remain a few caveats. The operational test phase begins in September, which will expose any unresolved design or technology glitches. The Government Accountability Office reported in March that a few software issues need to be fixed before operational tests can be performed. We’ll see how that pans out, but none of the issues sound like show-stoppers.</p><p>Some of the more cynical observers (blush) might also say that Boeing and the Navy cheated with the EA-18G.</p><p>This is not the same as starting a new weapon project from scratch. The airframe for the EA-18G is based on the design of the already proven F/A-18E/F Super Hornet and the electronic warfare package is based largely on the ICAP III suite already flying on the EA-6B Prowler. The ALQ-99 jammer is merely a decade-old, upgraded version of a pod that first flew in 1971 (and needs to be retired as threats evolve over the next decade).</p><p><span
id="more-2884"></span></p><p>But it’s also not fair to Boeing to dismiss the complexity of this project. Repackaging the ICAP III to fit inside the Growler involved no small risk. The “football” ALQ-218 receiver mounted on the EA-6B’s tail was split into two pieces and installed in the more aerodynamically harsh environment of the EA-18G’s wingtips. I’m still curious how they managed to pull off the ALQ-218’s radome, which must be sturdy enough to survive on the wingtip, yet not too sturdy to interfere with the operations of the embedded antenna.</p><p>Integrating the all-new Raytheon-made Communications Countermeasures Set (CCS) also added some complexity to the project, as did the introduction of the highly useful interference cancellation system (INCANS), which allows the EA-18G to continue jamming an enemy radar even while the pilot continues to communicate with other friendly aircraft.</p><p>It’s reasonable to question whether the navy should have been still more ambitious. Why not introduce an all-new, digital-era jamming pod with the first delivery of the EA-18G? Why not design a next-generation jammer aircraft around a more stealthy platform, like the navy’s forthcoming F-35C due to be delivered in 2015? Why not challenge your contractor — to which you’re paying billions of dollars — to invent something completely new, versus “repackaging” two familiar systems?</p><p>At the end of the day, the navy is getting exactly what it paid for, on-time. In this day and age, maybe that’s all you can really ask for.</p><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline/">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/06/03/growler-day/feed/</wfw:commentRss> <slash:comments>26</slash:comments> </item> <item><title>Why Do Commercial Platforms Make Such Lousy Military Aircraft?</title><link>http://defensetech.org/2008/04/02/why-do-commercial-platforms-make-such-lousy-military-aircraft/</link> <comments>http://defensetech.org/2008/04/02/why-do-commercial-platforms-make-such-lousy-military-aircraft/#comments</comments> <pubDate>Wed, 02 Apr 2008 11:46:54 +0000</pubDate> <dc:creator>Ward</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=2764</guid> <description><![CDATA[
The above is the question that the US Department of Defense is asking itself, courtesy of a new Defense Science Board Task Force chaired by Jacques Gansler. I wrote about the issue in a news analysis published this week in Flight International. I’ve posted an excerpt below, and you can read the full story here.Taking [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="airplane-construction.jpg" src="http://www.defensetech.org/images/airplane-construction.jpg" width="250" height="188" hspace="10" vspace="5"/></p><p>The above is the question that the US Department of Defense is asking itself, courtesy of a new Defense Science Board Task Force chaired by Jacques Gansler. I wrote about the issue in a news analysis published this week in Flight International. I’ve posted an excerpt below, and you can read the full story <a
target="_blank" href="http://www.flightglobal.com/articles/2008/04/01/222538/analysis-us-military-examines-pitfalls-of-relying-on-commercial.html">here</a>.</p><blockquote><p>Taking an “off-the-shelf” aircraft and adapting it for a new military role was supposed to be the cheap and easy alternative to designing an all-new platform.</p><p>So, in accord with the mantra “faster, better and cheaper”, US military services since 2001 have often turned to off-the-shelf derivatives of commercial and military aircraft to satisfy new and emerging requirements for a wide range of missions, including scout and utility helicopters, VIP transports, surveillance aircraft and aerial tankers, to name but a few.</p><p>The results, however, have proved disappointing. Far from removing cost and schedule risks, procurements based on off-the-shelf aircraft and similar equipment have led to some of the most expensive acquisition fiascos for the US military over the last decade.</p><p>Examples range from aborted efforts, such as the ERJ-145-based aerial common sensor (ACS) or the 767-400ER-based E-10A, to multi-billion dollar development fiascos, as endured by the EH101-based VH-71A presidential helicopter and the Bell 407-based ARH-71A armed reconnaissance helicopter.</p></blockquote><p><span
id="more-2764"></span></p><blockquote><p>Despite the dubious track record, off-the-shelf alternatives remain popular. A pending contract for an unmanned maritime surveillance aircraft, as well future procurements for new signals intelligence fleets, are all expected to rely on platforms originally designed to perform a different role.</p><p>Jacques Gansler, a former US undersecretary of defense for acquisition, technology and logistics (ATL), has been recruited to help solve the Department of Defense’s problem.</p><p>“A lot of the older systems also had the same characteristics” as today’s off-the-shelf aircraft programmes, Gansler says, adding: “We’ve just got a collection now of bad stories.”</p><p>Current ATL chief John Young has tapped Gansler to chair a task force aimed at evaluating the reasons why acquisition programmes based on off-the-shelf equipment often fail or face costly delays.</p></blockquote><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline/">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/04/02/why-do-commercial-platforms-make-such-lousy-military-aircraft/feed/</wfw:commentRss> <slash:comments>28</slash:comments> </item> <item><title>Have You Heard of This Bomb?</title><link>http://defensetech.org/2008/03/14/have-you-heard-of-this-bomb/</link> <comments>http://defensetech.org/2008/03/14/have-you-heard-of-this-bomb/#comments</comments> <pubDate>Fri, 14 Mar 2008 17:42:34 +0000</pubDate> <dc:creator>Ward</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=3897</guid> <description><![CDATA[
The US Air Force wants Boeing to integrate the GBU-57 bomb on the Northrop Grumman B-2A, or so says this solicitation document released earlier this week.
I find that very interesting on a number of levels, not least because the USAF has never before disclosed the existence of a weapon called the GBU-57!
(Designation-systems.net, in fact, [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="B2-fuel.jpg" src="http://www.defensetech.org/images/B2-fuel.jpg" width="250" height="159" hspace="10" vspace="5"/></p><p>The US Air Force wants Boeing to integrate the GBU-57 bomb on the Northrop Grumman B-2A, or so says this <a
href="http://www2.fbo.gov/spg/USAF/AFMC/AAC/FA9200%2D08%2DC%2D0120/SynopsisP.html">solicitation document</a> released earlier this week.</p><p>I find that very interesting on a number of levels, not least because the USAF has never before disclosed the existence of a weapon called the GBU-57!</p><p>(Designation-systems.net, in fact, lists weapons all the way up GBU-54, so that means a GBU-55 and GBU-56 could be somewhere in the classified inventory, too!)</p><p>But the existence of the GBU-57 gets even more interesting after a Google search. The only direct mention to the weapon <a
href="http://www.google.co.uk/url?sa=t&#038;ct=res&#038;cd=1&#038;url=http%3A%2F%2Fwww.ahmadinejad.ir%2F&#038;ei=iW3aR6PdOYeWwgHY6LCxCA&#038;usg=AFQjCNE786Y8cIGGYbOdzFvL1BiMbtHZWA&#038;sig2=-sGd6hEH_xuKIx4Vhwy-yQ">appeared in an article</a> in London’s Guardian newspaper in 2003, and then bizarrely as a passing reference. I would love to know how the Guardian’s reporter so casually came across that seemingly classified factoid for his article.</p><p><span
id="more-3897"></span></p><p>I would also love to know more about the GBU-57. The Guardian article describes the weapon as a 5,000lb-class penetrator. That puts it in the same class as the GBU-28/B. It likely shares the BLU-122 or improved BLU-113 warhead for 5,000lb-class penetrators. I wonder what makes the GBU-57 different in capability than the GBU-28?</p><p>I’m also interested in the timing of the USAF’s plan to integrate the weapon on the B-2. The GBU-57 would be the largest weapon ever integrated on the stealth bomber, and it’s capabilities seem ideal for a strike on heavily fortified, underground bunkers (<em>ahem, <a
href="http://www.google.co.uk/url?sa=t&#038;ct=res&#038;cd=1&#038;url=http%3A%2F%2Fwww.ahmadinejad.ir%2F&#038;ei=iW3aR6PdOYeWwgHY6LCxCA&#038;usg=AFQjCNE786Y8cIGGYbOdzFvL1BiMbtHZWA&#038;sig2=-sGd6hEH_xuKIx4Vhwy-yQ">Mahmoud Ahmadinejad</a>, Dick Cheney is on line 2.</em>)</p><p>The USAF hoped to integrate the even larger Massive Ordnance Penetrator (30,000lbs) on the B-2A, but last year Congress blocked the funding. There’s a chance the Guardian article was completely wrong, and the GBU-57 is in fact the new designation for the MOP. Even if that’s the case, I still wonder how the Guardian reporter came up with that designation in 2003, long before the MOP was conceived.</p><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline/">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/03/14/have-you-heard-of-this-bomb/feed/</wfw:commentRss> <slash:comments>24</slash:comments> </item> <item><title>More B-2 Crash Speculation</title><link>http://defensetech.org/2008/02/29/more-b-2-crash-speculation/</link> <comments>http://defensetech.org/2008/02/29/more-b-2-crash-speculation/#comments</comments> <pubDate>Fri, 29 Feb 2008 15:45:32 +0000</pubDate> <dc:creator>Ward</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=3866</guid> <description><![CDATA[You can look this one up. See FY 09 budget request, justification materials, US Air Force, Aircraft procurement-Vol. 2, page 71.
You’ll find on that page a detailed description for not one, but two potential mechanical problems that could cause a B-2A to crash.
Here’s a sampling (read highlighted text):The problem is caused by the B-2A’s distorted [...]]]></description> <content:encoded><![CDATA[<p>You can look this one up. See FY 09 budget request, justification materials, US Air Force, <a
href="http://www.saffm.hq.af.mil/shared/media/document/AFD-080204-083.pdf">Aircraft procurement-Vol. 2</a>, page 71.</p><p>You’ll find on that page a detailed description for not one, but two potential mechanical problems that could cause a B-2A to crash.</p><p>Here’s a sampling (read highlighted text):</p><p><img
alt="b2enginefanblade5.jpg" src="http://www.flightglobal.com/blogs/the-dewline/b2enginefanblade5.jpg" width="468" height="120" border="5"/></p><p>The problem is caused by the B-2A’s distorted engine inlets.</p><p>The distortion causes excessive wear on the stage 1 fan blades for the F118-GE-100 engines. Take that and an unplanned “foreign object damage event”, and, voila, your $1.1 billion bomber may experience a “catastrophic in-flight emergency”.</p><p>But there’s another problem. A loose fan blade also can spark an “uncontained titanium fire”. According to the same document, the titanium fire — whatever that is — may cause a “Class A event”, or what normal people call a “crash”.</p><p>The problem is listed in the budget justification documents because the USAF is buying repair blades this year to fix the problem. I’m sure it will be interesting for the investigators to find out whether the “Spirit of Kansas” had received the repairs before the crash, among other <a
href="http://www.flightglobal.com/blogs/the-dewline/2008/02/b2-crash-revives-memory-of-199.html">items of interest</a>, of course.</p><p>– <a
target="_blank" href="http://www.flightglobal.com/blogs/the-dewline/">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/02/29/more-b-2-crash-speculation/feed/</wfw:commentRss> <slash:comments>24</slash:comments> </item> <item><title>Second Guessing BAMS</title><link>http://defensetech.org/2008/02/08/second-guessing-bams/</link> <comments>http://defensetech.org/2008/02/08/second-guessing-bams/#comments</comments> <pubDate>Fri, 08 Feb 2008 13:00:14 +0000</pubDate> <dc:creator>paisley</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=3829</guid> <description><![CDATA[
I started covering the US Navy’s off-again/on-again Broad Area Maritime Surveillance (BAMS) program about five years ago. It’s been back on for two years and — last I checked — poised for a contract selection decision in five days.
This makes me sad because I just thought of an obvious angle for a BAMS story that [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="BAMS.jpg" src="http://www.defensetech.org/images/BAMS.jpg" width="298" height="391" hspace="10" vspace="5"/><br
/> I started covering the US Navy’s off-again/on-again Broad Area Maritime Surveillance (BAMS) program about five years ago. It’s been back on for two years and — last I checked — poised for a contract selection decision in five days.</p><p>This makes me sad because I just thought of an obvious angle for a BAMS story that I’ve missed somehow for the last five years.</p><p>If I had the chance to re-interview all of the competitors and USN program officials, here’s the first question I would ask: Why is this a winner take-all award instead of a split-buy?</p><p>The competitors for BAMs are the Northrop Grumman RQ-4N Global Hawk (high-altitude, turbofan, active electronically scanned arrays), Lockheed Martin/General Atomics Mariner (medium-altitude, turboprop, mechanically scanned arrays) and Boeing/Gulfstream G-550 (high-altitude, turbofan, optionally manned, multiple active arrays).</p><p>Each product is basically an off-the-shelf platform modified to meet the USN’s requirement. The USN is not paying to design a new aircraft. It’s essentially buying a la cart. That’s probably why each platform offers vastly different operational strengths and weaknesses.</p><p>This competition isn’t a choice between two discreetly differerent rivals, like the YF-22 versus the YF-23. This is more like the YF-22 versus the B-1. Each platform is a completely different capability, but both are useful for their intended purpose.</p><p>I agree there are downsides to a split buy award: the upfront costs are higher than a winner-takes-all award, you lose some of the marginal benefits of commonality and training gets more complicated.</p><p>But there are other advantages. The USN would not be beholden to one contractor for BAMS for the next two or three decades, but could keep playing the two teams off each other over the life of the program. Instead of a narrowly focused solution, the USN’s operators could employ the platform that makes the most sense for each mission.</p><p>Not to mention the fact that Congress tends to like split buys, as it spreads the jobs more broadly and subjects the defense industry to greater competition.</p><p>I’m not saying a split-buy is the best answer for BAMS, but rather that it’s an important and seemingly logical question that I should have asked long before now.</p><p>(Full disclosure: my wife works for Lockheed.)</p><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/02/08/second-guessing-bams/feed/</wfw:commentRss> <slash:comments>12</slash:comments> </item> <item><title>Going Foreign Again?</title><link>http://defensetech.org/2008/02/05/going-foreign-again/</link> <comments>http://defensetech.org/2008/02/05/going-foreign-again/#comments</comments> <pubDate>Tue, 05 Feb 2008 14:24:03 +0000</pubDate> <dc:creator>paisley</dc:creator> <category><![CDATA[Trimble on the Case]]></category><guid
isPermaLink="false">http://deftech.usmilblog.com/?p=3823</guid> <description><![CDATA[
It’s 2015. Both the long-lived Boeing C-17 and extremely long-lived Lockheed Martin C-130 production lines either have just shut down or are finally about to close.
Neither Boeing’s engineers in Long Beach nor Lockheed’s engineers in Marrietta have anything new in the pipeline. Sure, there’s some paper drawings of stealthy tactical airlifters getting some buzz, but [...]]]></description> <content:encoded><![CDATA[<p><img
align="left" alt="an-70.jpg" src="http://www.defensetech.org/images/an-70.jpg" width="286" height="191" hspace="10" vspace="5"/><br
/> It’s 2015. Both the long-lived Boeing C-17 and extremely long-lived Lockheed Martin C-130 production lines either have just shut down or are finally about to close.</p><p>Neither Boeing’s engineers in Long Beach nor Lockheed’s engineers in Marrietta have anything new in the pipeline. Sure, there’s some paper drawings of stealthy tactical airlifters getting some buzz, but nothing within at least five to 10 years of coming to flying fruition.</p><p>So, both manufacturers decide to do what all US defense companies do in this situation: they go foreign!</p><p>Lockheed locks arms with the company they spurned more than 15 years before on a potential joint tanker bid. So the Lockheed/Airbus axis offers the USAF the in-production A400M, which of course will be assembled in Mobile or Marrietta (or both) and fitted with a new 10,000shp-class General Electric turboprop or the Pratt &amp; Whitney PW800, which was actually the orignal A400M engine before “the Chirac affair”.</p><p>Boeing, which will never partner with the likes of Airbus, has to be more clever. They decide to link up with the manufacturer they briefly considered for a Joint Cargo Aircraft bid: Ukraine’s Antonov! The AN-70 is a rugged beast of an airframe, and Boeing’s engineers believe they can smooth out its aerodynamic and mechanical quirks. Boeing parks the new AN-70 assembly line somewhere in the US southeast, with Charleston (South Carolina), Jacksonville or San Antonio on the shortlist.</p><p>– <a
href="http://www.flightglobal.com/blogs/the-dewline">Steve Trimble</a></p> ]]></content:encoded> <wfw:commentRss>http://defensetech.org/2008/02/05/going-foreign-again/feed/</wfw:commentRss> <slash:comments>52</slash:comments> </item> </channel> </rss>
<!-- This site's performance optimized by W3 Total Cache. Dramatically improve the speed and reliability of your blog!

Learn more about our WordPress Plugins: http://www.w3-edge.com/wordpress-plugins/

Minified using apc
Page Caching using apc (user agent is rejected)
Database Caching 17/23 queries in 0.010 seconds using apc

Served from: unknown.dal.cologlobal.com @ 2010-03-13 11:47:22 -->