If a Robotaxi Crashes in Oregon: What Evidence May Show Responsibility

The absence of a human behind the wheel changes the evidence questions after a crash. It does not supply an automatic answer about fault.

Two separate developments make those evidence questions timely: federal regulators have opened an inquiry into Tesla’s certification basis for its 2026 Robotaxi, commonly called Cybercab, while Portland is separately considering updates to its automated-vehicle framework. Neither development means Cybercab deployment in Portland is planned or imminent.

The National Highway Traffic Safety Administration (NHTSA) investigation database, updated September 4, 2026, shows that Audit Query AQ26002 opened on September 3. The agency is examining the process and technical data Tesla used to certify Cybercab vehicles as complying with applicable Federal Motor Vehicle Safety Standards, including determinations that certain standards do not apply. The vehicles lack permanently attached conventional controls such as a steering wheel, brake pedal, accelerator pedal, and mirrors.

The Audit Query is not a finding that Cybercab has a safety defect or violates federal law. It is not a recall, negligence finding, causation decision, or civil-liability determination. Federal standards can apply differently depending on the particular standard and vehicle configuration, and manufacturer certification, standard-specific applicability, and a federal exemption are distinct concepts.

The current deployment facts in the approved materials concern Texas—not Oregon. As of September 4, 2026, Portland has no authorized commercial robotaxi service. Portland’s rulemaking is still underway, and human-driven mapping activity on city streets is not driverless testing or passenger service.

For an Oregon claimant, the durable lesson is broader than the current developments: investigating an automated-vehicle crash may require identifying what system was driving, which people and companies supported it, and where electronic and physical records are held.

Key Takeaways

• A vehicle with no in-vehicle driver does not identify who was at fault. Responsibility remains dependent on evidence about operation, design, monitoring, maintenance, control, causation, and the conduct of other road users.
• Potential evidence may extend far beyond an event data recorder. It can include automation-engagement records, sensor or camera data, telematics, software and map versions, remote-assistance communications, operational-domain information, dispatch records, and maintenance or calibration files.
• Federal crash reporting may point to useful evidence categories, but it does not automatically preserve or disclose all underlying company records to an injured person.
• Electronic records may be limited, overwritten, or divided among several entities. Prompt and specific preservation efforts can matter, although access and any court remedy are not guaranteed.
• Portland currently has no authorized commercial robotaxi service, and its February 2026 AV proposal is not a final rule.

Why Cybercab and Portland Put AV Crash Evidence in Focus

Cybercab illustrates why an automated-vehicle investigation cannot stop at the vehicle’s make, model, or outward appearance. NHTSA’s Audit Query concerns the technical and legal basis for Tesla’s certification of the vehicle under the federal standards applicable to it. Federal law generally places the initial certification obligation on the manufacturer or distributor rather than treating vehicle compliance as a categorical agency preapproval.

AQ26002 does not reveal Tesla’s complete certification analysis, the particular standards it treated as inapplicable, the underlying test data, or NHTSA’s eventual conclusion. Nor does the lack of conventional controls itself prove illegality, a product defect, negligence, or crash causation.

The U.S. Department of Transportation’s September 3 national AV strategy adds federal policy context for fiscal years 2026–2030. It is a roadmap, however—not an operative rule allocating responsibility and not evidence that any specific vehicle is safe or unsafe.

Portland’s preparations raise related questions about operating conditions, safety planning, trip data, and major incidents. Those proposed oversight categories can help readers understand what information may matter. They do not create current civil-discovery rights or prove what records would exist, be retained, or be available after a particular crash.

The First Question Is What Was Driving—and Who Supported It

“There was no driver” is a description of the passenger compartment, not a complete account of how the trip was controlled.

NHTSA’s automated-driving crash-reporting materials distinguish among the vehicle, its automated driving system, the manufacturer, the operator, and the reporting entity. They also recognize that responsibility for operation, fallback, or part of the dynamic driving task may involve an in-vehicle person, a remote person, no person, or another or unknown actor. Those categories frame an investigation; they do not decide liability.

