May 3, 2024

On May 28, 2019, NHTSA Published an Advanced Notice of Proposed Rulemaking (ANPRM) on Removing Regulatory Barriers for Vehicles with Automated Driving Systems

On May 28, 2019, NHTSA Published an Advanced Notice of Proposed Rulemaking (ANPRM) on Removing Regulatory Barriers for Vehicles with Automated Driving Systems

DATES:  Comments on this ANPRM are due no later than July 29, 2019

BACKGROUND: This ANPRM focuses on ADS–DVs without traditional manual controls and that may also lack other features intended to facilitate operation of a vehicle by a human driver. NHTSA reaffirms that, despite the use of the term ‘‘regulatory barrier’’ in its current and future documents, the existing FMVSSs neither have any provisions addressing the self-driving capability of an ADS nor prohibit inclusion of ADS components on a vehicle. NHTSA also states that nothing in the current standards poses testing or certification challenges for vehicles with ADSs so long as the vehicles have means of manual control and conventional seating, and otherwise meet the performance requirements of the FMVSSs.

DOT’s automation principles are to: (1) Prioritize safety; (2) Remain technology neutral; (3) Modernize regulations; (4) Encourage a consistent regulatory and operational environment; (5) Prepare proactively for automation; and (6) Protect and enhance the freedoms enjoyed by Americans.

NHTSA has also conducted research activities to help inform its decision-making with regard to identifying and resolving regulatory barriers. NHTSA, in collaboration with the Volpe National Transportation Systems Center, conducted a preliminary report identifying barriers to the compliance testing and self-certification of ADS– DVs without traditional manual controls. In March 2016, that report was published. The ‘‘Volpe Report’’ focused on FMVSS requirements that present barriers to the compliance testing and self-certification of ADS– DVs without traditional manual controls because they refer to a human driver.

Based on the Volpe Report findings, in 2017, NHTSA initiated work with Virginia Tech Transportation Institute (VTTI) to expand upon the work performed by Volpe by performing analysis and industry outreach to identify potential approaches for addressing compliance verification barriers.

Phase I of the VTTI project will include the technical translation of 30 FMVSSs and associated test procedures, and will conclude by the end of 2019. Phase II will focus on the remaining FMVSSs and associated test procedures, and is expected to start in 2019 and conclude in mid- 2021. These efforts are anticipated to inform NHTSA’s decisions on updates to the FMVSSs

In addition to these research efforts, NHTSA has also requested input from stakeholders through a January 2018 RFC to identify regulatory barriers in the FMVSS to the testing, compliance certification, and compliance verification of ADS–DVs without traditional manual controls.

NHTSA has determined that most of the potential regulatory barriers to the certification of ADS–DVs without traditional manual controls in the 100-series FMVSSs fall into three categories: (1) The standard requires a manual control; (2) the standard specifies how the agency will use manual controls in the regulatory description of how it will test for compliance; or (3) the definition or use of particular terms (e.g., ‘‘driver’’) become so unclear that clarification is necessary before certification and compliance verification testing is possible.

IV. Stakeholder Feedback

V. Addressing Barriers in the FMVSS A. Example #1 (FMVSS No. 135): Manual Control Required B. Example #2 (FMVSS No. 126): Existing Test Procedures That Cannot Be Executed Absent Manual Controls C. Additional Barrier Examples

VII. Public Participation

II. BACKGROUND:  This Advance Notice of Proposed Rulemaking (ANPRM) is a continuation of NHTSA’s efforts to gather input from stakeholders and the public regarding what approaches to propose to address potential challenges to the verification of the compliance with the Federal Motor Vehicle Safety Standards (FMVSSs) of Automated Driving System-Dedicated Vehicles (ADS–DVs)1 that lack traditional manual controls, but have traditional seating configurations.

NHTSA reaffirms its position that, despite the use of the term ‘‘regulatory barrier’’ in this and other future documents, the existing FMVSSs neither have any provisions addressing the self-driving capability of an ADS nor prohibit inclusion of ADS components on a vehicle. It states that nothing in those standards poses testing or certification challenges for vehicles with ADSs so long as the vehicles have means of manual control and conventional seating, and otherwise meet the performance requirements of the FMVSSs. However, the design of a motor vehicle without manual driving controls, design of a motor vehicle with novel seating configurations or orientations, or a covered party’s disabling of any part of a device or element of design of a motor vehicle or motor vehicle equipment that is currently in compliance with applicable FMVSSs could complicate the compliance of the vehicle to the existing FMVSSs

