<?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: Read the fine print: JetBlue revises its contract, defines &#8220;controllable irregularity&#8221;</title>
	<atom:link href="http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/</link>
	<description>Living the first class life -- at coach prices</description>
	<lastBuildDate>Fri, 06 Nov 2009 22:15:02 -0700</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: United&#8217;s half-assed policy changes: Not quite a bill of rights, and not quite an upgrade policy fix &#187; Upgrade: Travel Better</title>
		<link>http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/#comment-14903</link>
		<dc:creator>United&#8217;s half-assed policy changes: Not quite a bill of rights, and not quite an upgrade policy fix &#187; Upgrade: Travel Better</dc:creator>
		<pubDate>Fri, 01 Jun 2007 16:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/#comment-14903</guid>
		<description>[...] jetBlue&#8217;s policy revision had its problems, and didn&#8217;t go far enough in my opinion, it&#8217;s miles ahead of United&#8217;s policy, [...]</description>
		<content:encoded><![CDATA[<p>[...] jetBlue&#8217;s policy revision had its problems, and didn&#8217;t go far enough in my opinion, it&#8217;s miles ahead of United&#8217;s policy, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cranky</title>
		<link>http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/#comment-7719</link>
		<dc:creator>Cranky</dc:creator>
		<pubDate>Wed, 07 Mar 2007 21:33:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/#comment-7719</guid>
		<description>I think you can move back from being underwhelmed to just being, uh, whelmed.  If you look at all the sections on ground delays, they apply regardless of cause.  So all those people stuck on taxiways would be compensated.</description>
		<content:encoded><![CDATA[<p>I think you can move back from being underwhelmed to just being, uh, whelmed.  If you look at all the sections on ground delays, they apply regardless of cause.  So all those people stuck on taxiways would be compensated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Hass</title>
		<link>http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/#comment-7700</link>
		<dc:creator>Joe Hass</dc:creator>
		<pubDate>Wed, 07 Mar 2007 18:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.upgradetravelbetter.com/2007/03/07/read-the-fine-print-jetblue-revises-its-contract-defines-controllable-irregularity/#comment-7700</guid>
		<description>My follow up: What would the ruling be if the original problem was not a Force Majeure event, but a subsequent problem was? Take UA907 (http://blogs.usatoday.com/sky/2007/03/flight_907.html). The original problem was a plane change. But the time it took for the plane change caused the flight to be delayed by weather, which led to the nine-hour delay. So would this be considered conrollable (since the original delay was caused by UA) or uncontrollable (since the major portion of the delay was caused by the weather)?</description>
		<content:encoded><![CDATA[<p>My follow up: What would the ruling be if the original problem was not a Force Majeure event, but a subsequent problem was? Take UA907 (<a href="http://blogs.usatoday.com/sky/2007/03/flight_907.html)" rel="nofollow" target="_blank" class="liexternal">http://blogs.usatoday.com/sky/2007/03/flight_907.html)</a>. The original problem was a plane change. But the time it took for the plane change caused the flight to be delayed by weather, which led to the nine-hour delay. So would this be considered conrollable (since the original delay was caused by UA) or uncontrollable (since the major portion of the delay was caused by the weather)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