Was the ADS Engaged Before and During the Crash?

An early factual question is whether an automated driving system (ADS) was active and, if so, when. A vehicle may be capable of automation without using it on a particular trip. A human-driven mode, an ADS, or a Level 2 driver-assistance feature may present different evidence and reporting questions.

NHTSA’s current reporting order asks whether ADS or Level 2 advanced driver assistance was engaged at any time from 30 seconds before the crash began through the crash. For that order, “engaged” includes an attempted engagement that was rejected, aborted, or underway during the relevant window. That federal reporting window and definition are useful context, but they are not universal definitions of all records relevant to a civil claim. An investigation may need enough synchronized information to determine system status, transitions, alerts, faults, and any fallback event.

Which Entities Performed, Supported, or Controlled Relevant Functions?

Depending on the facts, relevant roles may include the vehicle owner, fleet or operating company, vehicle manufacturer, ADS manufacturer, software or equipment provider, remote-support actor, maintenance provider, and other road users. One company may fill several roles, or records may be distributed across different organizations.

Names and job labels alone do not establish legal responsibility. The important questions include what each entity actually did, which systems it controlled, what information it possessed, how its conduct related to the crash, and what contracts, insurance arrangements, and legal relationships apply.

Why “the ADS Was the Driver” Is Not a Current Oregon-Law Shortcut

Oregon House Bill 4085 would have established statewide rules for driverless operation and for-hire automated vehicles. It did not pass in 2026. Its proposed language cannot be treated as current Oregon law or used to declare that an ADS is legally “the driver” for every purpose.

That leaves no automatic AV-specific liability shortcut. The evidence still must connect relevant conduct or a claimed product issue to the crash and resulting harm under the law that applies to the case.

The AV-Specific Evidence That May Matter

Oregon Rule of Civil Procedure 43 allows parties to seek documents and electronically stored information—including photographs, sound recordings, images, and data compilations—and to request inspection, testing, or sampling of tangible things in another party’s possession, custody, or control. The rule also permits a conference about sources, production format, search terms, preservation, privilege, metadata, and cost. Nonparty records may involve subpoenas under ORCP 55.

Those procedures do not make every record discoverable. Relevance, possession or control, scope, burden, expense, privilege, privacy, trade-secret protections, jurisdiction, objections, and court rulings may limit what can be obtained. The first practical task is to identify records that may exist and the entities that may hold them.

ADS Engagement, Perception, Planning, and System-Event Logs

System records may help answer whether automation was active, what the system detected or classified, how it planned or responded, and whether it recorded alerts, disengagements, fallback events, or faults. Timestamps may be critical when comparing those records with video, physical evidence, and witness accounts.

Not every automated vehicle necessarily creates the same logs or retains raw data for the same period. A request should therefore avoid assuming a universal AV data format or retention schedule.

Sensor, Camera, Telematics, and Location Data

Potential sources may include vehicle video, available sensor or perception records, telematics, route or location information, and related timestamps. These materials may help reconstruct movement and system status when evaluated with scene evidence and other records.

NHTSA’s incident-data definitions separately track whether a reporting entity says event data recorder information, a police or government report, telematics, and video are available. A reported “available” field does not mean that NHTSA or a claimant has verified or obtained the underlying file, or that the public can access it.

Software, Automation-Feature, Map, and Configuration Versions

The vehicle’s model name may not reveal which software or automation feature was operating at the time. NHTSA’s data fields include the automation-feature version, and a case-specific investigation may also examine update history, map version, hardware configuration, and relevant settings.

A version difference or software update does not, by itself, prove a defect or show that software caused a crash. The purpose is to identify the actual configuration before evaluating what the system was intended to do and what happened.

Remote-Assistance and Fallback Records

Some operations may involve remote personnel who monitor, advise, respond to an intervention request, or participate in fallback or part of the driving task. If so, communications, timestamps, requests, actions, and escalation records may help clarify the person’s role.