In the Notice, NHTSA discusses two potential types of regulatory barriers for ADS–DVs without traditional manual controls, describes a FMVSS that exemplifies each challenge, and presents a brief overview of comments on the request for comment (RFC).

The agency also presents and seeks comment regarding the safety impacts of using alternative compliance test verification methods to conduct compliance verification testing for these types of vehicles, assuming that the standards and procedures could be revisited to appropriately ensure the existing standard of performance without requiring, directly or indirectly, manual controls.

III. NHTSA’s Efforts To Provide Guidance and Regulatory Certainty

VI. Possible Approaches To Revising Crash Avoidance Test Procedures

NHTSA’s General Questions for each of the proposed approaches:

1. What are the possible advantages and disadvantages of each approach?

2. Discuss whether each approach fits the requirements and criteria of the Safety Act and enables effective enforcement of the FMVSSs. Explain the basis for your answers.

3. Can more than one of these approaches be specified by the agency as alternative ways for the agency to determine compliance with the same requirement in the same FMVSS? If so, please describe how this could be done consistent with the Vehicle Safety Act, using one or more specific FMVSS requirements as illustrative examples. If more than one approach could be specified for the same requirement in the same FMVSS, do commenters believe that the agency, in assessing compliance with the same requirement in the same FMVSS, choose one approach for one vehicle model, but another approach for a different model? If so, explain why. 4. If only one of these approaches can be used to enforce a particular FMVSS requirement, what factors should be considered in selecting that approach? What policy or other considerations should guide the agency in choosing one alternative approach versus another for determining the compliance of a particular vehicle or item of equipment?

5. With respect to any single approach or combination of approaches, could it be ensured that the compliance of all makes and models across the industry is measured by the same yard stick, i.e., that all vehicles are held to the same standard of performance, in meeting the same FMVSS requirement?

6. What other potential revisions or additions to terms, in addition to ‘driver’, are necessary for crash avoidance standards that NHTSA should consider defining or modifying to better communicate how the agency intends to conduct compliance verification of ADS vehicle.

7. Should NHTSA consider an approach to establish new definitions that apply only to ADS–DVs without traditional manual controls?

8. For compliance testing methods involving adjusting current test procedures to allow alternative methods of controlling the test vehicle during the test (normal ADS–DV function, TMPE, TMEC), or to allow the use of a surrogate vehicle:

a. How could NHTSA ensure that the test vehicle’s performance using the compliance method is an accurate proxy for the ADS–DV’s performance during normal operation?

b. If NHTSA were to incorporate the test method into its test procedures, would NHTSA need to adjust the performance requirements for each standard (in addition to the test procedures) to adequately maintain the focus on safety for an ADS–DV?

9. For compliance testing methods that replace physical tests with non- physical requirements (simulation, documentation):

a. If the test method is used to determine compliance with a real-world test, how can NHTSA validate the accuracy of a simulation or documentation?

b. If NHTSA must run real-world tests to validate a simulation or documentation, what is the advantage of non-physical requirements over these other compliance methods?

10. Would non-physical requirements simply replicate the existing physical tests in a virtual world? If not, what would be the nature of the non-physical requirements (that is, what performance metrics would these requirements use, and how would NHTSA measure them)? Are there ways that NHTSA could amend the FMVSSs to remove barriers to ADS–DVs that would not require using the compliance test methods described in below?

a. Are there any barriers in the FMVSS or NHTSA’s test procedures that could be addressed by altering or removing references to manual controls in the test procedures without substantively changing the FMVSS performance requirement?

b. Are there any changes that NHTSA could make to the FMVSS test procedures that could incorporate basic ADS capabilities to demonstrate performance, such as using an ADS– DV’s capability to recognize and obey a stop sign to test service brake performance?

11. What research or data exists to show that the compliance test method would adequately maintain the focus on ADS–DV safety? What modifications of the safety standards would be necessary to enable the use of the test method?

Specific questions relating to each proposed approach:

A. Normal ADS–DV Operation

One possible approach for vehicle manufacturers to use for self- certification, and the agency to use for compliance verification, is the ‘‘Normal ADS–DV Operation’’ approach. This approach involves operating the ADS– DV without traditional manual controls ‘‘as-is’’ with no extra programming and/ or installation of any kind of manual controls for test maneuver execution. The ADS would be in control of the vehicle during compliance testing with all of its operational restrictions and decision-making capabilities in place. In its most basic form, compliance verification using Normal ADS–DV Operation would require the engineer performing the compliance test to input an appropriate destination using the same input method indicated by the ADS–DV’s manufacturer for real-world operation. Vehicle performance would be observed and assessed during the period of normal on-road vehicle operation.

