<?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"
	>
<channel>
	<title>Comments on: Boeing Update On 787</title>
	<atom:link href="http://www.fleetbuzzeditorial.com/2008/07/15/boeing-update-on-787/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fleetbuzzeditorial.com/2008/07/15/boeing-update-on-787/</link>
	<description></description>
	<pubDate>Wed, 19 Nov 2008 14:21:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: keesje</title>
		<link>http://www.fleetbuzzeditorial.com/2008/07/15/boeing-update-on-787/#comment-1330</link>
		<dc:creator>keesje</dc:creator>
		<pubDate>Sat, 19 Jul 2008 12:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.fleetbuzzeditorial.com/2008/07/15/boeing-update-on-787/#comment-1330</guid>
		<description>Reading between the lines we see that there are various issues that require a lot of attention. I'm afraid I smell further delay :-(

A small translation:
&lt;i&gt;
- The project is time challenged / risking further delays. We have little margin left at this moment
- We had to upgrade Line replaceable unit software
- Wiring issues are creating overweight
- We had anomalies with power on, some could not be rectified quickly 
- Still 4% of all hardware is not qualified for flight 
- 5% first flight hardware is not ready yet
- We have to do some more safety hardware tests
- Software has to be be rewritten for certification 
- We are redefining the 787-9, it will be 2 years later then planned. We have no firm configuration yet it will be  Q2, 2009 
- Airplane # 1 is good enough
- Mid-body section issues are not solved and demending unscheduled time
- We had quality problem on section 41 now solved. 
- Lack of engineering availability is affecting travelled work. Blame Global Aeronautica. 
Shipping date Airplane #4 uncertain yet.&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>Reading between the lines we see that there are various issues that require a lot of attention. I&#8217;m afraid I smell further delay <img src='http://www.fleetbuzzeditorial.com/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
<p>A small translation:<br />
<i><br />
- The project is time challenged / risking further delays. We have little margin left at this moment<br />
- We had to upgrade Line replaceable unit software<br />
- Wiring issues are creating overweight<br />
- We had anomalies with power on, some could not be rectified quickly<br />
- Still 4% of all hardware is not qualified for flight<br />
- 5% first flight hardware is not ready yet<br />
- We have to do some more safety hardware tests<br />
- Software has to be be rewritten for certification<br />
- We are redefining the 787-9, it will be 2 years later then planned. We have no firm configuration yet it will be  Q2, 2009<br />
- Airplane # 1 is good enough<br />
- Mid-body section issues are not solved and demending unscheduled time<br />
- We had quality problem on section 41 now solved.<br />
- Lack of engineering availability is affecting travelled work. Blame Global Aeronautica.<br />
Shipping date Airplane #4 uncertain yet.</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boeing investor</title>
		<link>http://www.fleetbuzzeditorial.com/2008/07/15/boeing-update-on-787/#comment-1298</link>
		<dc:creator>boeing investor</dc:creator>
		<pubDate>Wed, 16 Jul 2008 04:30:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.fleetbuzzeditorial.com/2008/07/15/boeing-update-on-787/#comment-1298</guid>
		<description>I wonder which publication starts off the scare stories about the brakes on the 787 ;-)</description>
		<content:encoded><![CDATA[<p>I wonder which publication starts off the scare stories about the brakes on the 787 <img src='http://www.fleetbuzzeditorial.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
