The deadly 2018 Uber crash in Tempe was a compound safety failure: the automated driving system detected the pedestrian but misclassified her, failed to predict her path, and did not slow down, while the sole safety operator was looking at her cellphone. The NTSB’s formal finding was that Uber Advanced Technologies Group had an inadequate safety culture, including weak risk assessment, ineffective operator oversight, inadequate safeguards against automation complacency, and insufficient state oversight.
The NTSB assigned probable cause to the operator’s prolonged visual distraction, but it did not find that the technology or Uber’s management performed adequately. The investigation showed why a developmental automated driving system cannot be made safe simply by putting a human behind the wheel.
As an Amazon Associate I earn from qualifying purchases.
The deadly 2018 Uber crash in Tempe was not caused by a single sensor failure or by a car that simply failed to see a pedestrian. The automated driving system detected the pedestrian 5.6 seconds before impact, but it misclassified her, failed to predict her path, did not slow down, and had its forward-collision warning and automatic emergency braking unavailable during automated operation. At the same time, the sole safety operator was looking down at her cellphone instead of monitoring the roadway.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The National Transportation Safety Board’s formal conclusion was more precise than the phrase “lax attitude toward safety”: Uber Advanced Technologies Group had an inadequate safety culture. The NTSB identified weak risk assessment, ineffective oversight of vehicle operators, inadequate safeguards against automation complacency, and insufficient state oversight. The agency assigned probable cause to the operator’s prolonged visual distraction, while finding that the technology and organizational failures contributed to the fatal outcome.
#1 Best Overall
- UPSCALED 4K FRONT + 1080P REAR DUAL DASH CAM: The ROVE R2-4K DUAL records the road ahead and behind at the same time. The front camera captures at 2.5K (QHD) and intelligently upscales to 4K (2160P) for higher-detail playback, while the rear camera records at Full HD 1080P. This is upscaled 4K, not native 4K, engineered to show sharper everyday detail than standard 1080P dash cams, so you can read license plates, signs, and surroundings in front and rear footage.
- SONY STARVIS 2 IMX675 SENSOR + SUPER NIGHT VISION: The front camera uses a Sony STARVIS 2 IMX675 5MP image sensor with a wide F1.5 aperture (F1.8 rear) and HDR to pull in more light for clearer low-light footage. This advanced sensor enhances nighttime clarity, helping capture license plates, road signs, and surrounding vehicles with greater reliability when driving after dark, through tunnels, or in dusk and dawn conditions.
- ULTRA FAST 5.8GHz WIFI/ UP TO 20MB/s DOWNLOAD SPEED: With its built-in dual-band 5.8GHz and 2.4GHz WiFi, you can use the ROVE dash cam app to view and manage dash cam recordings instantly on your iPhone and Android smartphone. Using the ROVE app, download your recorded videos directly to your smartphone at up to 20 MB/sec, then easily share them on social media with friends and family. Additionally, manage camera settings and update the latest firmware over-the-air via the ROVE App.
- CAR CAMERA WITH GPS: The new front and rear dashcam comes with built-in GPS, which enables you to view real-time live speed and compass on the 3” IPS wide camera screen. It records precise driving routes, locations, and speed stamps directly on the video so you can watch dashcam videos with GPS data using ROVE's free GPS Player on your PC or Mac & get additional evidence when you need it.
- FEATURES WITH STATE-OF-THE-ART TECHNOLOGY INCLUDED: Experience peace of mind with this front and rear car dash cam. It comes with a free 128GB microSD card and offers advanced features such as an f1.5 aperture, motion detection, G-sensor, seamless loop recording, emergency video lock, screen saver, live speed and compass direction, voice guidance, ring of threads for optional CPL filter, a built-in supercapacitor for extended product life, support for up to 1TB microSD cards, and many more.
What happened in Tempe
At approximately 9:58 p.m. Mountain Standard Time on March 18, 2018, a modified 2017 Volvo XC90 operated by Uber ATG was traveling in automated mode on North Mill Avenue in Tempe, Arizona. The vehicle had been operating in automated mode for about 19 minutes and was traveling approximately 45 mph as it approached the crash site.
A 49-year-old woman was walking a bicycle across the northbound lanes at a location without a crosswalk. The vehicle struck and fatally injured her. The safety operator inside the vehicle was not injured.
The NTSB’s Tempe investigation showed a compound failure:
- The automated driving system detected an object in the roadway 5.6 seconds before impact.
- It first classified the object as a vehicle, then as an unknown object, and later as a bicyclist.
- It did not correctly predict that the pedestrian would cross into the vehicle’s path.
- It continued tracking the pedestrian but did not reduce the vehicle’s speed in response.
- The human operator looked away from the roadway for an extended period.
- The vehicle was traveling approximately 39 mph at impact.
- The operator redirected her gaze toward the road about one second before impact and began steering left only 0.02 seconds before the collision.
The timing is important. This was not a case in which the system had no information about what was ahead. It perceived something, but its classification, prediction, response logic, and human-monitoring safeguards did not convert that information into a safe action.
The crash timeline
| Time or event | What happened | Why it matters |
|---|---|---|
| About 19 minutes before the crash | The Volvo had been operating in automated mode. | The vehicle was a developmental automated test vehicle, not a production-ready car intended to operate without an attentive human monitor. |
| Approach to the crash site | The Volvo was traveling about 45 mph on North Mill Avenue. | The system was operating on a public road at a speed that left little room for recovery once the pedestrian’s path was misunderstood. |
| 5.6 seconds before impact | The ADS first detected the pedestrian. | The central problem was not simple failure to detect an object; it was failure to classify and predict the situation correctly and respond safely. |
| Before impact | The system’s classification changed from vehicle to unknown object to bicyclist. | The changing classifications reflected uncertainty and were not followed by an appropriate prediction of the pedestrian’s path. |
| About 1 second before impact | The safety operator redirected her gaze toward the roadway after looking down toward the center console, where her cellphone was located. | She had not been continuously supervising the automated driving system. |
| 0.02 seconds before impact | The operator began steering left. | The attempted intervention came too late to avoid the collision. |
| Impact | The Volvo was traveling about 39 mph when it struck the pedestrian. | The pedestrian suffered fatal injuries; the operator was not injured. |
What the automated driving system did—and failed to do
Detection was not the same as understanding
It is misleading to say that the Uber vehicle could not see the pedestrian. According to the NTSB, the ADS detected her 5.6 seconds before impact and continued tracking her. The failure occurred in the next stages of automated driving:
- Classification: The system initially identified the pedestrian as a vehicle, then an unknown object, and then a bicyclist.
- Prediction: It did not correctly anticipate the pedestrian’s path across the northbound lanes.
- Planning and response: It did not reduce speed in response to the detected object.
- Fallback protection: The vehicle’s safety layers were not configured to provide an equivalent emergency response when the ADS failed to handle the situation.
This distinction matters beyond this particular crash. A vehicle can have sensors that detect an object while still failing to determine what that object is doing. Safe automated driving requires reliable perception, classification, path prediction, decision-making, and control—not merely an image or radar return.
Emergency braking had been disabled during ADS operation
The NTSB found that Uber had disabled the Volvo’s forward-collision warning and automatic emergency braking while the ADS was operating. The ADS design also precluded emergency braking in situations it classified as unavoidable.
Disabling a vehicle’s factory safety systems is not automatically unsafe if an automated-driving developer replaces their capabilities with an equally effective or better-tested system. In this case, however, the NTSB found that Uber had not replaced the full protective function with equivalent safety redundancy. That removed a layer of defense during public-road testing.
The issue was therefore not simply that the ADS made a bad prediction. The system was also designed so that one of the vehicle’s conventional last-resort protections would not provide emergency braking in the relevant circumstances. That increased the consequences of a perception or prediction error.
The human-monitoring problem
The Uber vehicle still depended on a human safety operator. The operator’s job was not to sit passively in a vehicle that was already safe to drive itself; she was expected to monitor the driving environment and the ADS continuously and intervene when necessary.
Inward-facing-camera footage showed the operator looking toward the bottom of the center console, where she had placed her cellphone. She looked away for an extended period and returned her gaze to the roadway approximately one second before impact. She began steering left just 0.02 seconds before striking the pedestrian.
Recommended Free Tools
Rank #2
- 💖💖【Important Note】Due to soaring memory chip costs, many brands have eliminated memory cards entirely, requiring a separate purchase. However, to save you the hassle of buying extra accessories, we are resisting cost pressures without raising our dashcam's price. Starting June 26, 2026, this camera will include a 32GB memory card (previously 64GB) so you can still use it out of the box. For extended storage, we highly recommend purchasing a Class 10, U3, and V30 (or higher) memory card.
- 【4K 2160P Resolution Dash Cam】Capture every drive in stunning 4K UHD resolution with the Galphi front dash cam, featuring a 160-degree wide-angle lens for clear, cinematic video footage. Ideal for family cars, new drivers, and Uber/Lyft drivers, it provides reliable video evidence for accident disputes and insurance claims.
- 【Advanced 5GHz WiFi with App】 Featuring cutting-edge 5GHz WiFi and a free app, the video download speed reaches up to 8MB/s, compared to just 2MB/s with the 2.4GHz option. This greatly reduces download times and minimizes lag during video playback.
- 【No Screen & Less Distraction】This dash camerma features a screen-free design, minimizing distractions while you drive so you can stay focused on the road. Enjoy peace of mind knowing your camera is recording without taking your attention away from the journey.
- 【Compact and Super Easy to Install】The dash cam's slim and compact design ensures it won't obstruct your view. With easy installation and clear, detailed instructions included, even first-time users can set it up without any hassle.
The NTSB assigned the crash’s probable cause to the operator’s failure to monitor the driving environment and the ADS because of that prolonged visual distraction. This finding identifies the immediate human action that allowed the vehicle to continue without intervention. It does not mean the automated system, Uber’s management, or the testing environment performed adequately.
Automation complacency is an engineering risk
The NTSB treated the operator’s behavior as automation complacency: a person assigned to supervise automation disengaged from the monitoring task because the drive appeared uneventful. The longer the vehicle operates without an obvious problem, the easier it can become for a human monitor to assume that continued attention is unnecessary.
That risk cannot be controlled simply by instructing a person to pay attention. Effective human oversight depends on several safeguards working together:
- an operator who understands the system’s limitations;
- an interface that keeps the monitoring task clear and manageable;
- real-time detection of whether the operator is looking at the roadway;
- alerts and escalation procedures when attention is lost;
- management that checks compliance rather than relying on written rules;
- staffing that provides enough capacity and redundancy for the task; and
- automated fallback systems that do not assume the human will always react in time.
The NTSB found that Uber did not adequately recognize or control the risk that an operator would disengage while the ADS was driving.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRemoving the second operator reduced redundancy
Uber had removed the second vehicle operator before the crash. That decision increased the workload placed on the sole operator and eliminated another layer of human redundancy.
“Human oversight” is therefore not a yes-or-no safety feature. One person in the driver’s seat is not equivalent to a robust monitoring system. The effectiveness of oversight depends on staffing, attention monitoring, training, workload, procedures, and organizational enforcement. A single distracted operator can become a single point of failure, particularly when the automated system is developmental and its emergency responses are limited.
The NTSB also found that Uber had the means to monitor operator behavior and compliance with procedures after the fact but rarely did so. The company’s ability to review operator conduct existed, but its oversight was not used effectively enough to identify and correct unsafe monitoring behavior before the crash.
Why the NTSB described Uber’s safety culture as inadequate
The NTSB’s language about safety culture was not a finding that Uber employees intentionally disregarded safety. It was an assessment of whether the organization had the systems needed to identify hazards, control them, and verify that safeguards were working.
Free tools Windows power users keep installed
One-click scans. No signup required.
The agency identified four major organizational and oversight shortcomings.
1. Inadequate safety-risk assessment
Uber ATG did not adequately manage the risks associated with the developmental system’s known functional limitations. Those limitations included the inability, demonstrated in this crash, to correctly classify and predict the path of a pedestrian crossing a road outside a crosswalk.
A meaningful risk assessment should have asked what would happen when the ADS was uncertain, how quickly the system could recognize a midblock crossing, whether the vehicle would slow or stop, and what would happen if the human monitor was not paying attention. The NTSB found that Uber did not sufficiently address those anticipated risks.
Rank #3
- 【1296P front recording and night vision】 The V300 front dash cam records in 2304 x 1296P to capture everyday road details with greater clarity than standard 1080P. A 170° wide-angle lens covers multiple lanes, while the F1.7 aperture and 6-layer glass lens help improve visibility during nighttime driving and other low-light conditions.
- 【WiFi app control 】Connect your phone to the dash camera’s built-in Wi-Fi and use the VeeCar app to preview live video, play back recordings, download clips, and share files. The Wi-Fi connection is local and does not provide internet access; this dash camera for cars still requires a power cable during use.
- 【Advanced Safety Engineering】Designed with your safety in mind, Veement V300 mini dash cam incorporates an RTC circuit and eliminates traditional lithium batteries to prevent overheating. This dedication to safety guarantees reliable performance under various conditions, requiring only a continuous USB-C power supply.
- 【Seamless Connectivity & Easy Operation】Utilize the built-in WIFI and exclusive VeeCar APP to effortlessly control your WiFi front dash cam. From real-time previews to straightforward video downloads, edits, and shares, Veement V300 dash camera for cars offers an intuitive interface for managing your driving footage.
- 【Advanced Features for Complete Protection】Take advantage of cutting-edge TS stream technology in this WiFi dashcam for fast and reliable video storage. Supporting up to 256GB SD cards, seamless loop recording, and 24/7 parking mode, Veement V300 car dash cam provides comprehensive security. Its user-friendly operation ensures a seamless experience. (Note: SD card not included, must be purchased separately).
2. Ineffective operator oversight
Uber had procedures and the ability to review operator behavior, but the NTSB found that the company rarely used its monitoring capability to enforce those procedures. The removal of the second operator further reduced the margin for error.
This is an important distinction between having a safety rule and managing safety. A written instruction to watch the road does little if the organization does not routinely verify compliance, identify distraction, and intervene when operators fail to meet the standard.
3. Insufficient safeguards against automation complacency
The organization did not adequately recognize that a human supervisor might disengage during a quiet automated drive. The NTSB found a lack of mechanisms to address automation complacency, including the risk that the operator would use a cellphone or otherwise stop actively monitoring the roadway.
The crash showed why a developmental ADS should be designed around the expectation that both the machine and the human can fail. Relying on a person to rescue an automated system without continuously checking that person’s attention is not a complete safety strategy.
4. Insufficient state oversight
The NTSB also found that the Arizona Department of Transportation had insufficient oversight of automated-vehicle testing. Public-road testing placed an experimental system, a human operator, other motorists, pedestrians, and cyclists in the same environment, yet the state’s oversight did not provide adequate assurance that the risks were being controlled.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →This finding broadened the issue beyond Uber. The safety of developmental automated vehicles depends not only on the developer’s engineering and management but also on the standards states use before allowing testing on public roads.
Other factors the NTSB considered
The pedestrian was crossing at night outside a crosswalk. Toxicology results also indicated the presence of drugs that could impair perception and judgment. The NTSB identified those circumstances as additional contributing factors.
That does not transfer responsibility for the crash to the pedestrian or make the crossing irrelevant to the investigation. A vehicle being tested on a public road must be evaluated against the real conditions it may encounter, including people crossing outside marked crossings at night. The system detected the pedestrian but did not correctly interpret and respond to her movement.
The NTSB found that several other possibilities were not factors in the crash: the operator’s licensing, experience, knowledge of system operation, substance impairment or fatigue, and the vehicle’s mechanical condition.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What the NTSB recommended
The NTSB’s recommendations focused on creating a more accountable framework for developmental automated-driving tests. Recommendations are safety actions issued by the agency; they are not legislation, a criminal verdict, or a civil-liability judgment.
Federal safeguards and safety self-assessments
The NTSB recommended that the National Highway Traffic Safety Administration require developers testing developmental automated driving systems on public roads to submit safety self-assessment reports. It also recommended a process to evaluate whether those reports included appropriate safeguards, including monitoring operator engagement when a human monitor was part of the system.
Rank #4
- 4-Channel Dash Cam for Complete Vehicle Coverage: This dash cam is equipped with four Full HD 1080P cameras, capturing footage of the front, rear, left, and right sides of your vehicle simultaneously. The adjustable front cameras enhance visibility and offer flexible recording angles, including interior footage.
- Time-Lapse Recording & Parking Mode: With time-lapse recording, 60 minutes of footage is compressed into 1 minute, saving memory card space. Activate parking mode with the optional ACC hardwire kit (sold separately) for security when your vehicle is parked.
- Enhanced Night Vision & WDR Technology: The dash cam features advanced night vision and Wide Dynamic Range (WDR) technology for clear, balanced footage, even in low-light conditions. Eight infrared lights ensure optimal visibility, and WDR adjusts exposure to capture detailed images in varying lighting.
- Optional GPS for Real-Time Vehicle Tracking: Purchase the GPS logger (sold separately) to add location, speed, and time tracking, providing a visual representation of your vehicle's route. This feature is perfect for documenting travel details in case of incidents.
- 5GHz Wi-Fi & App Integration: Share videos easily via Wi-Fi using the mobile app for both iOS and Android devices. This feature allows for quick video downloads and sharing on your preferred platforms.
The broader point was that a developer should have to explain how it will manage known hazards before putting an experimental vehicle into public traffic—not merely describe the technology after an incident.
Testing applications and expert review
The recommendations also called for testing applications that detail how a developer will manage crash risks and operator-inattentiveness risks, including countermeasures intended to prevent crashes or reduce their severity. The NTSB recommended expert review of applications before states grant testing permits.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsThe recommendation package addressed federal agencies, states, the American Association of Motor Vehicle Administrators, and Uber ATG. Together, the recommendations reflected the need for consistent expectations instead of leaving each company or state to decide independently how much safety evidence is enough.
A safety-management system for Uber ATG
The NTSB directed a recommendation to Uber ATG to complete a safety-management system covering four core elements:
- safety policy;
- safety risk management;
- safety assurance; and
- safety promotion.
A safety-management system is intended to make safety an organized, measurable business process. It should identify hazards, assign responsibility, verify that controls work, and ensure that lessons are incorporated into operations and training.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What changed after the crash
The NTSB report noted several postcrash changes that began addressing the identified weaknesses:
- Forward-collision warning and automatic emergency braking were made available during ADS operation.
- A second vehicle operator was added.
- Real-time monitoring of operator attentiveness was introduced.
These changes are significant because each addresses a different failure layer: vehicle-level redundancy, human redundancy, and active supervision. However, they should not be presented as proof that Uber’s entire program became safe or that every recommendation was fully implemented. They were corrective measures identified in the aftermath of the investigation.
What remains unresolved
The NTSB’s later automated-vehicle recommendations information records the recommendation directed to Uber ATG to complete a safety-management system as closed on April 26, 2024. The state-related recommendations are recorded as closed on December 15, 2020.
A closed recommendation does not establish that every automated-driving system is safe or that the United States has adopted a comprehensive approval regime for all automated-vehicle testing. The NTSB’s current description says voluntary safety self-assessment reports submitted to NHTSA can provide limited benefit because NHTSA does not evaluate them. It also says federal safety standards and meaningful testing protocols remain incomplete.
Those distinctions matter. The Tempe investigation established what went wrong in one test program and what the NTSB believed should change. It did not, by itself, create a federal certification system for automated-driving developers or prove that later systems have eliminated the same classes of risk.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat this crash teaches about automated driving
The most useful lesson is not that automated driving is inherently impossible or that human drivers are always safer. It is that a developmental automated system cannot be made safe merely by placing a person behind the wheel and calling that person a safety backup.
Best Value
- [4K+1080P Front & Rear Recording] REDTIGER F7NP dash cam captures every detail with stunning 4K front and 1080P rear video. Featuring the advanced STARVIS 2 sensor plus the 170° front and 140° rear wide-angle lens, this dash camera delivers sharper images, balanced lighting, and reliable evidence day or night. Ideal for commuting, road trips, rideshare drivers, and new drivers.
- [STARVIS 2 Sensor & WDR Night Vision] Equipped with the advanced STARVIS 2 sensor, F1.5 large aperture, and 6-layer optical lens, F7NP 4K dual dash cam delivers clear, high-contrast footage in any lighting. WDR and HDR technology balance highlights and shadows, ensuring sharp night vision and crisp details day or night, providing reliable evidence and enhanced safety for every drive.
- [Built-in 5.8GHz WiFi & Smart App] Connect your smartphone to the dashcam’s built-in 5.8GHz WiFi to enjoy ultra-fast downloads up to 20MB/s. Using Redtiger Cam app, you can preview, download, and replay videos in real time, check GPS ata (route, speed, and location), and manage settings effortlessly, making it simple to review footage and share important moments.
- [Loop Recording & Free Memory Card] This car camera supports seamless loop recording to ensure continuous coverage without interruption. Older files are automatically overwritten when storage is full, while important events are safely locked. A free memory card is included, giving you ample space for 4K recordings and allowing you to use the camera right out of the box.
- [24/7 Parking Mode* & G-Sensor] Enjoy round-the-clock protection with two parking modes: time-lapse recording for continuous low-bitrate monitoring and G-sensor mode that records when collision is detected. The car security camera with G-sensor automatically locks important clips, ensuring crucial evidence is safely preserved even while your vehicle is parked.(*Hardwire kit needed.)
A credible public-road testing program needs layered protection:
- Known limitations must be treated as risks. If the system has difficulty with unusual crossing patterns, the developer must define operating limits and add safeguards for those situations.
- Human monitoring must be measurable. The program should detect whether the operator is attentive in real time rather than assuming that a trained person will remain engaged.
- Independent vehicle safeguards should remain available. Emergency braking and collision-warning systems should not be removed unless equivalent protections have been demonstrated and validated.
- Redundancy should match the risk. Removing a second operator or another backup may increase workload and eliminate the very margin needed when automation fails.
- Safety management must continue after deployment begins. Data review, operator audits, incident reporting, corrective action, and independent oversight are essential parts of testing.
- Permitting should examine the safety case, not just the novelty of the technology. Public-road testing affects people who did not volunteer to participate in an experiment.
For readers who want deeper technical background, an autonomous-vehicle safety book covering human-machine interaction and risk management—such as Autonomous Vehicle Safety Solutions: Foundations, Technologies, and Prospects for the Future—is a better fit than a generic driving accessory. It is a general technical reference, not a substitute for the NTSB report and not presented as a detailed account of this specific crash.
The bottom line
The NTSB found a chain of failures. The operator was distracted, but the organization had not effectively controlled the risk of distraction. The ADS detected the pedestrian, but it misclassified and mispredicted her movement. Conventional emergency braking was unavailable during automated operation, and the second operator had been removed. Oversight at the state level was also insufficient.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Calling that a “lax attitude toward safety” captures the seriousness but not the NTSB’s exact conclusion. The agency found an inadequate safety culture—one that did not adequately assess known risks, supervise operators, address automation complacency, or provide enough redundant protection for public-road testing.
Primary source: National Transportation Safety Board investigation into the March 18, 2018, collision between a vehicle controlled by a developmental automated driving system and a pedestrian in Tempe, Arizona. The linked NTSB investigation page provides access to the agency’s final materials and docket.
Frequently Asked Questions
Was the Uber vehicle fully autonomous?
No. The vehicle was a developmental automated test vehicle operating with a human safety operator. “Self-driving car” is common shorthand, but it can incorrectly suggest a production-ready vehicle that required no human supervision.
Did the Uber automated system detect the pedestrian?
Yes. The ADS first detected the pedestrian 5.6 seconds before impact. It classified her successively as a vehicle, an unknown object, and a bicyclist, but did not correctly predict her path or reduce speed in response.
Recommended Free Tools
Who did the NTSB say was responsible for the crash?
The NTSB assigned probable cause to the safety operator’s failure to monitor the roadway and ADS because of prolonged visual distraction by her cellphone. Separately, the NTSB identified Uber ATG’s inadequate safety culture, ADS limitations, and insufficient state oversight as contributing factors.
Did the NTSB find Uber criminally or civilly liable?
No. The NTSB determines probable cause for transportation-safety purposes and issues recommendations. Its report was not a criminal verdict or a civil-liability judgment.
Were the NTSB’s recommendations implemented?
The NTSB recorded some recommendations as closed: the state-related recommendations on December 15, 2020, and the recommendation for Uber ATG to complete a safety-management system on April 26, 2024. The agency has nevertheless continued to describe limitations in voluntary safety self-assessments and incomplete federal safety standards and testing protocols.
The Bottom Line
Bottom line: The Uber crash was a compound safety failure, not a simple case of a car failing to see someone. The ADS detected the pedestrian but misclassified and mispredicted her movement; the safety operator was distracted; emergency-braking redundancy was unavailable; and Uber’s oversight and risk-management systems were inadequate. The NTSB’s formal finding was an inadequate safety culture, not intentional disregard for safety.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