Analysis The Normal ADS–DV Operation approach may provide the most ‘‘realistic’’ representation of how the vehicle would perform during normal use. This approach could allow NHTSA to continue acquiring vehicles in the same way that U.S. consumers do, from commercial dealerships, and testing actual vehicles to verify they meet the FMVSS requirements. NHTSA is interested in maintaining its policy to buy and test new production vehicles from dealership lots, to the extent possible.

NHTSA believes that there are several test requirements in the FMVSSs for which Normal ADS–DV Operation may be a feasible compliance option if certain assumptions are correct. For example, the FMVSS No. 138 procedure for testing a vehicle’s tire pressure monitoring system requires that the test vehicle is driven on a specific public roadway for a specified distance at the posted roadway speeds. During the test, the vehicle is stopped along the way to reduce tire inflation pressure and then driven again until a low inflation pressure indication is obtained. This test procedure could be modified to permit use of the Normal ADS–DV Operation approach for ADS–DVs by allowing the driving portion of the test to be performed by the ADS, which would be commanded by the test engineer using the ADS–DV’s normal input method to select a destination.

The primary drawback to the Normal ADS–DV Operation approach for ADS– DVs that lack manual controls is that its application is limited to test procedure requirements capable of being performed within the Operational Design Domain (ODD) of the ADS. As such, tests involving vehicle maneuvers or operation at speeds, locations, or other operating conditions not experienced within the vehicle’s ODD could not be performed using this method. For example, a vehicle whose ODD does not include the specified test track for the above TPMS test, whether for geographic or road-type restrictions, could not use this approach to conduct the test. Another drawback of this approach, which several of the alternatives below attempt to correct, is that, even if a vehicle’s ODD could allow it to perform a test, the vehicle may not be equipped with the controls necessary to allow NHTSA to actually conduct the test.

For NHTSA to evaluate the feasibility of the Normal ADS–DV Operation approach for compliance verification, the agency would need more information about the extent to which an ADS–DV can be controlled under normal operation. In addition, it is possible that normal control could be used on some vehicles but not on others, since manufacturers may implement different methods for vehicle operators to communicate with and command the vehicle to accomplish on- road driving.

To the extent that some but not all ADS–DVs could be designed to allow for this type of testing, at least for certain standards, it may be challenging for NHTSA to design appropriately objective standards to cover all ADS–DVs. To address these issues, NHTSA believes it is essential to better understand how operators will interface with and operate these ADS– DVs without traditional manual controls under normal conditions. To better understand the ‘‘Normal ADS–DV Operation’’ approach and its possible applications, the agency asks the following questions.

Questions Specific to This Testing Method:

12. What design concepts are vehicle manufacturers considering relating to how an ADS–DV passenger/operator will interface with, or command (e.g., via verbal or manual input), the ADS to accomplish any driving task within its ODD? Please explain each design concept and exactly how each would be commanded to execute on-road trips.

13. Are there specific challenges that will be encountered with this kind of approach for vehicle compliance verification? Please be specific and explain each challenge.

14. Will all ADS–DVs without traditional manual controls be capable of receiving and acting upon simple commands not consisting of a street address based destination, such as ‘‘drive forward or backwards a distance of 10 feet and stop’’; ‘‘shift from park to drive and accelerate to 25 mph’’; ‘‘drive up onto a car hauler truck trailer’’; etc.? Please explain projected challenges for ADS–DVs without traditional manual controls to complete discrete driving commands and tasks.

15. How would NHTSA ensure that the performance of the ADS–DV during testing is consistent with how the vehicle would perform during actual normal use?

B. Test Mode With Pre-Programmed Execution (TMPE)

Questions Specific to This Testing Method:

16. How could engineers responsible for performing FMVSS compliance assessments of an ADS–DV without manual controls be expected to access and interface with the compliance test library menu?

17. Would the FMVSS need to specify the libraries available to NHTSA to test the vehicle?

18. Is it practical to expect that an ADS–DV without any traditional manually-operated controls can be safely and efficiently operated within the confines of a test track with only a pre-programmed test menu (i.e., without some form of external controller or other means of vehicle control input)?

