Steve Creedy of The Australian posted an item on the impact of the IAM strike on 787 deliveries for QANTAS. This is the closest Boeing has come to acknowledging an impact on the 25 deliveries set for 2009. The article says QANTAS (Jetstar) was to get its first 787-8 (ZA021) in November 2009."I can just say that when the team went out on strike all production stopped," Boeing Commercial Airplanes marketing vice-president Randy Tinseth said. "None of us know when the strike will be over. When it is over we can give you a new schedule."QANTAS also indicated that it was still interested in the 787-10 and A350 XWB.Incoming Qantas chief executive Alan Joyce said last week Boeing was still telling the airline its 787s would be delivered in November next year but an update was due this week.
Before the strike, Qantas was facing further delays of up to three months after completion of the first aircraft slipped by eight weeks.
Speaking at the airline's A380 delivery event in Toulouse on 19 September, Qantas chief executive Geoff Dixon and his successor designate Alan Joyce revealed that the airline was in "the early stage of talks" with Boeing on the 787-10 as well as with Airbus about the A350 XWB.
The 787-10 is a proposed stretched version of the -9, seating around 300 passengers, making it similar in size to the -200 variants of the 777. Joyce, who was named as Dixon's successor in July, considers the 787-10 to be "a requirement", but acknowledges that Boeing is "not there yet".
Last week JAL finalized its 787 compensation deal with Boeing for 767 and 777 and clarified its delivery time frame for its first 787 (ZA020), which was set for October.
Two weeks ago, Boeing chief financial officer James Bell told investors to expect at
least a month's delay:
"Right now it's a one-for-one day slip on the 787 and all other programmes as well."
Back in the factory, it appears as though Boeing has been able to delivery many of those idling 737s at Boeing Field. Inside 40-26, the Dreamliner One's engines have been removed again and there's no explanation currently as to why this happened. Also, the start of static testing is on hold due to data acquisition issues. Can anyone shed some light on this?
Recent Comments