Guidelines for the Safe Deployment and Operation of Automated Vehicle Safety Technologies, 14934-14936 [2016-06143]

Download as PDF 14934 Federal Register / Vol. 81, No. 53 / Friday, March 18, 2016 / Notices Alaska (excluding waters in Southeastern Alaska and waters north of a line between Gore Point to Cape Suckling [including the North Gulf Coast and Prince William Sound])’’ The complete application is given in DOT docket MARAD–2016–0029 at https://www.regulations.gov. Interested parties may comment on the effect this action may have on U.S. vessel builders or businesses in the U.S. that use U.S.flag vessels. If MARAD determines, in accordance with 46 U.S.C. 12121 and MARAD’s regulations at 46 CFR part 388, that the issuance of the waiver will have an unduly adverse effect on a U.S.vessel builder or a business that uses U.S.-flag vessels in that business, a waiver will not be granted. Comments should refer to the docket number of this notice and the vessel name in order for MARAD to properly consider the comments. Comments should also state the commenter’s interest in the waiver application, and address the waiver criteria given in § 388.4 of MARAD’s regulations at 46 CFR part 388. Privacy Act Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT’s complete Privacy Act Statement in the Federal Register published on April 11, 2000 (Volume 65, Number 70; Pages 19477–78). By Order of the Maritime Administrator. Dated: March 8, 2016. T. Mitchell Hudson, Jr., Secretary, Maritime Administration. [FR Doc. 2016–06101 Filed 3–17–16; 8:45 am] BILLING CODE 4910–81–P DEPARTMENT OF TRANSPORTATION Maritime Administration [Docket No. MARAD–2016–0026] Requested Administrative Waiver of the Coastwise Trade Laws: Vessel BLACKBIRD X; Invitation for Public Comments Maritime Administration, Department of Transportation. ACTION: Notice. asabaliauskas on DSK3SPTVN1PROD with NOTICES AGENCY: As authorized by 46 U.S.C. 12121, the Secretary of Transportation, as represented by the Maritime Administration (MARAD), is authorized to grant waivers of the U.S.-build requirement of the coastwise laws under SUMMARY: VerDate Sep<11>2014 19:50 Mar 17, 2016 Jkt 238001 certain circumstances. A request for such a waiver has been received by MARAD. The vessel, and a brief description of the proposed service, is listed below. DATES: Submit comments on or before April 18, 2016. ADDRESSES: Comments should refer to docket number MARAD–2016–0026. Written comments may be submitted by hand or by mail to the Docket Clerk, U.S. Department of Transportation, Docket Operations, M–30, West Building Ground Floor, Room W12–140, 1200 New Jersey Avenue SE., Washington, DC 20590. You may also send comments electronically via the Internet at https://www.regulations.gov. All comments will become part of this docket and will be available for inspection and copying at the above address between 10 a.m. and 5 p.m., E.T., Monday through Friday, except federal holidays. An electronic version of this document and all documents entered into this docket is available on the World Wide Web at https:// www.regulations.gov. FOR FURTHER INFORMATION CONTACT: Bianca Carr, U.S. Department of Transportation, Maritime Administration, 1200 New Jersey Avenue SE., Room W23–453, Washington, DC 20590. Telephone 202– 366–9309, Email Bianca.carr@dot.gov. SUPPLEMENTARY INFORMATION: As described by the applicant the intended service of the vessel BLACKBIRD X is: Intended Commercial Use of Vessel: As a hovercraft charter business during Spring and Summer. If chartering includes sport fishing, the fish caught would NOT be sold commercially Geographic Region: ‘‘New York, Connecticut’’ The complete application is given in DOT docket MARAD–2016–0026 at https://www.regulations.gov. Interested parties may comment on the effect this action may have on U.S. vessel builders or businesses in the U.S. that use U.S.flag vessels. If MARAD determines, in accordance with 46 U.S.C. 12121 and MARAD’s regulations at 46 CFR part 388, that the issuance of the waiver will have an unduly adverse effect on a U.S.vessel builder or a business that uses U.S.-flag vessels in that business, a waiver will not be granted. Comments should refer to the docket number of this notice and the vessel name in order for MARAD to properly consider the comments. Comments should also state the commenter’s interest in the waiver application, and address the waiver criteria given in § 388.4 of MARAD’s regulations at 46 CFR part 388. PO 00000 Frm 00113 Fmt 4703 Sfmt 4703 Privacy Act Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT’s complete Privacy Act Statement in the Federal Register published on April 11, 2000 (Volume 65, Number 70; Pages 19477–78). By Order of the Maritime Administrator. Dated: March 8, 2016. T. Mitchell Hudson, Jr., Secretary, Maritime Administration. [FR Doc. 2016–06100 Filed 3–17–16; 8:45 am] BILLING CODE 4910–81–P DEPARTMENT OF TRANSPORTATION National Highway Traffic Safety Administration [Docket No. NHTSA–2016–0036] Guidelines for the Safe Deployment and Operation of Automated Vehicle Safety Technologies National Highway Traffic Safety Administration (NHTSA), Department of Transportation (DOT). ACTION: Announcement of public meeting. AGENCY: NHTSA is announcing a public meeting to seek input on planned guidelines for the safe deployment and operation of automated vehicles. The intent of the operational guidance is to encourage innovative and safe deployment of automated vehicle technologies. At this meeting, NHTSA is seeking public input on those aspects of automated vehicle (AV) systems that would benefit from operational guidelines. For example, of high importance to the Agency is information on the roadway scenarios and operational environments highly automated vehicles will need to address and the associated design and evaluation processes and methods needed to ensure that AV systems can detect and appropriately react to these scenarios such that a high level of safety is assured when these systems are deployed on US roadways. Also of interest would be input on aspects of automated vehicle technology that may not be suitable or ready for guidelines. For these areas, information would be useful on alternative approaches to assure safety. DATES: NHTSA will hold the public meeting on April 8, 2016, in SUMMARY: E:\FR\FM\18MRN1.SGM 18MRN1 asabaliauskas on DSK3SPTVN1PROD with NOTICES Federal Register / Vol. 81, No. 53 / Friday, March 18, 2016 / Notices Washington, DC. The meeting will start at 9:00 a.m. and continue until 4:00 p.m., local time. Check-in (through security) will begin at 8 a.m. (Note: A second public meeting will be held on the West Coast (California), and details for that meeting will be announced in a separate Federal Register (FR) Notice.) ADDRESSES: The meeting will be held at the U.S. Department of Transportation, West Building, Ground Floor Atrium, 1200 New Jersey Avenue SE., Washington, DC 20590. This facility is accessible to individuals with disabilities. The meeting will also be webcast live, and a link to the actual webcast will be available through https://www.nhtsa.gov/Research/ Crash+Avoidance/Automated+Vehicles. FOR FURTHER INFORMATION CONTACT: If you have questions about the public meeting, please contact us at av_info_ nhtsa@dot.gov. Registration is necessary for all attendees. Attendees should register at https://goo.gl/forms/l8z3HVM6hw by April 1, 2016. Please provide name and affiliation, indicate if you wish to offer technical remarks, and please indicate whether you require accommodations such as a sign language interpreter. Space is limited, so advanced registration is highly encouraged. Although attendees will be given the opportunity to offer technical remarks, there will not be time for attendees to make audio-visual presentations during the meeting. Note: We may not be able to accommodate all attendees who wish to make oral remarks. Should it be necessary to cancel the meeting due to inclement weather or other emergency, NHTSA will take all available measures to notify registered participants. NHTSA will conduct the public meeting informally, and technical rules of evidence will not apply. We will arrange for a written transcript of the meeting and keep the official record open for 30 days after the meeting to allow submission of supplemental information. You may make arrangements for copies of the transcripts directly with the court reporter, and the transcript will also be posted in the docket when it becomes available. Written Comments: Written statements and supporting information submitted during the comment period will be considered with the same weight as oral comments and supporting information presented at the public meeting. Please submit all written comments no later than May 9, 2016, by any of the following methods: • Federal Rulemaking Portal: Go to https://www.regulations.gov. Follow the VerDate Sep<11>2014 19:50 Mar 17, 2016 Jkt 238001 online instructions for submitting comments. • Mail: Docket Management Facility: U.S. Department of Transportation, 1200 New Jersey Avenue SE., West Building Ground Floor, Room W12–140, Washington, DC 20590–0001. • Hand Delivery or Courier: 1200 New Jersey Avenue SE., West Building Ground Floor, Room W12–140, Washington, DC 20590–0001, between 9 a.m. and 5 p.m. ET, Monday through Friday, except Federal Holidays. • Fax: 202–366–1767. Instructions: All submissions must include the agency name and docket number. Note that all comments received will be posted without change to https://www.regulations.gov, including any personal information provided. Please see the Privacy Act discussion below. Docket: For access to the docket go to https://www.regulations.gov at any time or to 1200 New Jersey Avenue SE., West Building, Ground Floor, Room W12– 140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal Holidays. Telephone: 202–366–9826. Privacy Act: Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT’s complete Privacy Act Statement in the Federal Register published on April 11, 2000 (Volume 65, Number 70; Pages 19477–78), or you may visit https://www.regulations.gov/ privacy.html. Confidential Business Information: If you wish to submit any information under a claim of confidentiality, you should submit three copies of your complete submission, including the information you claim to be confidential business information to the Chief Counsel, NHTSA, at the address given under FOR FURTHER INFORMATION CONTACT. In addition, you should submit two copies, from which you have deleted the claimed confidential business information, to Docket Management at the address given above. When you send a comment containing information claimed to be confidential business information, you should submit a cover letter setting forth the information specified in our confidential business information regulation (49 CFR part 512). SUPPLEMENTARY INFORMATION: Background DOT recently announced a series of actions to remove potential roadblocks PO 00000 Frm 00114 Fmt 4703 Sfmt 4703 14935 to the integration of innovative automotive technology. As part of this effort, several milestones were announced for 2016, including development of guidance on the safe deployment and operation of automated vehicles. Draft Agenda 08:00–09:00—Arrival/Check-In 09:00–12:00—Morning Public Meeting Session 12:00–13:00—Lunch Break 13:00–16:00—Afternoon Public Meeting Session 16:00–Adjourn Public Meeting Topics NHTSA is seeking input on the following topics during the morning and afternoon sessions of the meeting. 1. Evaluation and testing of scenarios the AV system should detect and correctly operate in: Within the AV system’s operating envelope, consider how to identify the scenarios that could be encountered by the AV system (e.g., behavioral competencies/normal driving, pre-crash scenarios, etc.) and what design and evaluation (testing) processes and methods are needed to ensure that the vehicle can detect and appropriately react to these scenarios. Consider whether third party testing is appropriate for validating test results. 2. Detection and communication of operational boundaries: If there are limitations on where AV technology will operate—what methods should the AV technology use to sense when it is reaching the operational domain limit and how should that be communicated to the driver? 3. Environmental operation and sensing: Consider what environmental conditions AV systems will likely operate in. For environmental conditions in which AV systems are not designed to operate, discuss methods used to detect these conditions. 4. Driver transitioning to/from AV operating mode: For AV systems that rely on transferring vehicle operation back to the driver, discuss approaches to (a) ensuring safe transitioning back to a fully capable non-impaired driver (e.g., geo-fencing, adverse weather) and (b) how non optimal driver behavior will be addressed by the AV system (e.g., decision errors, erratic behavior, driver impairment.) 5. Data: Consider data recording capabilities of system(s) necessary to monitor the correct operation of the AV system, and what are appropriate triggers (crash, near crash, etc.) to determine system operational status or possible malfunction of the system. Also consider how recorded data could be E:\FR\FM\18MRN1.SGM 18MRN1 14936 Federal Register / Vol. 81, No. 53 / Friday, March 18, 2016 / Notices accessed and by whom. During the testing phase, consider what data should be made public for further analysis and understanding. 6. Crash avoidance capability: Consider the capabilities of AV systems with respect to detecting roadway hazards (other vehicles, pedestrians, animals, etc.) such that common crash scenarios involving these hazards (control loss, crossing paths head-on, etc.) can be detected and either avoided or mitigated. 7. Electronics systems safety: Consider methods and potential documentation that could be produced with respect to functional safety and cybersecurity. 8. Non-passenger AVs: Consider differences between AVs designed for delivery of goods and products that are not intended to have a human operator or potentially even human passengers. 9. Aspects of AV technology that may not be suitable or ready for guidelines. For these areas, information would be useful on alternative approaches to assure safety. 10. Identification of industry voluntary standards, best practices, etc., related to automated vehicle operation. 11. Information AV’s may need to communicate to pedestrians and other vehicles (manual or automated) just as a driver would. Consider situations such as pedestrians crossing a travel lane in a parking lot and how this communication should be accomplished. 12. Other topics needed for operational guidance: Other topics that would be beneficial to address in an operational guidance document to facilitate innovation and safe deployment of these systems on public roadways. Issued in Washington, DC, under authority delegated by 49 CFR 1.95. Nathaniel Beuse, Associate Administrator for Vehicle Safety Research. [FR Doc. 2016–06143 Filed 3–17–16; 8:45 am] been in process for 180 days or more. The reason(s) for delay and the expected completion date for action on each application is provided in association with each identified application. FOR FURTHER INFORMATION CONTACT: Ryan Paquet, Director, Office of Hazardous Materials Special Permits and Approvals, Pipeline and Hazardous Materials Safety Administration, U.S. Department of Transportation, East Building, PHH–30, 1200 New Jersey Avenue SE., Washington, DC 20590– 0001, (202) 366–4535. Key to ‘‘Reason for Delay’’ BILLING CODE 4910–59–P DEPARTMENT OF TRANSPORTATION Pipeline and Hazardous Materials Safety Administration Hazardous Materials: Delayed Applications 1. Awaiting additional information from applicant 2. Extensive public comment under review 3. Application is technically complex and is of significant impact or precedent-setting and requires extensive analysis 4. Staff review delayed by other priority issues or volume of special permit applications Office of Hazardous Materials Safety, Pipeline and Hazardous Materials Safety Administration (PHMSA), DOT. ACTION: List of application delayed more than 180 days. Meaning of Application Number Suffixes In accordance with the requirements of 49 U.S.C. 5117(c), PHMSA is publishing the following list of special permit applications that have Issued in Washington, DC, on March 10, 2016. Donald Burger, Chief, General Approvals and Permits. AGENCY: SUMMARY: Application No. N—New application M—Modification request R—Renewal Request P—Party To Exemption Request Reason for delay Applicant Estimated date of completion Modification to Special Permits 16412–M ........... 15628–M ........... 15610–M ........... 15537–M ........... 7607–M ............. 16035–M ........... 14437–M ........... Nantong CMC Tank Equipment Co. Ltd., Jiangsu, Province ................................................... Chemours Company FC, LLC, Wilmington, DE ....................................................................... TechKnowServ Corp., State College, PA ................................................................................. Alaska Pacific Powder Company, Watkins, CO ....................................................................... Thermo Fisher Scientific, Franklin, MA .................................................................................... LCF Systems, Inc., Scottsdale, AZ .......................................................................................... Columbiana Boiler Company (CBCo), LLC, Columbiana, OH ................................................. 4 4 4 4 4 4 4 03–31–2016 03–31–2016 03–31–2016 04–15–2016 03–31–2016 04–30–2016 02–15–2016 3 3 4 4 4 3 4 4 4 02–29–2016 03–31–2016 03–15–2016 03–31–2016 03–15–2016 03–31–2016 04–15–2016 04–30–2016 04–30–2016 4 03–31–2016 New Special Permit Applications asabaliauskas on DSK3SPTVN1PROD with NOTICES 15767–N 16001–N 16477–N 16495–N 16524–N 16463–N 16571–N 16559–N 16560–N ........... ........... ........... ........... ........... ........... ........... ........... ........... Union Pacific Railroad Company, Omaha, NE ........................................................................ VELTEK ASSOCIATES, INC., Malvern, PA ............................................................................. Hydroid, Inc., Pocasset, MA ..................................................................................................... TransRail Innovation, Inc., Calgary .......................................................................................... Quantum Fuel Systems Technologies Worldwide, Inc., Lake Forest, CA ............................... Salco Products, Lemont, IL ...................................................................................................... Chevron USA Inc., San Ramon, CA ........................................................................................ HTEC Hydrogen Technology & Energy Corporation, North Vancouver, BC; Canada ............ LightSail Energy, Inc., Berkeley, CA ........................................................................................ Party to Special Permits Application 16279–P ........... AEG Environmental Products & Services, Inc.; Westminster, MD .......................................... [FR Doc. 2016–06055 Filed 3–17–16; 8:45 am] BILLING CODE 4910–60–M VerDate Sep<11>2014 19:50 Mar 17, 2016 Jkt 238001 PO 00000 Frm 00115 Fmt 4703 Sfmt 9990 E:\FR\FM\18MRN1.SGM 18MRN1

