By Scott Hamilton Commentary Oct. 1, 2020, © Leeham News: Nobody, but nobody, should be surprised that Boeing is going to consolidate 787 production in Charleston (SC). This die was cast Oct. 28, 2009, when Boeing announced that the… Read More
DownloadOct. 1, 2020, (c) Leeham News: This is the fourth in a series of Retrospectives about Boeing’s decision to locate the second 787 Final Assembly Line in Charleston (SC).
DownloadRetrospective-2, Oct. 1, 2020, (c) Leeham News. This is the second in a series of Retrospective looks at the 2009 decision by Boeing to locate 787 Line 2 in Charleston (SC).
Dashing off a quick note here, since we’re still on hiatus. IAM 751 successfully achieved a complaint and hearing from the National Labor Relations Board filed a year ago against Boeing, alleging that the October 2009 decision to… Read More
A publication obtained an 18-page summary of the incentives obtained by Boeing for its 787 Line 2 in Charleston (SC). The news report may be accessed here.
Boeing told Washington State that incentives had nothing to do with its decision to locate 787 Line 2 in Charleston (SC)–that it was all about the unions. This article in the Charleston Post and Courier reveals that incentives… Read More
The Background It had been a long time coming. Boeing’s 787 repeated delays and great backlog meant that the company had to have a second production line to catch up and to offer delivery positions within reasonable time… Read More
This 5-page story (when printed out) picked up by several SC newspapers tells how Boeing selected Charleston for Line 2 and it paints a very different picture than the one in the previous post of the Everett Herald… Read More
Update: Boeing spokesman Tim Healy provided this response to us when we asked about the article: “We were utterly serious about reaching an agreement. And we told the IAM quite precisely what we needed from them and when.”… Read More
The spin wars continue. Earlier today Boeing issued a message to employees explaining, from its perspective, why a deal with the IAM could not be reached. A few hours later, the IAM 751 responded. We have both after… Read More