Remote assistance should not be assumed in every driverless trip, and it is not necessarily the same as continuous remote driving. Even when a remote person participated, that fact alone does not establish fault.

Operational Design Domain Records

An operational design domain, often shortened to ODD, concerns the conditions or domain in which an automated system is intended or authorized to function. Depending on the actual system and available records, relevant information may include the mapped area, road type, weather, time, construction, lane closures, or other operating conditions.

Portland’s proposed framework would require applicants to describe and map a proposed ODD and its conditions. That proposal illustrates why the category matters to oversight. It does not create a current disclosure right or show that a vehicle operated outside its ODD in any particular event.

Fleet, Operator, Dispatch, Maintenance, and Calibration Records

Trip assignment and dispatch records may help identify the operating entity and the specific vehicle. Operator incident reports, maintenance and inspection files, calibration records, complaints, prior system-failure information, and ownership or control records may help connect the system’s condition to the organizations involved.

These are possible evidence categories, not a promise that each record exists, is required, or will be discoverable or admissible. Portland’s draft rule likewise treats deployment experience and major crashes or system failures as proposed disclosure categories, not current claimant-access rights.

The Physical Vehicle, EDR, and Ordinary Crash Evidence

The physical vehicle remains important. Inspection may help document damage and identify components or systems requiring further analysis. An event data recorder (EDR), where the federal rule applies to a covered light vehicle equipped with one, contains standardized short-duration crash or near-crash information—typically 30 seconds or less. Some non-air-bag-deployment event data may be overwritten depending on buffer status and manufacturer choice, while Part 563 requires specified air-bag-deployment event memory to be locked.

An EDR is not a complete robotaxi “black box.” It does not itself provide a full history of ADS perception, planning, video, mapping, dispatch, or remote assistance.

Police or government reports, personal photos and video, witness information, scene evidence, medical records, and Oregon crash reports provide other evidence paths. They complement rather than replace the underlying AV records. For broader principles beyond automated-vehicle data, see this guide to preserving crash evidence in Oregon.

Federal Crash Reporting Can Offer Leads—but Not the Full Evidence File

NHTSA’s Third Amended Standing General Order 2021-01 requires specified vehicle manufacturers, equipment manufacturers, and ADS operators to report certain crashes involving ADS or Level 2 systems. It may provide leads about engagement, versions, roles, and available data. It is not a civil evidence-preservation or disclosure system for claimants.

When a Five-Day ADS or Level 2 Report May Be Required

For an entity named in the order, a report is due no later than five calendar days after the entity receives notice of a crash meeting all of the following criteria; that five-day period is not extended for weekends or federal holidays:

1. The crash occurred on a publicly accessible road in the United States.
2. ADS or Level 2 advanced driver assistance was engaged at any time from 30 seconds before the crash began through the crash, including an attempted engagement that was rejected, aborted, or underway during that window.
3. The crash resulted in a fatality, transport to a hospital for medical treatment, a vulnerable-road-user strike, or airbag deployment. When the subject vehicle has ADS, tow-away of any vehicle involved in the crash also satisfies the outcome criterion.

The tow-away trigger is ADS-specific. The order applies to the named reporting entities, not directly to the injured consumer.

When an ADS Crash May Instead Be Monthly Reportable

An ADS crash outside the five-day category may instead be reportable by the fifteenth calendar day of the month after the month in which the named reporting entity received notice. The monthly category can apply when ADS was engaged during the same 30-second window and property damage is reasonably expected to exceed $1,000. It can also apply below that amount when the ADS vehicle was the only vehicle involved or struck another vehicle or object.

This monthly category concerns ADS-equipped subject vehicles, not Level 2 systems in the same way. Federal reporting thresholds also differ from Oregon’s collision-reporting requirements, so one report should not be assumed to satisfy the other.

What Company Notice and NHTSA Fields May Reveal