Agencies

[Federal Register Volume 81, Number 53 (Friday, March 18, 2016)]
[Notices]
[Pages 14934-14936]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2016-06143]


-----------------------------------------------------------------------

DEPARTMENT OF TRANSPORTATION

National Highway Traffic Safety Administration

[Docket No. NHTSA-2016-0036]


Guidelines for the Safe Deployment and Operation of Automated 
Vehicle Safety Technologies

AGENCY: National Highway Traffic Safety Administration (NHTSA), 
Department of Transportation (DOT).

ACTION: Announcement of public meeting.

-----------------------------------------------------------------------

SUMMARY: NHTSA is announcing a public meeting to seek input on planned 
guidelines for the safe deployment and operation of automated vehicles. 
The intent of the operational guidance is to encourage innovative and 
safe deployment of automated vehicle technologies.
    At this meeting, NHTSA is seeking public input on those aspects of 
automated vehicle (AV) systems that would benefit from operational 
guidelines. For example, of high importance to the Agency is 
information on the roadway scenarios and operational environments 
highly automated vehicles will need to address and the associated 
design and evaluation processes and methods needed to ensure that AV 
systems can detect and appropriately react to these scenarios such that 
a high level of safety is assured when these systems are deployed on US 
roadways.
    Also of interest would be input on aspects of automated vehicle 
