Boeing 787 "Blacklisted" From Some Air Traffic Control Services (flightglobal.com)
An anonymous reader writes: A software glitch causes the Boeing 787 to report its position incorrectly, which has led Australia and Canada to 'blacklist' the aircraft from using ADB-S and until it is resolved the latest Boeing is treated as an aircraft without ADS-B capabilities. The practical implication is that the aircraft is not allowed to use reduced separation procedures and an maximum altitude limit of 29,000 feet was also considered. Boeing denies that the bug causes a safety hazard because existing services (radar) still allow safe operation. A bugfix is coming to restore ADS-B functionality.
It's graceful degradation.
as that can end deadly.
... instead of ATC relying on radar. What could possibly go wrong?
Nav Canada first detected a problem on 1 July 2014 when controllers noticed a 787 appearing to deviate up to 38nm (70km) from its planned track. The controllers alerted the crew by radio, but the pilots insisted their instruments showed they were still on course. Suddenly, however, the 787 “was observed jumping back to the flight plan route” on the controller’s screens, according to ICAO documents.
I'm sorry, but if a plane is reporting that it is 70km from where it actually is, that's no small deviation. That deviation is more than 10 times the required flight separation. It may not pose a safety hazard once controllers already know they have to fall back to the older system. But before this was discovered? That's a HUGE safety hazard. The only reason they can get away with claiming it wasn't a safety hazard was because they lucked out and the system only screwed up when there were no other planes around
Have gnu, will travel.
"an maximum altitude" -- typo, or Euro-grammar gone too far?! It's getting so hard to tell anymore.
Strange things are afoot at the Circle-K.
what's the difference between ADB-S v ADS-B
I'm pretty sure it's a typo. The link for "ADB-S" actually goes to a page discussing ADB-S, so it appears that - as often happens - the slashdot "editors" didn't edit for shit before posting to the front page. Timothy usually does better than this, but the slashdot "editors" are busy in job-hunting mode right now with slashdot up on for sale.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
"A bugfix is coming to restore ADS-B functionality."
$adsb.model = "777-200ER";
Timothy usually does better than this, but the slashdot "editors" are busy in job-hunting mode right now with slashdot up on for sale.
What? Timothy and co. generally *introduce* errors into the submitted summaries.
Saying Timothy is a better editor than the rest of the gang of idiots here is like saying I'm a better at cross-country running than most squid. Yeah, it's valid, but it doesn't mean much.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
Perhaps the bug is really a hidden feature, only revealed by accident. ( This is a shoe in for a Bruce Schneier's Movie Plot Scenario )
Deeply buried in the ADS-B firmware is an emergency setting which, should the Department of Homeland Security get a credible security theatre warning that criminals with smartphones and GPS guided drones are planning to bring down airliners. All airliners with updated ADS-B firmware will report their position as exactly 70nm away from their real position on a pseudo-randomly generated bearing keyed on the date. Thus all participating aircraft are equally displaced in the same direction by the same amount.
As to them darn foreigners, well we shoot them down first to clear the skies lest our majestic fleet become damaged.
I log ADS-B traffic to a PostGIS DB, and as part of the deduplication and data cleaning process, I look at the position reports, time & distance between them and the logged speed to see if they make sense. I sometimes have to add a fudge factor of up to 50km. ADS-B packets can get corrupted in ways that dump1090 can't fix up or detect, and I thought that the errors were due to that. Dump1090 has its own quirks when you're pulling position reports down from its JSON interface, but it's easier than pulling the ADS-B messages directly from its other interfaces and attempting to reconstruct the plane's track from that.
ADS-B has zero security controls. Someone with a simple transmitter could draw a murder of giant dicks swarming in three dimensional space using A-380s as pixels. It's hilariously bad.
FOR SHAME! It's ADS-B not ADB-S.
All share equipment and data streams. So what are the odds that a 787 broadcasting a bad position is also fooling surrounding aircraft into a collision avoidance maneuver (false positive) or tricking them into thinking the affected aircraft is not in conflict (false negative)?
In busy airspace, pilots cannot rely solely on ATC to maintain separation. So that's why these collision avoidance technologies were developed. Shame if they don't work correctly.
Have gnu, will travel.
There is no mention of the time interval
Enough time to travel 70 nautical miles.
Have gnu, will travel.