The order defines company notice broadly. It can include internal or external information in vehicle reports, test reports, crash reports, media reports, customer reports, claims, demands, and lawsuits—even when the reporting entity has not verified the allegations.

Prompt, accurate notice of a crash may therefore be relevant to a covered company’s federal reporting obligations. Reported fields may identify claimed availability of EDR data, a police or government report, telematics, and video. Other fields address automation engagement, the automation-feature version, and who was responsible for operation, fallback, or part of the dynamic driving task.

None of that creates a private right under the order for an injured person to obtain company files.

Why an NHTSA Report Is Not Proof of Fault or Automatic Discovery

NHTSA warns that public SGO data may be incomplete or unverified, may include more than one report for a single crash, and are redacted for personal information and claimed confidential business information. Reporting can also depend on when the entity receives notice and on its telemetry capabilities. The counts are not normalized by miles driven or other operating exposure.

For those reasons, a public entry is not proof of fault, and raw counts should not be used as comparative safety rates. The absence of a crash from public data does not prove that it never happened or that automation was not involved.

Most importantly for a claimant, the SGO does not require a company to preserve or disclose to that claimant every sensor log, camera file, remote-assistance communication, or engineering record. Civil evidence requests follow separate legal processes.

Preserving and Seeking AV Evidence After a Crash

Electronic evidence can be distributed across the vehicle, fleet systems, vendors, and public agencies. Some information may be short-lived or overwritten. A focused preservation strategy starts by asking who may control each category and describing it precisely.

Identify the Entities and Data Custodians Early

Available identifying information may point to the vehicle owner, fleet or operator, vehicle and ADS manufacturers, hardware or software providers, remote-support entities, maintenance providers, insurers, and public agencies. Different entities may possess different pieces of the record.

Access may depend on possession, custody, or control as well as jurisdiction, privacy, privilege, and trade-secret issues. Identifying a possible custodian does not guarantee that it has the data or must produce them.

Describe the Records Precisely

A generic request for the robotaxi’s “black box” may miss important categories. Depending on the facts, preservation and later discovery efforts may distinguish among:

• ADS engagement, perception, planning, fault, and system-event logs;
• sensor or camera files, telematics, and location or route data;
• EDR data;
• software, automation-feature, configuration, map, and update records;
• remote-assistance and fallback communications;
• ODD and mapping materials;
• trip, dispatch, and operator incident records;
• inspection, maintenance, and calibration records; and
• the physical vehicle and relevant components.

The appropriate scope depends on the crash and the systems involved. ORCP 43’s ESI process may address data sources, production form, search terms, preservation, metadata, privilege, and cost rather than treating electronic evidence as a single file.

Understand That Preservation and Production Are Different Questions

A preservation request may notify a recipient about potentially relevant information, but it does not guarantee retention, later production, or admissibility. Obtaining records may require requests to parties, nonparty subpoenas, an agreement, or a court order. Objections, scope, burden, expense, legal protections, and the recipient’s actual control over the information may affect the result.

Federal crash reporting does not replace those steps. It also does not guarantee that every underlying AV record will remain available while a claim is evaluated.

Avoid Promises About Missing Data

Oregon Evidence Code Rule 311 recognizes a presumption that evidence willfully suppressed would be adverse to the party suppressing it. That is narrower than saying every missing or overwritten log proves wrongdoing.

Whether evidence was preserved, whether its loss was willful, and what consequence may follow are fact- and procedure-specific questions. Missing data alone do not automatically establish fault, justify a sanction, or require an adverse presumption.

Who Could Be Responsible? Oregon Law Requires a Fact-Specific Answer

An automated-vehicle crash can raise questions about operation, product design, monitoring, maintenance, and the conduct of other road users. But a list of possible roles is not a list of liable defendants. Responsibility depends on the evidence, applicable duties and legal relationships, causation, defenses, insurance, and the law governing the claim.

Comparative Fault Still Requires Evidence About Conduct and Causation