19. Can an ADS–DV be expected to perform within tight tolerance levels using the regular on-board sensors?

20. How much variation in test results across various test locations (i.e., proving grounds) is expected to result from testing an ADS–DV equipped with the same FMVSS compliance library at different locations? Could the ability to satisfy FMVSS performance requirements depend on the location the tests are performed?

21. Is it reasonable to assume any geofence-based operating restrictions could be suspended while the ADS–DV is operating in a ‘‘test mode’’ intended to assess FMVSS compliance?

22. How could vehicle-based electronically accessible libraries for conducting FMVSS testing be developed in a way that would allow NHTSA to access the system for compliance testing but not allow unauthorized access that could present a security or safety risk to an ADS–DV?

23. Are there other considerations NHTSA should be aware of when contemplating the viability of programmed execution-based vehicle compliance verification?

24. When changes or updates are made to the ADS, how will the TMPE content be updated to reflect the changes and how often would it be updated?

C. Test Mode With External Control (TMEC)

Questions Specific to This Testing Method:

25. Is it reasonable to assume a common (universal) interface, translator, and/or communication protocol between an external controller and any ADS–DV will be developed?

26. What is the most viable method for securely interfacing an external controller with the ADS–DV (e.g., wireless or physical access)?

27. Could a means of manual control be developed that would allow NHTSA to access the system for compliance testing but not allow unauthorized access that could present a security or safety risk to an ADS–DV?

28. Is it reasonable to assume any geofence-based operating restrictions could be suspended while an external controller intended to assess FMVSS compliance is connected to the ADS– DV? 29. Are there other considerations NHTSA should be aware of when contemplating the viability of using an external controller-based vehicle certification?

D. Simulation

Questions Specific to This Testing Method:

30. How can simulations be used to assess FMVSS compliance?

31. Are there objective, practicable ways for the agency to validate simulation models to ensure their accuracy and repeatability?

32. Is it feasible to perform hardware- in-the-loop simulations to conduct FMVSS compliance verification testing for current FMVSS?

33. Is it feasible to perform software- in-the-loop simulations to conduct FMVSS compliance verification testing?

E. Technical Documentation for System Design and/or Performance Approach F. Use of Surrogate Vehicle With Human Controls

Questions Specific to This Testing Method:

34. How can the documentation- focused approach ensure compliance with FMVSS, considering it neither verifies that the vehicles on the road match the documentation nor confirms that the vehicles on the road comply with the FMVSSs?

35. If technical documentation were acceptable for compliance verification, how would the manufacturer assure the agency that the documentation accurately represents the ADS–DV and that the system is safe?

36. Exactly what kind of documentation could be submitted for each kind of FMVSS requirement? Provide specific examples with detailed explanation of the documentation required.

F.  Use of a Surrogate Vehicle with Human Controls

Questions Specific to This Testing Method:

37. To what extent could equivalence of the vehicle components used for conventional and ADS–DVs be demonstrated to assure that surrogate vehicle performance would be indicative of that of a surrogate ADS– DV?

38. How can the agency confirm that the maneuver severity performed by a surrogate manually-drivable vehicle, during FMVSS compliance tests, is equal to that of the subject ADS–DV? For example, how can the characterization maneuvers and subsequent scaling factors in the FMVSS No. 126 ESC test on the surrogate vehicle be confirmed as equivalent on the ADS–DV?

39. If results from FMVSS compliance tests of a conventional vehicle performed by its manufacturer differ from the results of NHTSA tests of an equivalent ADS–DV (particularly if the conventional vehicle complies with the agency’s standards, but the ADS–DV does not), can the conflicting results be reconciled? If so, how?

On May 28, The Federal Motor Carrier Safety Administration Published an Advanced Notice of Proposed Rulemaking Requesting Comments on the Safe Integration of Automated Driving Systems-Equipped Commercial Motor Vehicles

DATES: : Comments on this document must be received on or before August 26, 2019

BACKGROUND:

On April 24, 2017, FMCSA held a public listening session to solicit information on issues relating to the design, development, testing, and integration of ADS-equipped CMVs. The listening session provided interested parties an opportunity to share their views and any data or analysis on this topic with Agency representatives. The Agency also invited interested parties to submit written comments by July 17, 2017. For further information on this see public docket FMCSA–2017–0114, at www.regulations.gov.

