Slashdot Mirror

An anonymous reader quotes a report from Arizona Daily Star: The autonomous Uber SUV that struck and killed an Arizona pedestrian in March spotted the woman about six seconds before hitting her, but did not stop because the system used to automatically apply brakes in potentially dangerous situations had been disabled, according to federal investigators. In a preliminary report on the crash, the National Transportation Safety Board said Thursday that emergency braking is not enabled while Uber's cars are under computer control, "to reduce the potential for erratic vehicle behavior." Instead, Uber relies on a human backup driver to intervene. The system, however, is not designed to alert the driver. The report comes a day after Uber announced it will be ending it's self-driving vehicle testing in Arizona. The full NTSB report is available here.

The National Transportation Safety Board has removed Tesla from the investigation into a fatal Autopilot accident that occurred in March. The NTSB says it took the action because Tesla had released "investigative information before it was vetted and confirmed by" the agency. "Such releases of incomplete information often lead to speculation and incorrect assumptions about the probable cause of a crash, which does a disservice to the investigative process and the traveling public," the agency writes. The Verge reports: The NTSB's account contradicts Tesla's version of the story. In a statement, the automaker says it decided to remove itself from the investigation on Tuesday because of the NTSB was restricting it from sharing information before the probe ends. The company also accuses the NTSB of being duplicitous, arguing that the agency has released statements about the crash at the same time that it told Tesla not to. "It's been clear in our conversations with the NTSB that they're more concerned with press headlines than actually promoting safety," a spokesperson for the company says. "Among other things, they repeatedly released partial bits of incomplete information to the media in violation of their own rules, at the same time that they were trying to prevent us from telling all the facts. We don't believe this is right and we will be making an official complaint to Congress." The company also said it will issue "a Freedom Of Information Act request to understand the reasoning behind their focus on the safest cars in America while they ignore the cars that are the least safe." The full letter send to Musk from the NTSB can be seen here.

A new lawsuit claims post-tensioning triggered the collapse of the pedestrian bridge at Florida International University, killing five motorists and one worker. Engineering News Record reports According to the lawsuit, the March 15, 2018 collapse occurred while a crew was post-tensioning bars in a diagonal member at the north end of the concrete truss that was the bridge's main element. The post-tensioning compressed the diagonal so that it overstressed a joint in the top chord, the lawsuit claims, triggering hinge failure at a connection in the lower chord and resulting in the catastrophic failure of the rest of the 174-ft-long structure. Post-tensioning that modifies the stresses in a structure is inherently risky and should be performed "in the absence of traffic," the lawsuit claims. [The lawsuit] draws heavily on video of the collapse, a voice message about cracks in the structure that were deemed superficial at that time by the engineer of record and design drawings in the design-build joint venture's proposal.
Slashdot reader McGruber writes: Interestingly, just two days after the collapse, an Anonymous Coward posted that post-tensioning likely led to the collapse of the bridge... A March 21, 2018 NTSB News Release said "The investigative team has confirmed that workers were adjusting tension on the two tensioning rods located in the diagonal member at the north end of the span when the bridge collapsed. They had done this same work earlier at the south end, moved to the north side, and had adjusted one rod. They were working on the second rod when the span failed and collapsed. The roadway was not closed while this work was being performed."
The Miami Herald reports that "how and where precisely the bridge broke apart likely won't be known for months, until the National Transportation Safety Board issues an official finding." While summarizing the leading theories, they're also calling it "the sort of baffling accident that makes structural engineers break out in sweats."

"In September, Slashdot reported on an in-flight collision between an Army UA60 helicopter and a hobby drone over Staten Island," writes Slashdot reader ElizabethGreene. "The NTSB has released its final report on the incident, blaming the drone pilot." Ars Technica reports: After waiting 30 minutes, [drone-owner] Tantashov assumed there had been a mechanical malfunction and that his drone had fallen into the water. He returned home. A week later, Tantashov received a call at work. It was an investigator from the National Transportation Safety Board... Would Tantashov be surprised to learn, the investigator asked, that his drone had not crashed into the water?

And that it had instead slammed into the main rotor of a US Army-operated Sikorsky UH-60M Black Hawk helicopter that was patrolling for the UN General Assembly in Manhattan? And that it had put a 1.5-inch dent in said rotor and led to the helicopter diverting back to its New Jersey base...? As the recently completed NTSB report on the incident puts it, "several [drone] components were lodged in the helicopter."
The drone's serial number was still legible on its motor, and investigators were able to track down its owner by contacting the manufacturer, who'd maintained a record of the sale. The drone's owner said he'd been unaware of "temporary flight restrictions" in effect that night, and "said that he relied on 'the app' to tell him if it was OK to fly." But for two months DJI had disabled the feature that checks for temporary flight restrictions (to perform troubleshooting), and the NTSB notes that that feature "is intended for advisory use only," and it's the responsibility of drone pilots to comply with FAA airspace regulations.