technology that may not be suitable or ready for guidelines. For these 
areas, information would be useful on alternative approaches to assure 
safety.

DATES: NHTSA will hold the public meeting on April 8, 2016, in

[[Page 14935]]

Washington, DC. The meeting will start at 9:00 a.m. and continue until 
4:00 p.m., local time. Check-in (through security) will begin at 8 a.m. 
(Note: A second public meeting will be held on the West Coast 
(California), and details for that meeting will be announced in a 
separate Federal Register (FR) Notice.)

ADDRESSES: The meeting will be held at the U.S. Department of 
Transportation, West Building, Ground Floor Atrium, 1200 New Jersey 
Avenue SE., Washington, DC 20590. This facility is accessible to 
individuals with disabilities. The meeting will also be webcast live, 
and a link to the actual webcast will be available through https://www.nhtsa.gov/Research/Crash+Avoidance/Automated+Vehicles.

FOR FURTHER INFORMATION CONTACT: If you have questions about the public 
meeting, please contact us at av_info_nhtsa@dot.gov.
    Registration is necessary for all attendees. Attendees should 
register at https://goo.gl/forms/l8z3HVM6hw by April 1, 2016. Please 
provide name and affiliation, indicate if you wish to offer technical 
remarks, and please indicate whether you require accommodations such as 
a sign language interpreter. Space is limited, so advanced registration 
is highly encouraged.
    Although attendees will be given the opportunity to offer technical 
