<?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 for Corporate Aviation Blog</title>
	<atom:link href="http://gofir.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://gofir.com/blog</link>
	<description>GOFIR.com</description>
	<lastBuildDate>Fri, 08 Apr 2011 16:47:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Southwest Airlines Accident by admin</title>
		<link>http://gofir.com/blog/southwest-airlines-accident/#comment-119</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 08 Apr 2011 16:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://gofir.com/blog/?p=136#comment-119</guid>
		<description>Southwest Airlines canceled hundreds of flights over the 2-3 April weekend after subsequent inspections revealed structural problems in its fleet of Boeing 737 aircraft. Cracks have been discovered in at least three separate aircraft as of 4 April, and approximately 80 of the company’s 737 aircraft have been grounded.</description>
		<content:encoded><![CDATA[<p>Southwest Airlines canceled hundreds of flights over the 2-3 April weekend after subsequent inspections revealed structural problems in its fleet of Boeing 737 aircraft. Cracks have been discovered in at least three separate aircraft as of 4 April, and approximately 80 of the company’s 737 aircraft have been grounded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gulfstream G650 Accident &#8211; update by admin</title>
		<link>http://gofir.com/blog/gulfstream-g650-accident-update/#comment-118</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 08 Apr 2011 16:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://gofir.com/blog/?p=131#comment-118</guid>
		<description>In a statement issued this morning, Gulfstream pledged its cooperation with the NTSB. “We are participating fully in the aircraft investigation, and will resume flying the G650 only when we and the [FAA] are satisfied it is safe to do so,” said Pres Henne, Gulfstream’s senior vice president for programs, engineering and test. The aircraft manufacturer noted that all other certification and production work on the program would continue.</description>
		<content:encoded><![CDATA[<p>In a statement issued this morning, Gulfstream pledged its cooperation with the NTSB. “We are participating fully in the aircraft investigation, and will resume flying the G650 only when we and the [FAA] are satisfied it is safe to do so,” said Pres Henne, Gulfstream’s senior vice president for programs, engineering and test. The aircraft manufacturer noted that all other certification and production work on the program would continue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Strategic Lateral Offset Procedure (SLOP) by bobsell</title>
		<link>http://gofir.com/blog/slop/#comment-34</link>
		<dc:creator>bobsell</dc:creator>
		<pubDate>Mon, 17 Jan 2011 10:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://gofir.com/blog/?p=65#comment-34</guid>
		<description>I like the idea of using SLOP to add separation between aircraft. However, I think it should be at pilot’s discretion verses employing the procedure every time without any thought into the process. Making your decision to offset 1 or 2 miles should be done on a case by case basis and not automatically. Take in to consideration traffic in the area and weather before deciding. 

You need to address SLOP in your aviation operations manual so your pilots know that management supports it and that it’s okay to use it. Adding SLOP procedures to your operations manual is a must. However, don’t tie the hands of the Captain by writing policies that dictate WHAT the Captain WILL do.  The Captain needs to be free to use good judgment.</description>
		<content:encoded><![CDATA[<p>I like the idea of using SLOP to add separation between aircraft. However, I think it should be at pilot’s discretion verses employing the procedure every time without any thought into the process. Making your decision to offset 1 or 2 miles should be done on a case by case basis and not automatically. Take in to consideration traffic in the area and weather before deciding. </p>
<p>You need to address SLOP in your aviation operations manual so your pilots know that management supports it and that it’s okay to use it. Adding SLOP procedures to your operations manual is a must. However, don’t tie the hands of the Captain by writing policies that dictate WHAT the Captain WILL do.  The Captain needs to be free to use good judgment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on GIV Landing Overrun at TEB by gmail</title>
		<link>http://gofir.com/blog/giv-landing-overrun-at-teb/#comment-32</link>
		<dc:creator>gmail</dc:creator>
		<pubDate>Fri, 10 Dec 2010 23:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://gofir.com/blog/?p=39#comment-32</guid>
		<description>Anyone have any updates on this?</description>
		<content:encoded><![CDATA[<p>Anyone have any updates on this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Brazil Handling by Bob Sell</title>
		<link>http://gofir.com/blog/brazil-handling/#comment-31</link>
		<dc:creator>Bob Sell</dc:creator>
		<pubDate>Fri, 10 Dec 2010 23:28:19 +0000</pubDate>
		<guid isPermaLink="false">http://gofir.com/blog/?p=63#comment-31</guid>
		<description>You never know about Customs or Handling. Seems like every time you go back, it&#039;s a different deal. It would be nice if places like this would stick to some sort of custom (pardon the pun). You can deal with the quirks if you just know about them.</description>
		<content:encoded><![CDATA[<p>You never know about Customs or Handling. Seems like every time you go back, it&#8217;s a different deal. It would be nice if places like this would stick to some sort of custom (pardon the pun). You can deal with the quirks if you just know about them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