The NTSB also faults the drone's owner for letting it fly out of his line of sight.

"In September, Slashdot reported on an in-flight collision between an Army UA60 helicopter and a hobby drone over Staten Island," writes Slashdot reader ElizabethGreene. "The NTSB has released its final report on the incident, blaming the drone pilot." Ars Technica reports: After waiting 30 minutes, [drone-owner] Tantashov assumed there had been a mechanical malfunction and that his drone had fallen into the water. He returned home. A week later, Tantashov received a call at work. It was an investigator from the National Transportation Safety Board... Would Tantashov be surprised to learn, the investigator asked, that his drone had not crashed into the water?

And that it had instead slammed into the main rotor of a US Army-operated Sikorsky UH-60M Black Hawk helicopter that was patrolling for the UN General Assembly in Manhattan? And that it had put a 1.5-inch dent in said rotor and led to the helicopter diverting back to its New Jersey base...? As the recently completed NTSB report on the incident puts it, "several [drone] components were lodged in the helicopter."
The drone's serial number was still legible on its motor, and investigators were able to track down its owner by contacting the manufacturer, who'd maintained a record of the sale. The drone's owner said he'd been unaware of "temporary flight restrictions" in effect that night, and "said that he relied on 'the app' to tell him if it was OK to fly." But for two months DJI had disabled the feature that checks for temporary flight restrictions (to perform troubleshooting), and the NTSB notes that that feature "is intended for advisory use only," and it's the responsibility of drone pilots to comply with FAA airspace regulations.

The NTSB also faults the drone's owner for letting it fly out of his line of sight.

An anonymous reader quotes a report from USA Today: U.S. investigators said a driver who was killed while using Tesla's partially self-driving car ignored repeated warnings to put his hands on the wheel. In a 538-page report providing new details of the May 2016 crash that killed Ohio resident Joshua Brown in a highway crash in Florida, the National Transportation Safety Board described the scene of the grisly incident and the minutes leading up to it. The agency, which opened an investigation to explore the possibility that Tesla's Autopilot system was faulty, said it had drawn "no conclusions about how or why the crash occurred." The NTSB report appears to deliver no conflicting information. The agency said the driver was traveling at 74 miles per hour, above the 65 mph limit on the road, when he collided with the truck. The driver used the vehicle's self-driving system for 37.5 minutes of the 41 minutes of his trip, according to NTSB. During the time the self-driving system was activated, he had his hands on the wheel for a total of only about half a minute, investigators concluded. NTSB said the driver received seven visual warnings on the instrument panel, which blared "Hold Steering Wheel," followed by six audible warnings.

An anonymous reader quotes a report from Los Angeles Times: The Tesla car involved in a fatal crash in Florida this spring was in Autopilot mode and going about 10 miles faster than the speed limit, according to safety regulators, who also released a picture of the mangled vehicle. Earlier reports had stated the Tesla Model S struck a big rig while traveling on a divided highway in central Florida, and speculated that the Tesla Autopilot system had failed to intervene in time to prevent the collision. The National Transportation Safety Board released a preliminary report Tuesday that confirms some details of the May 7 collision, along with a photo that shows the car with its windshield flattened and most of its roof sheared off. The federal agency also included a photo of the big rig, circling an area on the right side of the tractor-trailer that showed the light damage the truck received from the collision. The 2015 Model S was moving at 74 mph, above the posted 65 mph speed limit, when it struck a 53-foot trailer being pulled by a Freightliner Cascadia truck. Tesla's semi-autonomous Autopilot driving feature was engaged, the report says.

astroengine writes: SpaceShipTwo co-pilot Michael Alsbury was not properly trained to realize the consequences of unlocking the vehicle's hinged tail section too soon, a mistake that led to his death and the destruction of the ship during a test flight in California last year. Responsibility for the accident falls to SpaceShipTwo manufacturer Scaled Composites, a Mojave, Calif., company owned by Northrop Grumman Corp, the National Transportation Safety Board (NTSB) determined at a webcast hearing on Tuesday (PDF). Poor oversight by the Federal Aviation Administration, which oversees commercial spaceflights in the United States, was also a factor in the accident, the NTSB said.

