<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The Osprey Jink</title>
	<atom:link href="http://defensetech.org/2009/07/20/the-osprey-jink/feed/" rel="self" type="application/rss+xml" />
	<link>http://defensetech.org/2009/07/20/the-osprey-jink/</link>
	<description>The Future of the Military, Law Enforcement and National Security</description>
	<lastBuildDate>Sat, 26 May 2012 04:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: George</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91212</link>
		<dc:creator>George</dc:creator>
		<pubDate>Fri, 31 Jul 2009 23:33:32 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91212</guid>
		<description>Just today I read that representatives from the Man-Bunny Matrix witnessed extensive V-22 testing in Utah.
http://manbunnymatrix.net/
</description>
		<content:encoded><![CDATA[<p>Just today I read that representatives from the Man-Bunny Matrix witnessed extensive V-22 testing in Utah.<br />
<a href="http://manbunnymatrix.net/" rel="nofollow">http://manbunnymatrix.net/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SMSgt Mac</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91211</link>
		<dc:creator>SMSgt Mac</dc:creator>
		<pubDate>Wed, 22 Jul 2009 00:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91211</guid>
		<description>And for the record, almost anyone who&#039;s piloted a plane with an FE requirement will probably tell you the FEs know more about their planes&#039; systems and performance than the pilots.
There I was....
We were flying cross-country, coming back from a deployment in a C-130. I was sitting on th eCrew Chief rack behind the operators on headsets watching the world go by. The Pilot was reading the AF Times, and the Co-pilot was reading Fortune. The FE kicked the pilot seats when we got a radio call, calling out traffic &#039;no factor&#039; as fast as ATC was alerting us, and managing the fuel transfer systems and monitoring instruments all the while. After a while, the Pilot comes over the Intercom: Man! They&#039;re talking about cutting pilot bonuses again! I&#039;ll never forget the &#039;WTF?&#039; look on the FE&#039;s face when he turned around and looked at me.
P.S. Anyone who&#039;s the least bit familiar with the FE job on the Pave Lows can tell you that it was the highest workload flying, in the most hostile &#039;office&#039; in the sky. So intense, the Pave Lows routnely flew with two FEs that would rotate in and out of the center seat.
</description>
		<content:encoded><![CDATA[<p>And for the record, almost anyone who’s piloted a plane with an FE requirement will probably tell you the FEs know more about their planes’ systems and performance than the pilots.<br />
There I was.…<br />
We were flying cross-country, coming back from a deployment in a C-130. I was sitting on th eCrew Chief rack behind the operators on headsets watching the world go by. The Pilot was reading the AF Times, and the Co-pilot was reading Fortune. The FE kicked the pilot seats when we got a radio call, calling out traffic ‘no factor’ as fast as ATC was alerting us, and managing the fuel transfer systems and monitoring instruments all the while. After a while, the Pilot comes over the Intercom: Man! They’re talking about cutting pilot bonuses again! I’ll never forget the ‘WTF?’ look on the FE’s face when he turned around and looked at me.<br />
P.S. Anyone who’s the least bit familiar with the FE job on the Pave Lows can tell you that it was the highest workload flying, in the most hostile ‘office’ in the sky. So intense, the Pave Lows routnely flew with two FEs that would rotate in and out of the center seat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91210</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 21 Jul 2009 23:02:06 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91210</guid>
		<description>FTR...I am a Flight Engineer.
</description>
		<content:encoded><![CDATA[<p>FTR…I am a Flight Engineer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stinger</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91208</link>
		<dc:creator>stinger</dc:creator>
		<pubDate>Tue, 21 Jul 2009 11:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91208</guid>
		<description>It&#039;s MANPADS, never MANPAD. MANPADS = man-portable air defense system. MANPADS is not plural for MANPAD; Rather MANPADS is the proper acronym.
</description>
		<content:encoded><![CDATA[<p>It’s MANPADS, never MANPAD. MANPADS = man-portable air defense system. MANPADS is not plural for MANPAD; Rather MANPADS is the proper acronym.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SMSgt Mac</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91207</link>
		<dc:creator>SMSgt Mac</dc:creator>
		<pubDate>Tue, 21 Jul 2009 05:36:14 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91207</guid>
		<description>If all the people now chafing in their bunched panties over the &#039;complexity&#039; and challenges in fielding and operating a completely new kind of weapon system had been in charge during  prehistoric times, we would still be sitting in our caves ostracizing anyone and everyone who  came up with a new way to make fire.
&#039;First&#039; aircraft in any category always break new ground, and always have at least one or two  growing pains - as anyone with any real experinece will tell you. Get a sense of history, people, and get some appreciation of what the V-22 folks are working through (and under a microscope no less).
&#039;Painless progress&#039; is an oxymoron in the real world.
</description>
		<content:encoded><![CDATA[<p>If all the people now chafing in their bunched panties over the ‘complexity’ and challenges in fielding and operating a completely new kind of weapon system had been in charge during  prehistoric times, we would still be sitting in our caves ostracizing anyone and everyone who  came up with a new way to make fire.<br />
’First’ aircraft in any category always break new ground, and always have at least one or two  growing pains — as anyone with any real experinece will tell you. Get a sense of history, people, and get some appreciation of what the V-22 folks are working through (and under a microscope no less).<br />
’Painless progress’ is an oxymoron in the real world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91206</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Tue, 21 Jul 2009 01:08:27 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91206</guid>
		<description>I get really tired of seeing programs take ten years to come to fruition, just to find they did not get it right and they have to &quot;re-engineer&quot; everything.....
I am a fan of the Osprey, in the way the Marines are. I love what it can do, but hate the complexity.....
The next generation may be much simpler. By using electric motors to spin the props and keeping the power plants and battery backup in the body will significantly reduce complexity and greatly increase reliability.
With such reduced complexity, four props will be possible. Allowing for landing with only three operational.....
DARPA is also funding a &quot;rotodyne&quot; configuration. One prop to get airborne, non-moving engines to go forward.
I just hope they do not ignore better designs due to political considerations and money already spent.
But they probably will....
</description>
		<content:encoded><![CDATA[<p>I get really tired of seeing programs take ten years to come to fruition, just to find they did not get it right and they have to “re-engineer” everything.….<br />
I am a fan of the Osprey, in the way the Marines are. I love what it can do, but hate the complexity.….<br />
The next generation may be much simpler. By using electric motors to spin the props and keeping the power plants and battery backup in the body will significantly reduce complexity and greatly increase reliability.<br />
With such reduced complexity, four props will be possible. Allowing for landing with only three operational.….<br />
DARPA is also funding a “rotodyne” configuration. One prop to get airborne, non-moving engines to go forward.<br />
I just hope they do not ignore better designs due to political considerations and money already spent.<br />
But they probably will.…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. Foskey</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91205</link>
		<dc:creator>C. Foskey</dc:creator>
		<pubDate>Mon, 20 Jul 2009 21:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91205</guid>
		<description>I&#039;m sorry, but from an engineering perspective the fact that there have been &quot;parts breaking that are not supposed to break&quot; is most certainly an issue with the aircraft...lest we forget than any aircraft is merely a complicated system of &quot;parts&quot;.
</description>
		<content:encoded><![CDATA[<p>I’m sorry, but from an engineering perspective the fact that there have been “parts breaking that are not supposed to break” is most certainly an issue with the aircraft…lest we forget than any aircraft is merely a complicated system of “parts”.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sgt Oblat</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91204</link>
		<dc:creator>Sgt Oblat</dc:creator>
		<pubDate>Mon, 20 Jul 2009 20:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91204</guid>
		<description>Of course all the bravado will evaporate as soon as the pilots start getting shot down in combat. Then they will be squealing for a fix and claim to be betrayed.
But perhaps th war will be over before the Osprey gets deployed on anything real. The Marines are making sure that the program is fully front loaded by delivering them all before risking one in combat.
You gotta love being a contractor with clients like these.
</description>
		<content:encoded><![CDATA[<p>Of course all the bravado will evaporate as soon as the pilots start getting shot down in combat. Then they will be squealing for a fix and claim to be betrayed.<br />
But perhaps th war will be over before the Osprey gets deployed on anything real. The Marines are making sure that the program is fully front loaded by delivering them all before risking one in combat.<br />
You gotta love being a contractor with clients like these.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91203</link>
		<dc:creator>James</dc:creator>
		<pubDate>Mon, 20 Jul 2009 18:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91203</guid>
		<description>I hate to say it but this continuing Osprey saga reminds me of the M-14 vs. M-16 soap opera, 40 plus years and counting...
</description>
		<content:encoded><![CDATA[<p>I hate to say it but this continuing Osprey saga reminds me of the M-14 vs. M-16 soap opera, 40 plus years and counting…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://defensetech.org/2009/07/20/the-osprey-jink/#comment-91202</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Mon, 20 Jul 2009 18:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://deftech.usmilblog.com/2009/07/20/the-osprey-jink/#comment-91202</guid>
		<description>I&#039;m one of those engineers (on the govt. side) that, as &quot;Jim&quot; said, is working day in and day out to improve all the reliability issues. He certainly made accurate statements on that front, and it&#039;s true that from a reliability standpoint, the aircraft still has a ways to go, but I&#039;ve got chart after chart showing the before and after for various improvements and the attending improvement in mean flight hour between failures. And I only work on two of the systems of the aircraft (one of which was one of the top degraders of the aircraft, and despite the fact that it worked just fine, crews never turned it on because they felt that as soon as they did, it would break).
The trick is that most of these fixes are small, incremental, and will take time to prove out. They (the contractor) fix one piece here, one piece there. Each one gives a small improvement, and on the whole the situation improves. It takes more time than one would think to implement these changes, and sometimes, when you fix one part, you end up finding the &quot;next worst&quot; item, and you have to fix that as well. It&#039;s really not as straightforward as everyone would love it to be, and there&#039;s no silver bullet answer. Not like fixing a tire on your car. And even if it were, how would you prove that your new tire lasted longer than the last one? You have to drive on it for a while.
There&#039;s no question that over the years that I have been here doing this job, the situation has improved (both in my area and others that I have heard about around here), and it will continue to do so. Like &quot;Jim&quot; says, the system works, and we are working every day to make sure that it works all the time.
</description>
		<content:encoded><![CDATA[<p>I’m one of those engineers (on the govt. side) that, as “Jim” said, is working day in and day out to improve all the reliability issues. He certainly made accurate statements on that front, and it’s true that from a reliability standpoint, the aircraft still has a ways to go, but I’ve got chart after chart showing the before and after for various improvements and the attending improvement in mean flight hour between failures. And I only work on two of the systems of the aircraft (one of which was one of the top degraders of the aircraft, and despite the fact that it worked just fine, crews never turned it on because they felt that as soon as they did, it would break).<br />
The trick is that most of these fixes are small, incremental, and will take time to prove out. They (the contractor) fix one piece here, one piece there. Each one gives a small improvement, and on the whole the situation improves. It takes more time than one would think to implement these changes, and sometimes, when you fix one part, you end up finding the “next worst” item, and you have to fix that as well. It’s really not as straightforward as everyone would love it to be, and there’s no silver bullet answer. Not like fixing a tire on your car. And even if it were, how would you prove that your new tire lasted longer than the last one? You have to drive on it for a while.<br />
There’s no question that over the years that I have been here doing this job, the situation has improved (both in my area and others that I have heard about around here), and it will continue to do so. Like “Jim” says, the system works, and we are working every day to make sure that it works all the time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