FMCSA also commissioned the Department’s Volpe National Transportation Systems Center (Volpe) to conduct a preliminary review of the FMCSRs to identify regulations that relate to the development and safe introduction of ADS. Volpe’s final report is titled ‘‘Review of the Federal Motor Carrier Safety Regulations for Automated Commercial Vehicles: Preliminary Assessment of Interpretation and Enforcement Challenges, Questions, and Gaps,’’ report number MCSA–RRT–17–013, August 2017 is available in public docket, FMCSA– 2017–0114, at www.regulations.gov.

On March 26, 2018, FMCSA published ‘‘Request for Comments [RFC] Concerning Federal Motor Carrier Safety Regulations (FMCSRs) Which May Be a Barrier to the Safe Testing and Deployment of Automated Driving Systems-Equipped Commercial Motor Vehicles on Public Roads’’ (83 FR 12933). The document solicited public comments on existing FMCSRs that may need to be updated, modified, or eliminated to facilitate the safe introduction of ADS-equipped CMVs. Further, FMCSA requested comments on certain FMCSRs likely to be affected as ADS- equipped CMVs appear on our roadways.

ANPRM

The Agency requested responses to the following issues and questions:

1. Do the FMCSRs require a human driver?

1.1. How should FMCSA ensure that an ADS-equipped CMV only operates consistent with the ODD for the ADS equipped on the vehicle?

1.2. What are manufacturers’ and motor carriers’ plans for when and how Levels 4 and 5 ADS-equipped CMVs will become commercially available?

1.3. Should FMCSA consider amending or augmenting the definition of ‘‘driver’’ and/or ‘‘operator’’ in 49 CFR 390.5 or define a term such as ‘‘ADS driver’’ to reduce the potential for misinterpretation of the requirements? 

2. CDL Endorsements?

2.1. Should a CDL endorsement be required of individuals operating an ADS-equipped CMV?

2.2. If so, what should be covered in the knowledge and/or skills test associated with an ADS endorsement?

2.3. What would be the impacts on SDLAs?

2.4. Should a driver be required to have specialized training for ADS-equipped CMVs? 2.5. In an operational model that has an individual remotely monitoring multiple CMVs, should the Agency impose limitations on the number of vehicles a remote driver monitors?

2.6. Is there any reason why a dedicated or stand-by remote operator should not be subject to existing driver qualifications?

3. Drivers’ Hours of Service (HOS) Rules

3.1. Should HOS rule changes be considered if ADS technology performs all the driving tasks while a human is on-duty, not driving; off-duty or in the sleeper berth; or physically remote from the CMV?

3.2. Should the HOS requirements apply to both onboard and remote operators?

3.3. If so, how should HOS be recorded when an individual is not physically in control of the vehicle?

4. Medical Qualifications for Human Operators

4.1. Should some of the physical qualification rules be eliminated or made less stringent for humans remotely monitoring or potentially controlling ADS-equipped CMVs?

4.2. If so, which of the requirements should be less restrictive for human operators who would take control of an ADS-equipped CMV remotely?

4.3. Should the Agency consider less restrictive rules for humans who have the benefit of ADS technology to assist them in controlling the vehicle (e.g., technologies that would enable individuals with limb impairments to operate at a level comparable to individuals without such impairments)?

5. Distracted Driving and Monitoring

5.1. How should the prohibition against distracted driving (i.e., texting, hand-held cell phone) apply to onboard operators responsible for taking control of the CMV under certain situations, and to remote operators with similar responsibilities?

6. Safe Driving and Drug and Alcohol Testing

6.1. Should FMCSA consider revising its rules to ensure that (1) any human exercising control of an ADS-equipped vehicle must continue to comply with all the rules under Part 392, and (2) a CMV under the control of a Level 4 or Level 5 ADS must satisfy the operational rules?

6.2. For example, should FMCSA require that the ADS be capable of identifying highway-rail grade crossings and stopping the CMV prior to crossing railroad tracks to avoid collisions with trains, or going onto a highway-rail grade crossing without having sufficient space to travel completely through the crossing without stopping?

6.3. For scenarios in which the control of the ADS-equipped CMV alternates, or may alternate, between a human and the technology, should FMCSA require that both the human operator and ADS comply with the applicable operational rules?

7. Inspection, Repair, and Maintenance

7.1. What qualifications should be required of the individual performing the pre-trip inspection?

7.2. What kind of routine or scheduled inspections should be performed and what types of ADS-related maintenance records should be required?

7.3. Should the inspection period be more or less frequent than annual for an ADS- equipped CMV?

