<?xml version="1.0" encoding="iso-8859-1" ?> 
<rss version="2.0">
	<channel>
		<title>Ionosphere Media</title> 
		<description>Articles from Ionosphere Media</description> 
		<link>http://www.ionospheremedia.com</link> 
		<lastBuildDate>Tue, 16 Jun 2009 10:33:32 -0400</lastBuildDate>
		<generator>Network Strategics</generator> 
		<image>
		  <url>http://www.ionospheremedia.com</url> 
		  <title>Syndicated articles from Ionosphere Media</title> 
		  <link>http://www.ionospheremedia.com</link> 
		  <description>Articles from Ionosphere Media</description> 
		</image>
		<item>
		  <title>This is text number 2 for gus</title> 
		  <link>http://www.ionospheremedia.com/this-is-text-number-2-for-gus-article-2.html</link> 
		  <description>Months ago, I received a letter from a Sunwing Airlines customer who shared her frightening experience in which she witnessed a flight attendant creating sparks inflight by manipulating an emergency light in an effort to entertain her fellow crew members with a high-flying pyrotechnics display. The passenger wrote a letter to Sunwing describing this and the overall shocking behavior of this company representative.
Here is the response this customer received months after the incident:</description> 
		  <category></category> 
		</item>
		<item>
		  <title>Sunwing customer shocked by inflight spark response</title> 
		  <link>http://www.ionospheremedia.com/sunwing-customer-shocked-by-inflight-spark-response-article-1.html</link> 
		  <description>Months ago, I received a letter from a Sunwing Airlines customer who shared her frightening experience in which she witnessed a flight attendant creating sparks inflight by manipulating an emergency light in an effort to entertain her fellow crew members with a high-flying pyrotechnics display. The passenger wrote a letter to Sunwing describing this and the overall shocking behavior of this company representative.
Here is the response this customer received months after the incident:</description> 
		  <category></category> 
		</item>
	</channel>
</rss>
