Aviation Rulemaking Advisory Committee-Continuing a Task, 27538-27539 [2012-11302]

Download as PDF 27538 Federal Register / Vol. 77, No. 91 / Thursday, May 10, 2012 / Notices AMENDMENTS TO PFC APPROVALS Amendment approved date Amendment No. city, State 11–11–C–01–RNO Reno, NV .............................................. 07–02–C–01–CLT ................................................................ Issued in Washington, DC, on May 3, 2012. Joe Hebert, Manager, Financial Analysis and Passenger Facility Charge Branch. [FR Doc. 2012–11231 Filed 5–9–12; 8:45 am] BILLING CODE 4910–13–M DEPARTMENT OF TRANSPORTATION Federal Aviation Administration Aviation Rulemaking Advisory Committee—Continuing a Task Federal Aviation Administration (FAA), DOT. ACTION: Notice of continuing a task assignment for the Aviation Rulemaking Advisory Committee (ARAC). AGENCY: The FAA assigned the Aviation Rulemaking Advisory Committee (ARAC) a continuing task to provide advice and recommendations to the FAA about implementing a process for prioritizing rulemaking projects. This task addresses, in part, one of the Department of Transportation’s Future of Aviation Advisory Committee (FAAC) recommendations. This notice informs the public of a continuing ARAC activity and does not solicit membership for the existing Rulemaking Prioritization Working Group (RPWG). FOR FURTHER INFORMATION CONTACT: Katherine Haley, Office of Rulemaking, Federal Aviation Administration, 800 Independence Avenue SW., Washington, DC 20591; telephone: 202– 493–5708, facsimile: 202–267–5075; email: Katherine.L.Haley@faa.gov. SUPPLEMENTARY INFORMATION: mstockstill on DSK4VPTVN1PROD with NOTICES SUMMARY: Background The FAA established ARAC to provide advice and recommendations to the FAA Administrator on the FAA’s rulemaking activities. ARAC’s objectives are to improve the development of the FAA’s regulations by providing information, advice, and recommendations related to aviation issues. In April 2011, the FAA tasked ARAC to provide advice and recommendations on developing a framework and methodologies to assist the FAA in assessing and sequencing potential VerDate Mar<15>2010 17:18 May 09, 2012 Jkt 226001 04/03/12 04/11/12 Original approved net PFC revenue $25,491,376 144,557,137 rulemaking projects.1 The FAA provided the RPWG with a set of issues to test the framework and methodologies. The RPWG conducted its task from June to December 2011 and submitted recommendations to ARAC on December 14, 2011. ARAC accepted the recommendations on December 16, 2011 and forwarded them to the FAA. The entire recommendation report can be found at: http://www.faa.gov/ regulations_policies/rulemaking/ committees/arac/. The March 2012 ARAC Executive Committee meeting included a discussion of continuing the task to further test the RPWG’s methodology. This notice advises the public that the FAA has assigned, and the ARAC Executive Committee has accepted, the task to test the methodology and to develop a report including recommendations explaining the results. The Task The FAA has tasked the RPWG to provide advice and recommendations to further test the recommended methodology. The RPWG is expected to develop a report containing recommended changes to the methodology. This report should document both majority and minority positions on the findings and the rationale for each position. Any disagreements should be documented, including the rationale for each position and the reasons for the disagreement. In developing its recommendations, the RPWG shall: 1. Review the RPWG Phase I Recommendation Report. 2. Test the methodology and the tools using a subset of completed rulemakings provided by the FAA. 3. Develop measurable scoring evaluation to evaluate projects against each other. 4. Evaluate the results of the test and refine the process and the tools accordingly. Schedule: The recommendations must be forwarded to the ARAC Executive Committee for review and approval no later than September 2012. The RPWG 1 FAA, Aviation Rulemaking Advisory Committee (ARAC)—New Task (76 FR 21936). PO 00000 Frm 00123 Fmt 4703 Sfmt 4703 Amended approved net PFC revenue $33,933,876 143,057,137 Original estimated charge exp. date 04/01/17 12/01/18 Amended estimated charge exp. date 07/01/18 12/01/18 may be asked to clarify the report between September and December 2012. ARAC Acceptance of Task The ARAC Executive Committee has accepted the continuing task using members of the existing RPWG. The RPWG serves as staff to ARAC and assists in the analysis of the assigned task. ARAC must review and approve the RPWG’s recommendations. If ARAC accepts the working group’s recommendations, it will send them to the FAA. Working Group Activity The RPWG must comply with the procedures adopted by ARAC. As part of the procedures, the RPWG must: 1. Recommend a work plan for completion of the task, including the rationale supporting such a plan, for consideration at the next ARAC Executive Committee meeting held following publication of this notice. 2. Provide a status report at each meeting of the ARAC Executive Committee. 3. Draft the recommendation report and required analyses and/or any other related materials or documents. 4. Present the final recommendations to the ARAC Executive Committee for review and approval. Participation in the Working Group The existing RPWG is comprised of technical experts having an interest in the assigned task. A working group member need not be a representative or a member of the full committee. All existing RPWG members who choose to participate in this task must actively participate by attending all meetings, and providing written comments when requested to do so. Each member must devote the resources necessary to support the working group in meeting any assigned deadlines. Each member must keep their management chain, and those they may represent, advised of working group activities and decisions to ensure the proposed technical solutions do not conflict with their sponsoring organization’s position when the subject is presented to ARAC for approval. Once the RPWG has begun deliberations, members will not be added or substituted without the E:\FR\FM\10MYN1.SGM 10MYN1 Federal Register / Vol. 77, No. 91 / Thursday, May 10, 2012 / Notices approval of the FAA and the Working Group Chair. The Secretary of Transportation determined the formation and use of ARAC is necessary and in the public interest in connection with the performance of duties imposed on the FAA by law. ARAC meetings are open to the public. However, RPWG meetings are not open to the public, except to the extent individuals with an interest and expertise are selected to participate. The FAA will make no public announcement of the RPWG meetings. Issued in Washington, DC, on May 3, 2012. Brenda D. Courtney, Acting Executive Director, Aviation Rulemaking Advisory Committee. [FR Doc. 2012–11302 Filed 5–9–12; 8:45 am] BILLING CODE 4910–13–P DEPARTMENT OF TRANSPORTATION Federal Railroad Administration [Docket Number FRA–2012–0020] mstockstill on DSK4VPTVN1PROD with NOTICES Petition for Waiver of Compliance In accordance with Part 211 of Title 49 Code of Federal Regulations (CFR), this document provides the public notice that by a document dated March 8, 2012, the Union Pacific Railroad (UP) has petitioned the Federal Railroad Administration (FRA) for a waiver of compliance from certain provisions of the Federal railroad safety regulations contained at 49 CFR Part 234. FRA assigned the petition Docket Number FRA–2012–0020. UP seeks a waiver from the portion of 49 CFR Section 234.223, Gate arm. Section 234.223 requires that ‘‘each gate arm shall start its downward motion not less than three seconds after flashing lights begin to operate * * *.’’ UP also requests that the normal position of the gate arm down and the flashing lights dark not be considered as an activation failure, partial activation, or a false activation under 49 CFR 234.5. This waiver petition is related to the Illinois high-speed passenger rail project on the route between Chicago, IL, and St. Louis, MO; on UP’s Joliet and Springfield Subdivisions. This route is owned and maintained by UP. Highspeed passenger operation will be conducted by the National Railroad Passenger Corporation (Amtrak) or another operator designated by the Illinois Department of Transportation (IDOT). At farm private crossings (also known as field access crossings), which are currently not protected by active VerDate Mar<15>2010 17:18 May 09, 2012 Jkt 226001 warning devices, IDOT has requested UP install active warning devices that operate differently than standard active warning devices. Currently, there are 24 field access crossings proposed for the installation of the nonconventional crossing warning system. At the field access crossings involved, the normal operation would require the gate arms to be in the lowered position with no flashing lights activated. Upon the train’s approach, the flashing lights and bells would then activate. To allow for the landowner to bring vehicles or farm equipment across the crossing, it would be necessary to unlock a pushbutton box and operate the pushbutton. The gate would then return to the upright position and operate as a conventional active warning system for either 8 hours, or if ‘‘reset,’’ via pushbutton within the box. If not manually reset to the gate arm down condition, at the end of 8 hours the gate arms would then return to the down position. A copy of the petition, as well as any written communications concerning the petition, is available for review online at www.regulations.gov and in person at the U.S. Department of Transportation’s (DOT) Docket Operations Facility, 1200 New Jersey Avenue SE., W12–140, Washington, DC 20590. The Docket Operations Facility is open from 9 a.m. to 5 p.m., Monday through Friday, except Federal holidays. Interested parties are invited to participate in these proceedings by submitting written views, data, or comments. FRA does not anticipate scheduling a public hearing in connection with these proceedings since the facts do not appear to warrant a hearing. If any interested party desires an opportunity for oral comment, they should notify FRA, in writing, before the end of the comment period and specify the basis for their request. All communications concerning these proceedings should identify the appropriate docket number and may be submitted by any of the following methods: • Web site: http:// www.regulations.gov. Follow the online instructions for submitting comments. • Fax: 202–493–2251. • Mail: Docket Operations Facility, U.S. Department of Transportation, 1200 New Jersey Avenue SE., W12–140, Washington, DC 20590. • Hand Delivery: 1200 New Jersey Avenue SE., Room W12–140, Washington, DC 20590, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. Communications received by June 25, 2012 will be considered by FRA before PO 00000 Frm 00124 Fmt 4703 Sfmt 4703 27539 final action is taken. Comments received after that date will be considered as far as practicable. Anyone is able to search the electronic form of any written communications and 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 online at http://www.dot.gov/ privacy.html. Issued in Washington, DC, on May 7, 2012. Ron Hynes, Acting Deputy Associate Administrator for Regulatory and Legislative Operations. [FR Doc. 2012–11337 Filed 5–9–12; 8:45 am] BILLING CODE 4910–06–P DEPARTMENT OF TRANSPORTATION National Highway Traffic Safety Administration Reports, Forms, and Recordkeeping Requirements; Agency Information Collection Activity Under OMB Review National Highway Traffic Safety Administration (NHTSA), DOT. ACTION: Notice. AGENCY: In compliance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.), this notice announces that the Information Collection Request (ICR) abstracted below has been forwarded to the Office of Management and Budget (OMB) for review and comment. The ICR describes the nature of the information collection and the expected burden. The Federal Register Notice with a 60-day comment period was published on November 16, 2011 (76 FR 71122–71123). DATES: Comments must be submitted on or before June 11, 2012. ADDRESSES: Send comments, within 30 days, to the Office of Information and Regulatory Affairs, Office of Management and Budget, 725 17th Street NW., Washington, DC 20503, Attention NHTSA Desk Officer. FOR FURTHER INFORMATION CONTACT: Jessica Cicchino, Ph.D., Contracting Officer’s Technical Representative, Office of Behavioral Safety Research (NTI–131), National Highway Traffic Safety Administration, 1200 New Jersey Ave. SE., W46–491, Washington, DC 20590. Dr. Cicchino’s phone number is 202–366–2752 and her email address is jessica.cicchino@dot.gov. SUMMARY: E:\FR\FM\10MYN1.SGM 10MYN1