remarks, there will not be time for attendees to make audio-visual 
presentations during the meeting. Note: We may not be able to 
accommodate all attendees who wish to make oral remarks. Should it be 
necessary to cancel the meeting due to inclement weather or other 
emergency, NHTSA will take all available measures to notify registered 
participants.
    NHTSA will conduct the public meeting informally, and technical 
rules of evidence will not apply. We will arrange for a written 
transcript of the meeting and keep the official record open for 30 days 
after the meeting to allow submission of supplemental information. You 
may make arrangements for copies of the transcripts directly with the 
court reporter, and the transcript will also be posted in the docket 
when it becomes available.
    Written Comments: Written statements and supporting information 
submitted during the comment period will be considered with the same 
weight as oral comments and supporting information presented at the 
public meeting. Please submit all written comments no later than May 9, 
2016, by any of the following methods:
     Federal Rulemaking Portal: Go to https://www.regulations.gov. Follow the online instructions for submitting 
comments.
     Mail: Docket Management Facility: U.S. Department of 
Transportation, 1200 New Jersey Avenue SE., West Building Ground Floor, 
Room W12-140, Washington, DC 20590-0001.
     Hand Delivery or Courier: 1200 New Jersey Avenue SE., West 
Building Ground Floor, Room W12-140, Washington, DC 20590-0001, between 
9 a.m. and 5 p.m. ET, Monday through Friday, except Federal Holidays.
     Fax: 202-366-1767.
    Instructions: All submissions must include the agency name and 