7.4. Should inspections be mileage-based or time-based (e.g., 1,000 miles, 3 months or 1,000 hours of operation)?

7.5. Should FMCSA impose general requirements for motor carrier personnel responsible for ADS-related inspection, repair, and maintenance tasks similar to the Agency’s brake inspector qualification requirements?

7.6. How could FMCSA ensure that motor carriers apply safety-critical software updates?

8. Roadside Inspections

8.1. Should motor carriers be required to notify FMCSA that they are operating Level 4 or 5 ADS- equipped CMVs?

8.2. If so, how should the carrier notify FMCSA?

8.3. Should FMCSA require markings identifying the ADS Level of a vehicle?

8.4. Should the Agency require motor carriers to utilize ADS-equipped CMVs that have a malfunction indicator?

8.5. Should the Agency require that motor carriers deploying ADS-equipped CMVs ensure the vehicle can pull over in response to Federal and State officials or move out of the way of first-responders?

8.6. How might that be achieved, and at what cost?

8.7. How would roadside enforcement personnel know that a vehicle can no longer operate safely?

8.8. Absent an FMVSS, how could standard indications be provided to enforcement personnel?

9. Cybersecurity

9.1. What types of safety and cargo security risks may be introduced with the integration of ADS- equipped CMVs?

9.2. What types of rules should FMCSA consider to ensure that motor carriers’ safety management practices adequately address cybersecurity?

10. Confidentiality of Shared Information

10.1. As the development of ADS technology continues, the Agency believes there is a need to learn about the performance limitations of these systems. FMCSA draws a distinction between information about performance limitations (e.g., how well does the ADS keep the vehicle in its lane and under what environmental conditions, etc.) and details about the system design (e.g., the specific types of sensors, or the arrays of sensors and cameras used for input to the central processing unit for the ADS). To what extent do ADS developers believe performance data should be considered proprietary and withheld from the public?

10.2. Are the Agency’s current processes under 49 CFR 389.9 for submission and protection of confidential business information in the context of a rulemaking sufficient to allow ADS developers and motor carriers to communicate essential information to the Agency regarding the operation of ADS?

10.3. If not, how should those processes be modified?

FMCSA would like to build upon best practices from the private sector in providing guidance to motor carriers on safe practices for the integration of ADS-equipped CMVs. The Agency would consider use of private sector standards to ensure cost-effective, performance-based safety requirements

On May 15, NHTSA Published a Notice of Propose Rulemaking to Extend the Time Period for Retention of Documents, (49 CFR 576)

DATES: Comments should be submitted by July 15, 2019. 

BACKGROUND:

This rulemaking is in response to Congressional Direction in Section 24403 of the Fix America’s Surface Transportation (FAST) Act, which directs the Secretary of Transportation to issue a rule increasing the time of record retention to a period not less than ten years, instead of five years as presently required under the regulatory provisions.

Based on NHTSA’s experience investigating potential defects and overseeing recalls, it has determined that a ten-year records retention requirement would ensure that the agency’s investigative needs are meet without unnecessarily burdening manufacturers of motor vehicles and equipment. In this NPRM, NHTSA proposes to extend the record retention requirement for records required to be maintained under 49 CFR 576.6 to ten years.

On April 4th, NHTSA Withdrew Its Proposed Rulemaking from 2012 That Would Have Harmonized FMVSS 205 (49 CFR 571.205) with the Global Technical Regulation Number 6

DATES:  The June 21, 2012 NPRM on Glazing material was withdrawn as of April 4, 2019.

RATIONALE:  NHTSA determined that it did not have sufficient data to evaluate the safety implications of harmonizing FMVSS No. 205 with GTR No. 6, and therefore, withdrew the 2012 NPRM.

On February 8th, NHTSA Withdrew Its Proposed Rulemaking from 2012 That Would Have Mandated Event Data Recorders With the Characteristics Required by FMVSR 563 For Optional Event Data Recorders (49 CFR 563)

DATES: The NPRM ‘‘Federal Motor Vehicle Safety Standards; Event Data Recorders,’’ RIN 2127–AK86, published December 13, 2012 (77 FR 74144), is withdrawn as of February 8, 2019

RATIONALE:  At the time the NPRM was published, there were a large number of light vehicles that did not have event data recorders, and NHTSA was proposing to mandate them.  As of the date of withdrawal, almost all light vehicles contain event data recorders, making mandating them unnecessary.