Agencies

[Federal Register Volume 77, Number 91 (Thursday, May 10, 2012)]
[Notices]
[Pages 27538-27539]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: 2012-11302]


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

DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration


Aviation Rulemaking Advisory Committee--Continuing a Task

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Notice of continuing a task assignment for the Aviation 
Rulemaking Advisory Committee (ARAC).

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

SUMMARY: The FAA assigned the Aviation Rulemaking Advisory Committee 
(ARAC) a continuing task to provide advice and recommendations to the 
FAA about implementing a process for prioritizing rulemaking projects. 
This task addresses, in part, one of the Department of Transportation's 
Future of Aviation Advisory Committee (FAAC) recommendations. This 
notice informs the public of a continuing ARAC activity and does not 
solicit membership for the existing Rulemaking Prioritization Working 
Group (RPWG).

FOR FURTHER INFORMATION CONTACT: Katherine Haley, Office of Rulemaking, 
Federal Aviation Administration, 800 Independence Avenue SW., 
Washington, DC 20591; telephone: 202-493-5708, facsimile: 202-267-5075; 
email: Katherine.L.Haley@faa.gov.

SUPPLEMENTARY INFORMATION:

Background

    The FAA established ARAC to provide advice and recommendations to 
the FAA Administrator on the FAA's rulemaking activities. ARAC's 
objectives are to improve the development of the FAA's regulations by 
providing information, advice, and recommendations related to aviation 
issues.
    In April 2011, the FAA tasked ARAC to provide advice and 
