<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Ships Of The Future &#8211; LCS, Littoral Combat Ship</title>
	<atom:link href="http://gcaptain.com/maritime/blog/ships-of-the-future-lcs-littoral-combat-ship/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcaptain.com/maritime/blog/ships-of-the-future-lcs-littoral-combat-ship/</link>
	<description>A Blog About Ships</description>
	<lastBuildDate>Tue, 16 Mar 2010 19:23:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jerry P.</title>
		<link>http://gcaptain.com/maritime/blog/ships-of-the-future-lcs-littoral-combat-ship/comment-page-1/#comment-14133</link>
		<dc:creator>Jerry P.</dc:creator>
		<pubDate>Mon, 22 Sep 2008 21:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/ships-of-the-future-lcs-littoral-combat-ship/#comment-14133</guid>
		<description>John you havent see ours yet.  That is LCS-2 It carries more twice the payload and dwarfs the competition in size. LCS-1 is not capable of 45 kts with a mission package onboard. Infact I hear it barley made 40kts during a full power run. Not bad for being two years behind schedule and over budget by a few hundred million.</description>
		<content:encoded><![CDATA[<p>John you havent see ours yet.  That is LCS-2 It carries more twice the payload and dwarfs the competition in size. LCS-1 is not capable of 45 kts with a mission package onboard. Infact I hear it barley made 40kts during a full power run. Not bad for being two years behind schedule and over budget by a few hundred million.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
