I just noticed this thread. I didn't know it was out there. My first gig out of college was at Boeing's Flight Systems Lab which did all the testing on all the electronics going into new commercial aircraft. they also had flight deck simulators for each Boeing airliner.
I started just after the 747-400 rolled out and left just as the 777 was in flight test. Back then the company was a huge bureaucracy and there was a lot of waste, but the company was run by engineers and working out all the bugs before delivering the plane was the #1 priority on the engineering side. The testing regime was incredibly thorough and even minor glitches would be a big deal.
I had been there a year or two when a bug was found in the 747-400 navigation computer. SAS airlines started offering a certificate to passengers who flew from the US to Europe over the north pole. The first time they tried it in a 747-400, the plane did an 'S' around the pole because the navigation computer couldn't handle 0/0, but it safely compensated.
That got the entire 747-400 fleet grounded and was a level 1 excrement storm from management and the FAA. I went to Everett while the planes were grounded and Boeing couldn't even fly them to a holding airport. Paine Field was cheek to jowl in 747s. It was pretty impressive but also meant a lot of money tied up in inventory that wasn't going anywhere.
Boeing made a big deal of taking care of pilots. When the 777 became the first fly by wire plane in Boeing's fleet, a lot of effort went into making the controls behave like controls connected mechanically to the control surfaces. It was a quite involved system that cost a lot to develop. Airbus gave much less feedback and it contributed to the loss of the Air France Airbus over the Atlantic about 10 years ago.
My job was working on the simulator hardware and test instruments for the aircraft buses. Boeing took aircraft out of service seriously. One time a 747 was down for an unknown reason in Korea and I needed to add a feature to a test instrument going with the team heading out there to troubleshoot the problem. My manager told me in no uncertain terms that I couldn't go home until the feature was ready. Fortunately it was a quick fix and I was only about an hour late getting out of there, but that's how seriously they took fixing problems.
I don't have any contacts left in Boeing, but from what I can tell from the outside, the company has changed. The bean counters are running the show and cutting corners to try and make a quick buck. Just like the corner cutting that led to the Deepwater Horizon accident, things came back to bite them. I wonder how many other problems are lurking in recent Boeing designs that haven't surfaced yet?
I started just after the 747-400 rolled out and left just as the 777 was in flight test. Back then the company was a huge bureaucracy and there was a lot of waste, but the company was run by engineers and working out all the bugs before delivering the plane was the #1 priority on the engineering side. The testing regime was incredibly thorough and even minor glitches would be a big deal.
I had been there a year or two when a bug was found in the 747-400 navigation computer. SAS airlines started offering a certificate to passengers who flew from the US to Europe over the north pole. The first time they tried it in a 747-400, the plane did an 'S' around the pole because the navigation computer couldn't handle 0/0, but it safely compensated.
That got the entire 747-400 fleet grounded and was a level 1 excrement storm from management and the FAA. I went to Everett while the planes were grounded and Boeing couldn't even fly them to a holding airport. Paine Field was cheek to jowl in 747s. It was pretty impressive but also meant a lot of money tied up in inventory that wasn't going anywhere.
Boeing made a big deal of taking care of pilots. When the 777 became the first fly by wire plane in Boeing's fleet, a lot of effort went into making the controls behave like controls connected mechanically to the control surfaces. It was a quite involved system that cost a lot to develop. Airbus gave much less feedback and it contributed to the loss of the Air France Airbus over the Atlantic about 10 years ago.
My job was working on the simulator hardware and test instruments for the aircraft buses. Boeing took aircraft out of service seriously. One time a 747 was down for an unknown reason in Korea and I needed to add a feature to a test instrument going with the team heading out there to troubleshoot the problem. My manager told me in no uncertain terms that I couldn't go home until the feature was ready. Fortunately it was a quick fix and I was only about an hour late getting out of there, but that's how seriously they took fixing problems.
I don't have any contacts left in Boeing, but from what I can tell from the outside, the company has changed. The bean counters are running the show and cutting corners to try and make a quick buck. Just like the corner cutting that led to the Deepwater Horizon accident, things came back to bite them. I wonder how many other problems are lurking in recent Boeing designs that haven't surfaced yet?