recommendations on developing a framework and methodologies to assist 
the FAA in assessing and sequencing potential rulemaking projects.\1\ 
The FAA provided the RPWG with a set of issues to test the framework 
and methodologies. The RPWG conducted its task from June to December 
2011 and submitted recommendations to ARAC on December 14, 2011. ARAC 
accepted the recommendations on December 16, 2011 and forwarded them to 
the FAA. The entire recommendation report can be found at: http://www.faa.gov/regulations_policies/rulemaking/committees/arac/.
---------------------------------------------------------------------------

    \1\ FAA, Aviation Rulemaking Advisory Committee (ARAC)--New Task 
(76 FR 21936).
---------------------------------------------------------------------------

    The March 2012 ARAC Executive Committee meeting included a 
discussion of continuing the task to further test the RPWG's 
methodology. This notice advises the public that the FAA has assigned, 
and the ARAC Executive Committee has accepted, the task to test the 
methodology and to develop a report including recommendations 
explaining the results.

The Task

    The FAA has tasked the RPWG to provide advice and recommendations 
to further test the recommended methodology.
    The RPWG is expected to develop a report containing recommended 
changes to the methodology. This report should document both majority 
and minority positions on the findings and the rationale for each 
position. Any disagreements should be documented, including the 
rationale for each position and the reasons for the disagreement.
    In developing its recommendations, the RPWG shall:
    1. Review the RPWG Phase I Recommendation Report.
    2. Test the methodology and the tools using a subset of completed 