Oregon’s comparative-fault statute, ORS 31.600, generally provides that claimant fault does not bar recovery when it is not greater than the combined fault of the persons specified by the statute. Allowed damages are reduced in proportion to claimant fault, and qualifying fault is compared among parties, third-party defendants, and settling persons.

That is a general allocation framework, not an AV-specific answer. The lack of a human behind the wheel does not establish which person or entity qualifies for comparison or what percentage, if any, should be assigned. The evidence must still address conduct and causation within the broader Oregon crash-claim process.

Product Issues Are Possible, Not Presumed

Oregon’s product-liability definition includes actions against a manufacturer, distributor, seller, or lessor arising from alleged design, inspection, testing, manufacturing, or other product defects, as well as failures to warn or instruct properly.

Those categories may become relevant if the facts and technical evidence support them. The involvement of an automated vehicle does not itself establish a defect, and NHTSA’s Cybercab Audit Query proves no defect or causal connection. Oregon product-liability claims require case-specific evidence and legal analysis.

Operational and Organizational Roles May Matter Too

Evidence may also raise questions about fleet operation, dispatch, remote support, maintenance, calibration, or another road user’s conduct. The inquiry should focus on what an actor did or controlled—not assume a duty, agency relationship, insurance obligation, or legal responsibility from a company label.

This role-based approach is why preserving contracts, control records, communications, and technical data may be as important as identifying the vehicle itself.

What Portland Readers Should Know About Current AV Activity

As of September 4, 2026, the Portland Bureau of Transportation’s AV page says it has issued no AV testing permits and that the current 2018 version of TRN-14.34 does not allow for-hire AV operations on Portland streets. No authorized commercial robotaxi service currently operates there.

PBOT says a City testing permit is required for any testing that uses an AV’s ADS on City of Portland streets, even if a human safety operator is present. That city rule should not be generalized to roads Portland does not control. Statewide, the Oregon Department of Transportation says Oregon currently uses a voluntary AV-testing notification process. The state and city frameworks are separate.

PBOT also reports that Waymo and General Motors have used licensed human drivers to map Portland streets while sensors gather information and the ADS is disengaged. That activity is not driverless testing and is not commercial robotaxi service.

Portland’s February 2026 proposed revisions remain unfinished rulemaking. Proposed requirements addressing ODD maps, major crashes or system failures, safety plans, and trip-level data show the kinds of information the City considers relevant to oversight. They are not current civil-disclosure duties or a guarantee that such information would be public, discoverable, admissible, retained, or available after a crash. A separate article discusses Portland’s proposed automated-vehicle rules in more detail.

Because the Cybercab inquiry and Portland’s regulatory status are time-sensitive, both should be checked again before reliance.

Practical Next Steps After an Oregon AV Crash

After a crash involving a vehicle that appeared automated or driverless, practical early steps may include:

1. Preserve identifying details. Keep available information about the vehicle, fleet or operator, trip, app or account, receipts, and communications.
2. Record what was observed without overstating it. Note whether the vehicle appeared to lack an in-vehicle driver and whether remote or in-vehicle support was disclosed. Appearance alone does not establish whether ADS was engaged.
3. Keep complementary evidence. Preserve personal photos and video, crash and medical records, and witness contact information. These materials can help correlate or test electronic data.
4. Identify likely data custodians. Consider which entities may hold vehicle, ADS, fleet, remote-support, maintenance, insurance, or government records.
5. Describe AV records specifically. Prompt preservation efforts may be more useful when they identify particular data categories instead of requesting a generic “black box.”
6. Do not wait for a public NHTSA entry to explain the event. Public federal data have important limits and may not include the underlying records.
7. Seek case-specific guidance promptly. Potential parties, preservation options, public-body notice requirements, claim theories, jurisdiction, and deadlines can vary. Oregon personal-injury and product-liability laws contain different timing provisions, and wrongful-death, public-body, discovery, repose, and other issues may alter the analysis.

