Up to 700 engineers at Boeing losing jobs
Boeing says it will lay off as many as 700 engineers this year, with the first notices going out Friday, as it cuts overall engineering employment by up to 1,700 positions.
Seattle Times aerospace reporter
Boeing has begun to ax engineering jobs at its local commercial-airplanes unit as its latest jet programs shift from development to production, and will lay off as many as 700 manufacturing engineers this year.
Managers learned Thursday that Boeing aims to reduce the engineering staff by up to 1,700 positions by the end of the year through attrition and layoffs.
Layoff notices to the first 100 of those employees are going out Friday.
An internal “talking points” memo for managers states that further layoffs in other areas of engineering are possible and that it will be “18 or more months” before hiring of engineers resumes.
In an email, Mike Delaney, vice president of engineering, said the reduction is needed because development work is complete on the 747-8, the 787-9 and the KC-45 Air Force tanker.
Downsizing as new jet programs transition to more routine production has been a cyclical pattern at Boeing over the decades.
Delaney’s email cited another factor, too: The layoffs might have been avoided, he said, if Boeing had launched its 787-10 and 777X programs.
At one time, both programs were expected to launch last year. It’s now widely anticipated that both will launch later this year.
“I realize this news may be surprising,” Delaney wrote. “Commercial Airplanes has been on an upswing for several years. We continue to ramp up production on our major programs, and the prospect for future development work is very positive.”
Boeing clearly still needs many engineers on the 737 MAX jet-development program, but “overall, we must reduce our Engineering employment level by 1,500 to 1,700 positions during 2013,” Delaney wrote.
He said Boeing has “significantly scaled back external hiring” in the past year and since last October has let go almost 700 contract employees.
“We hope to mitigate the number of layoffs through the reductions we are making in contract labor, by natural attrition and by not filling many open positions,” Delaney wrote. “Unfortunately and unavoidably we must take additional actions.”
The bottom line is that “through the rest of 2013 we will issue 60-day layoff notices to as many as 700 employees.”
He said the first layoff notices will go out Friday to 100 manufacturing engineers (MEs).
Last week, a manager on the 787 program sent an email to the manufacturing engineers warning them of an imminent downsizing.
The internal “talking points” memo states the 700 announced layoffs focus on MEs in the Puget Sound region and that “future layoffs could impact other parts of ... Engineering.”
The memo also says engineering staffing at Boeing South Carolina “does not require reductions.”
Ray Goforth, executive director of Boeing’s white-collar union, the Society of Professional Engineering Employees in Aerospace (SPEEA), said he’s concerned Boeing is cutting employees at the same time as it is sending engineering work offshore.
“I’m disappointed that work is being outsourced to the Moscow Design Center while people here are being laid off,” said Goforth.
Rich Plunkett, SPEEA’s director of strategic development, said a manufacturing engineer (ME) who does “installation planning” on the 787 program — working out the sequence of production and the order in which parts are installed during jet assembly — reported he’s been told “throw all the installation planning you can direct to Moscow.”
According to Plunkett, the ME planner said his function “will revert to simply managing the work of the Design Center in Moscow.”
In response, Boeing spokesman Doug Alder said, “The Moscow Design Center has also come down from its peak employment numbers, just like other areas of the company.”
Delaney’s message underlines the importance of Boeing’s 787-10 and 777X programs, while at the same time suggesting that delays in deciding to move forward with those programs have been very consequential.
“Potential development programs for the 787-10X and 777X, which might have provided opportunities to avoid these layoffs, have not been formally approved and launched,” he wrote.
Early in 2012, then-CEO of Boeing Commercial Airplanes Jim Albaugh spoke publicly of putting a 777X proposal to the company’s board in Chicago by the end of that year, with a go-ahead on the 787-10 perhaps coming even before that.
But by last fall, after Albaugh abruptly resigned in June, that talk faded. Boeing’s board has not announced a decision on either program.
“The challenge we are facing is that those yet-to-be-launched programs are too far out for us to maintain present levels of employment,” Delaney said.
The internal “talking points” memo pins down the gap in engineering requirements.
“This creates a lengthy time period (18 or more months) before workforce needs for those programs would begin rising to current levels,” the memo states.
And yet, the aviation industry certainly considers both programs still on the near-term horizon.
The Boeing board is expected to meet this month to approve offering the 777X. That is one step before a formal launch, which would typically follow within months.
Likewise, the 787-10X is also expected to launch this year.
Launch of either or both programs normally would trigger an uptick in engineering needs.
Boeing’s Alder said the layoffs do not indicate any further delay to 777X or 787-10.
“Our timing for both remains the same,” Alder said. “There is no impact to study and development on either.”
Delaney’s email to his managers expressed regret at the need for layoffs.
“This has been a difficult decision,” Delaney wrote. “We know layoffs impact individuals and families.”
Last month, Boeing announced layoffs of 800 machinists working on the 787 and 747-8 programs.
Boeing also is considering the move of some airline customer engineering support to Long Beach, Calif., and will move significant IT support work to St. Louis and North Charleston, S.C.
Dominic Gates: (206) 464-2963 or firstname.lastname@example.org