rulemakings provided by the FAA.
    3. Develop measurable scoring evaluation to evaluate projects 
against each other.
    4. Evaluate the results of the test and refine the process and the 
tools accordingly.
    Schedule: The recommendations must be forwarded to the ARAC 
Executive Committee for review and approval no later than September 
2012. The RPWG may be asked to clarify the report between September and 
December 2012.

ARAC Acceptance of Task

    The ARAC Executive Committee has accepted the continuing task using 
members of the existing RPWG. The RPWG serves as staff to ARAC and 
assists in the analysis of the assigned task. ARAC must review and 
approve the RPWG's recommendations. If ARAC accepts the working group's 
recommendations, it will send them to the FAA.

Working Group Activity

    The RPWG must comply with the procedures adopted by ARAC. As part 
of the procedures, the RPWG must:
    1. Recommend a work plan for completion of the task, including the 
rationale supporting such a plan, for consideration at the next ARAC 
Executive Committee meeting held following publication of this notice.
    2. Provide a status report at each meeting of the ARAC Executive 
Committee.
    3. Draft the recommendation report and required analyses and/or any 
other related materials or documents.
    4. Present the final recommendations to the ARAC Executive 
Committee for review and approval.

Participation in the Working Group

    The existing RPWG is comprised of technical experts having an 
interest in the assigned task. A working group member need not be a 
representative or a member of the full committee.
    All existing RPWG members who choose to participate in this task 
must actively participate by attending all meetings, and providing 
written comments when requested to do so. Each member must devote the 
resources necessary to support the working group in meeting any 
assigned deadlines. Each member must keep their management chain, and 
those they may represent, advised of working group activities and 
decisions to ensure the proposed technical solutions do not conflict 
with their sponsoring organization's position when the subject is 
presented to ARAC for approval. Once the RPWG has begun deliberations, 
members will not be added or substituted without the

[[Page 27539]]

approval of the FAA and the Working Group Chair.
    The Secretary of Transportation determined the formation and use of 
ARAC is necessary and in the public interest in connection with the 
performance of duties imposed on the FAA by law.
    ARAC meetings are open to the public. However, RPWG meetings are 
not open to the public, except to the extent individuals with an 
interest and expertise are selected to participate. The FAA will make 
no public announcement of the RPWG meetings.

    Issued in Washington, DC, on May 3, 2012.
Brenda D. Courtney,
Acting Executive Director, Aviation Rulemaking Advisory Committee.
[FR Doc. 2012-11302 Filed 5-9-12; 8:45 am]
BILLING CODE 4910-13-P