docket number. Note that all comments received will be posted without 
change to https://www.regulations.gov, including any personal 
information provided. Please see the Privacy Act discussion below.
    Docket: For access to the docket go to https://www.regulations.gov 
at any time or to 1200 New Jersey Avenue SE., West Building, Ground 
Floor, Room W12-140, Washington, DC 20590, between 9 a.m. and 5 p.m., 
Monday through Friday, except Federal Holidays. Telephone: 202-366-
9826.
    Privacy Act: Anyone is able to search the electronic form of all 
comments received into any of our dockets by the name of the individual 
submitting the comment (or signing the comment, if submitted on behalf 
of an association, business, labor union, etc.). You may review DOT's 
complete Privacy Act Statement in the Federal Register published on 
April 11, 2000 (Volume 65, Number 70; Pages 19477-78), or you may visit 
https://www.regulations.gov/privacy.html.
    Confidential Business Information: If you wish to submit any 
information under a claim of confidentiality, you should submit three 
copies of your complete submission, including the information you claim 
to be confidential business information to the Chief Counsel, NHTSA, at 
the address given under FOR FURTHER INFORMATION CONTACT. In addition, 
you should submit two copies, from which you have deleted the claimed 
confidential business information, to Docket Management at the address 
given above. When you send a comment containing information claimed to 
be confidential business information, you should submit a cover letter 
setting forth the information specified in our confidential business 
information regulation (49 CFR part 512).

