"....unapproved sensors on almost 800 737s"
"....unapproved sensors on almost 800 737s"
"FAA fines Boeing for unapproved sensors on almost 800 737s"
OK, what's the truth here? Is there a real safety problem with the sensors, or is it just a question of incorrect documentation that is perhaps old news anyway?
My money's on the latter, but I'm curious to see if that's right.
OK, what's the truth here? Is there a real safety problem with the sensors, or is it just a question of incorrect documentation that is perhaps old news anyway?
My money's on the latter, but I'm curious to see if that's right.
Join Date: Dec 2006
Location: Florida and wherever my laptop is
Posts: 1,350
Likes: 0
Received 0 Likes
on
0 Posts
"FAA fines Boeing for unapproved sensors on almost 800 737s"
OK, what's the truth here? Is there a real safety problem with the sensors, or is it just a question of incorrect documentation that is perhaps old news anyway?
My money's on the latter, but I'm curious to see if that's right.
OK, what's the truth here? Is there a real safety problem with the sensors, or is it just a question of incorrect documentation that is perhaps old news anyway?
My money's on the latter, but I'm curious to see if that's right.
The sensors were installed before the formal certification for use on the particular aircraft type. Later that paperwork was completed with no changes to the sensors.
I think the sensors were already approved for other aircraft, just not specifically for the 737-NG.
Sadly, it's painfully simple to mess up the paperwork, and the FAA/Boeing systems make it more so.
Even after a change is certified, there is a requirement to notify the FAA of it's first installation in each major and minor model - so for example it you certify the change for the 737NG, you'd need to notify of the first time it was delivered in a 737-700, 737-800, 737-900, and if they ever built another the 737-600.
When we put together the cert plans, we need to call out the incorporation point for each minor model. However, that's months (or even years) before the actual incorporation, schedules change, and new aircraft don't always deliver in line number order, so it's really easy to mess this part up - and the Boeing system doesn't help.
I personally got caught up in this shortly before I retired on the 747-8 - we'd made an engine control change, did everything per the cert plan, with incorporation points for both the 747-8 and the 747-8F. Except that the airline that was supposed to receive the first 747-8 went bankrupt and the aircraft 'ticket' and delivery didn't happen, but no one bothered to inform me. We delivered half a dozen 747-8 Intercontinentals with the change before we stumbled across the issue and informed the FAA - they were not amused. I spent the next month arguing with the Boeing Regulatory Administration (RA) over who was responsible - me or the RA. I finally threw it back and them and said they needed a system that - if a delivery was delayed or cancelled - would notify the Cert Plan owners who called out that aircraft as initial incorporation so they could take appropriate action. Since such a system was not in place, it was the RA's fault and they owned the escape. They didn't figure out how to throw it back at me before I retired - no idea what happened after that...
Even after a change is certified, there is a requirement to notify the FAA of it's first installation in each major and minor model - so for example it you certify the change for the 737NG, you'd need to notify of the first time it was delivered in a 737-700, 737-800, 737-900, and if they ever built another the 737-600.
When we put together the cert plans, we need to call out the incorporation point for each minor model. However, that's months (or even years) before the actual incorporation, schedules change, and new aircraft don't always deliver in line number order, so it's really easy to mess this part up - and the Boeing system doesn't help.
I personally got caught up in this shortly before I retired on the 747-8 - we'd made an engine control change, did everything per the cert plan, with incorporation points for both the 747-8 and the 747-8F. Except that the airline that was supposed to receive the first 747-8 went bankrupt and the aircraft 'ticket' and delivery didn't happen, but no one bothered to inform me. We delivered half a dozen 747-8 Intercontinentals with the change before we stumbled across the issue and informed the FAA - they were not amused. I spent the next month arguing with the Boeing Regulatory Administration (RA) over who was responsible - me or the RA. I finally threw it back and them and said they needed a system that - if a delivery was delayed or cancelled - would notify the Cert Plan owners who called out that aircraft as initial incorporation so they could take appropriate action. Since such a system was not in place, it was the RA's fault and they owned the escape. They didn't figure out how to throw it back at me before I retired - no idea what happened after that...
Pegase Driver
Join Date: May 1997
Location: Europe
Age: 74
Posts: 3,693
Likes: 0
Received 0 Likes
on
0 Posts
To be fair I think these sorts of things happened before quite a few times with various manufacturers , it is just that now the media picks up everything that from the FAA has the name Boeing on it .
Join Date: Jan 2008
Location: Melbourne
Age: 77
Posts: 14
Likes: 0
Received 0 Likes
on
0 Posts
Well Boeing painted themselves into this corner by cutting so many corners and flaunting so many rules and regulations. They cannot blame anyone but themselves if they are now being nick picked. They well and truly earned it.
Join Date: Aug 2006
Location: Looking for the signals square at LHR
Posts: 236
Likes: 0
Received 0 Likes
on
0 Posts
Join Date: Jan 2013
Location: Seattle Area
Posts: 263
Likes: 0
Received 0 Likes
on
0 Posts
This was not "just a documentation issue." The HUD units were originally approved to be installed in combination with particular sensors based on compatibility demonstrations by the HUD vendor. Later, Boeing made a production change to use different sensors without the HUD vendor demonstrating that the HUD worked properly with the different sensors. After the issue was discovered (after delivery of many airplanes) the evaluation was done to verify the sensors were compatible with the HUD. It turned out they were, so no design change was necessary. "Paperwork" was involved, but that paperwork documented a compliance showing activity that was only done after many airplanes had already been delivered prior to the proper evaluation. While it didn't bite them in terms of an event caused by an incompatibility, that's not a trivial error.
Do you have a link to it? I'll try to find the one I saw again.
Join Date: Mar 2014
Location: Way north
Age: 47
Posts: 497
Likes: 0
Received 0 Likes
on
0 Posts
We were at one point told we were not allowed to change the setup, hence move phones, monitors etc., on a workstation... because the setup was approved by the authorities, and any moving around would require paperwork. Even changing a monitor to another, would require so... they needed the correct serialnumber, not just the specific type of monitor...
And we're ATC.
And we're ATC.
Pegase Driver
Join Date: May 1997
Location: Europe
Age: 74
Posts: 3,693
Likes: 0
Received 0 Likes
on
0 Posts
We were at one point told we were not allowed to change the setup, hence move phones, monitors etc., on a workstation... because the setup was approved by the authorities, and any moving around would require paperwork. Even changing a monitor to another, would require so... they needed the correct serialnumber, not just the specific type of monitor...
And we're ATC.
And we're ATC.