jones_supa writes: There's no video footage from inside the cockpit of the Germanwings flight that left 150 people dead — nor is such footage recorded from any other commercial airline crash in recent years. Unlike many other vehicles operating with heightened safety concerns, airline cockpits don't come with video surveillance. The reason, in part, is that airline pilots and their unions have argued vigorously against what they see as an invasion of privacy that would not improve aviation safety. The long debate on whether airplane cockpits in the U.S. should be equipped with cameras dates back at least 15 years, when the National Transportation Safety Board (NTSB) first pushed regulators to require video monitoring following what the agency called "several accidents involving a lack of information regarding crewmember actions and the flight deck environment." The latest NTSB recommendation for a cockpit image system (PDF) came in January 2015. Should video streams captured inside the plane become a standard part of aviation safety measures?

alphadogg writes: A deadly air crash that killed a pilot and passenger in Colorado last year was likely due to a loss of spatial awareness brought on in part by taking of selfies while in flight, the National Transportation Safety Board has concluded. An examination of the aircraft revealed no apparent problems that would have caused the accident so, based on the previous patterns of behavior, the NTSB concluded that "it is likely that cell phone use during the accident flight distracted the pilot and contributed to the development of spatial disorientation and subsequent loss of control."

Lucas123 writes "In the aftermath of a school bus accident last year, the U.S. National Transportation Safety Board (NTSB) this week called for cars, trucks and buses to be equipped with machine-to-machine communications technology that could help vehicles avoid accidents by knowing what other vehicles are doing. In the bus accident, a Mack truck sped through an intersection slamming into the rear of the bus, killing one and injuring more than a dozen others. 'Systems such as connected vehicle technology could have provided an active warning to the school bus driver of the approaching truck as he began to cross the intersection,' the NTSB stated in its report. Among others, Intel is working with National Taiwan University on M2M technology that would allow vehicles the exchange of data, allowing each to know what's going on around them. 'We're even imagining that in the future cars would be able to ask other cars, "Hey, can I cut into your lane?" Then the other car would let you in,' said Jennifer Healey, a research scientist with Intel."

YIAAL writes "After a multi-car pileup involving two school buses, the NTSB is urging states to ban all cellphones and personal electronic devices in cars, even hands-free phones. But on looking at the NTSB report, it appears that the big problem was a school bus driver who was following too closely, and another school bus driver who wasn't watching the road. Why is the NTSB targeting gadgets instead of bad drivers?"

ducomputergeek writes "According to this AP report, the National Transportation Safety Board says 'States should ban all driver use of cell phones and other portable electronic devices, except in emergencies.' 'The recommendation, unanimously agreed to by the five-member board, applies to both hands-free and hand-held phones and significantly exceeds any existing state laws restricting texting and cellphone use behind the wheel.' So what about all the cars today that come with built-in computers, navigation, internet capabilities, and cell phones?"

Hugh Pickens writes "The NY Times reports that two Northwest Airlines pilots who flew about 110 miles past their destination to the skies over Wisconsin as more than a dozen air-traffic controllers in three locations tried to get the plane's attention had taken out their personal laptops in the cockpit, a violation of airline policy, so the first officer could tutor the captain in a new scheduling system put in place by Delta Air Lines, which acquired Northwest last fall. 'Both said they lost track of time,' said an interim report from the National Transportation Safety Board countering theories in aviation circles that the two pilots might have fallen asleep or were arguing in the cockpit. 'Using laptops or engaging in activity unrelated to the pilots' command of the aircraft during flight,' said a statement from Delta Airlines, 'is strictly against the airline's flight deck policies and violations of that policy will result in termination.' Industry executives and analysts said the pilots' behavior was a striking lapse for such veteran airmen who have a total of 31,000 flying hours of experience between them. In the case of Flight 188, 'Neither pilot was aware of the airplane's position until a flight attendant called about five minutes before they were scheduled to land and asked what was their estimated time of arrival,' the interim report said."

jd writes "The National Transportation Safety Board has now released the text of its examination (full narrative available) into the crash of Steve Fossett's aircraft on Sept 3rd, 2007. It concludes that downdrafts were the likely cause of the crash, dragging the plane into the mountain with such force that, even at full power, it would have been impossible to escape the collision. Pilots experienced in the area report that those winds can rip the wings off aircraft; and Mark Twain remarked that they could roll up a tin house 'like sheet music.' One must wonder why such a skilled aviator was taking a gamble with such hostile conditions, given that he was looking for a flat stretch of land to race cars on, but that is one mystery we shall probably never know the answer to."

linuxwrangler writes "Officials at the National Transportation Safety Board are recommending the government require data recorders in all passenger vehicles. David Sobel of EPIC says his group has privacy concerns - especially when drivers are unaware of the presence of the devices. Auto black-boxes have been covered here before."