SUPPLEMENTARY INFORMATION:

Background

    DOT recently announced a series of actions to remove potential 
roadblocks to the integration of innovative automotive technology. As 
part of this effort, several milestones were announced for 2016, 
including development of guidance on the safe deployment and operation 
of automated vehicles.

Draft Agenda

08:00-09:00--Arrival/Check-In
09:00-12:00--Morning Public Meeting Session
12:00-13:00--Lunch Break
13:00-16:00--Afternoon Public Meeting Session
16:00-Adjourn

Public Meeting Topics

    NHTSA is seeking input on the following topics during the morning 
and afternoon sessions of the meeting.
    1. Evaluation and testing of scenarios the AV system should detect 
and correctly operate in: Within the AV system's operating envelope, 
consider how to identify the scenarios that could be encountered by the 
AV system (e.g., behavioral competencies/normal driving, pre-crash 
scenarios, etc.) and what design and evaluation (testing) processes and 
methods are needed to ensure that the vehicle can detect and 
appropriately react to these scenarios. Consider whether third party 
testing is appropriate for validating test results.
    2. Detection and communication of operational boundaries: If there 
are limitations on where AV technology will operate--what methods 
should the AV technology use to sense when it is reaching the 
operational domain limit and how should that be communicated to the 
driver?
    3. Environmental operation and sensing: Consider what environmental 
conditions AV systems will likely operate in. For environmental 
conditions in which AV systems are not designed to operate, discuss 
methods used to detect these conditions.
    4. Driver transitioning to/from AV operating mode: For AV systems 
that rely on transferring vehicle operation back to the driver, discuss 
approaches to (a) ensuring safe transitioning back to a fully capable 
non-impaired driver (e.g., geo-fencing, adverse weather) and (b) how 
non optimal driver behavior will be addressed by the AV system (e.g., 
decision errors, erratic behavior, driver impairment.)
    5. Data: Consider data recording capabilities of system(s) 
necessary to monitor the correct operation of the AV system, and what 
are appropriate triggers (crash, near crash, etc.) to determine system 
operational status or possible malfunction of the system. Also consider 
how recorded data could be

[[Page 14936]]

accessed and by whom. During the testing phase, consider what data 
should be made public for further analysis and understanding.
    6. Crash avoidance capability: Consider the capabilities of AV 
systems with respect to detecting roadway hazards (other vehicles, 
pedestrians, animals, etc.) such that common crash scenarios involving 
these hazards (control loss, crossing paths head-on, etc.) can be 
detected and either avoided or mitigated.
    7. Electronics systems safety: Consider methods and potential 
documentation that could be produced with respect to functional safety 
and cybersecurity.
    8. Non-passenger AVs: Consider differences between AVs designed for 
delivery of goods and products that are not intended to have a human 
operator or potentially even human passengers.
    9. Aspects of AV technology that may not be suitable or ready for 
guidelines. For these areas, information would be useful on alternative 
approaches to assure safety.
    10. Identification of industry voluntary standards, best practices, 
etc., related to automated vehicle operation.
    11. Information AV's may need to communicate to pedestrians and 
other vehicles (manual or automated) just as a driver would. Consider 
situations such as pedestrians crossing a travel lane in a parking lot 
and how this communication should be accomplished.
    12. Other topics needed for operational guidance: Other topics that 
would be beneficial to address in an operational guidance document to 
facilitate innovation and safe deployment of these systems on public 
roadways.

    Issued in Washington, DC, under authority delegated by 49 CFR 
1.95.
Nathaniel Beuse,
Associate Administrator for Vehicle Safety Research.
[FR Doc. 2016-06143 Filed 3-17-16; 8:45 am]
 BILLING CODE 4910-59-P
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.