No single step guarantees that evidence will be retained or produced. Early, accurate identification of the vehicle, operating system, relevant entities, and possible data sources can nevertheless make the investigation more focused.

Frequently Asked Questions

Who Is Liable if a Robotaxi Causes a Crash in Oregon?

There is no automatic answer. Responsibility may depend on evidence about ADS engagement, system design, fleet operation, remote support, maintenance, other road users, causation, and the legal relationships among the involved entities. Oregon comparative-fault and product-liability laws provide frameworks, not presumptions against a manufacturer or operator.

What Data Should Be Preserved After an Automated-Vehicle Crash?

Potentially relevant categories may include ADS and system-event logs, sensor or camera files, telematics, EDR data, software and automation-feature versions, update and mapping records, remote-assistance communications, ODD materials, dispatch records, maintenance and calibration files, incident reports, and the physical vehicle. Whether a record exists, is retained, or can be obtained varies by case.

Is an Event Data Recorder the Same as a Robotaxi Black Box?

No. Federal Part 563 EDR rules standardize limited, short-duration crash or near-crash information for covered light vehicles equipped with an EDR. An EDR is not a complete record of ADS perception, planning, camera data, mapping, dispatch, or remote assistance.

Does a NHTSA ADS Crash Report Give an Injured Person Access to Company Files?

No. NHTSA’s Standing General Order requires reporting by covered entities, but it does not automatically preserve or disclose every underlying record and does not create a claimant’s private right to company data. Civil evidence access may involve requests, subpoenas, agreements, or court orders.

Are Commercial Robotaxis Operating in Portland Now?

According to PBOT’s information reviewed September 4, 2026, no authorized commercial robotaxi service operates on Portland streets. Human-driven mapping with the ADS disengaged is different from driverless testing or passenger service.

Does NHTSA’s Cybercab Audit Query Mean the Vehicle Is Defective?

No. AQ26002 is an open examination of Tesla’s certification process and technical basis. It is not a recall or a finding of defect, noncompliance, violation, negligence, causation, or civil liability.

Sources and Source Notes

• NHTSA Defect Investigations database, AQ26002 — official opening summary for the Cybercab certification inquiry. The database was updated September 4, 2026; the record lists September 3, 2026, as the opening date.
• 49 U.S.C. § 30115 and 49 C.F.R. § 567.4 — manufacturer certification and certification-label requirements.
• 49 U.S.C. § 30118 — separate statutory process for agency defect or noncompliance decisions.
• USDOT, America Leads: DOT’s National Strategy for Automated Vehicles — September 3, 2026 policy roadmap for fiscal years 2026–2030.
• NHTSA, Third Amended Standing General Order 2021-01 and SGO Data Element Definitions — current federal crash-reporting triggers, definitions, and reported evidence categories.
• NHTSA, Standing General Order on Crash Reporting — public data and limitations.
• 49 C.F.R. Part 563 — federal requirements for specified EDR data in covered equipped vehicles.
• PBOT, Automated Vehicles: Portland’s approach and PBOT’s proposed AV administrative-rule update — Portland’s current status, testing distinction, and unfinished rulemaking.
• ODOT, Automated Vehicles — Oregon’s voluntary statewide AV-testing notification process.
• Oregon Legislative Information System, HB 4085 — legislative status of the unsuccessful 2026 automated-vehicle bill.
• Oregon Rules of Civil Procedure, ORCP 43 — discovery of ESI, data compilations, images, recordings, and tangible things.
• ORS 31.600, ORS 30.900 and ORS 30.905, and ORS 40.135 — comparative fault, product-liability provisions, and Oregon Evidence Code Rule 311.
• ORS 802.040, ORS 810.460, and ORS 811.720 — Oregon crash-report information and state collision-reporting requirements.

This article provides general educational information only and is not legal advice. Automated-vehicle evidence, responsibility, reporting requirements, and claim deadlines depend on the facts and law applicable to a particular matter.