16902 Federal Register / Vol. 75, No. 63 / Friday, April 2, 2010 / Notices 

• 14h15 to 17h00: Split-up sessions. 

• ED201: Include transversal topics 

extracted from other parts; coordinate 

details with other parts. 

• ED202/203–SG2: Discussion of 

differences with SC216/SG2; identify 

specific terms and glossary concerns; 

establish common basis for 

collaboration or joint work. 

• ED204–SG4: Review the SOW of 

both groups, determine if full or partly 

joint work with one resulting document 

is possible, identify parts, that can’t be 

joint. 

Days 2 and 3 

• 09h00 to 17h00: Split-up sessions. 

• Continuation of work for all 

documents. 

Day 4 

• 09h00 to 13h00: Plenary Session: 

• 09:00 to 09:20: Review Status of 

ED201 session work—What has been 

added/modified? Which elements will 

be dealt with in 2010, which in a later 

issue? What is the status of the EFB 

analysis? 

• 09:20 to 10:00: Review Status of 

ED202/ED203–SG2 session work—What 

is the status of the documents? Is it 

reasonable to expect termination of 

ED202/DO–TBD work in 2010? 

• 10:00 to 10:30: Review Status of 

ED204–SG4 session work—Is the target 

audience clear and limited, for which 

the document is to be established? Are 

the expectations of the audience well 

understood? How will the work 

progress, fully joint, partly joint, 

coordinated w/two separate documents? 

• 10:30 to 11:00: Discussion of 

Glossary: Content and Publication 

(separate in ED210 or integrated). 

• 11:00 to 11:15: Break. 

• 11:15 to 11:30: Discuss 

collaboration and associated topics with 

other organisations (Arinc, DSWG, 

ICAO, etc.). 

• 11:30 to 12:00: Summarize the 

official Eurocae and RTCA release/ 

review processes in relation to the 

planned releases for this year/early 

next—verify publication schedule. 

• 12:00 to 12:30: Future meeting dates 

and locations; Expertise to be included; 

Action Item review. 

• 12:30 to 12:45: Wrap-up of Meeting, 

Agreement on Conclusions and Main 

Events, Main messages to be 

disseminated. 

Attendance is open to the interested 

public but limited to space availability. 

With the approval of the chairmen, 

members of the public may present oral 

statements at the meeting. Persons 

wishing to present statements or obtain 

information should contact the person 

listed in the FOR FURTHER INFORMATION

CONTACT section. Members of the public 

may present a written statement to the 

committee at any time. 

Issued in Washington, DC on March 29, 

2010. 

Meredith Gibbs, 

RTCA Advisory Committee. 

[FR Doc. 2010–7546 Filed 4–1–10; 8:45 am] 

BILLING CODE 4910–13–P 

DEPARTMENT OF TRANSPORTATION 

Federal Aviation Administration 

Aviation Rulemaking Advisory 

Committee; Transport Airplane and 

Engine Issue Area—New Task 

AGENCY: Federal Aviation 

Administration (FAA), DOT. 

ACTION: Notice of new task assignment 

for the Aviation Rulemaking Advisory 

Committee (ARAC). 

SUMMARY: The FAA assigned the 

Aviation Rulemaking Advisory 

Committee (ARAC) a new task to 

identify and develop recommendations 

on additional requirements for low 

speed alerting in new transport category 

airplanes. This task is the first phase of 

an overall effort to examine new 

standards, as well as possible retrofit 

standards. This notice is to inform the 

public of this ARAC activity. 

FOR FURTHER INFORMATION CONTACT: Joe 

Jacobsen, Airplane & Flight Crew 

Interface Branch, ANM–111, Transport 

Airplane Directorate, Federal Aviation 

Administration, 1601 Lind Ave SW, 

Renton, Washington, 98057; telephone 

(425) 227–2011, facsimile (425) 227– 

1149; e-mail joe.jacobsen@faa.gov. 

SUPPLEMENTARY INFORMATION: 

Background 

The FAA established ARAC to 

provide advice and recommendations to 

the FAA Administrator on the FAA’s 

rulemaking activities with respect to 

aviation-related issues. With respect to 

low speed alerting, the FAA previously 

revised regulations in the area of flight 

guidance (autopilot) and performance 

and handling qualities in icing 

conditions to improve transport airplane 

standards for low speed protection (in 

the case of icing, stall warning standards 

were enhanced). However, as a result of 

several recent loss-of-control accidents 

and incidents, the FAA has identified a 

need for additional low speed 

safeguards, in addition to the regulatory 

actions that have already been taken. 

The committee will address the first 

task under the Transport Airplane and 

Engine Issues, under the existing 

Avionics Systems Harmonization 

Working Group. 

The Task 

ARAC is initially tasked with 

providing information that will be used 

to develop standards and guidance 

material for low speed alerting systems. 

This information may result in 

standards that complement existing stall 

warning requirements. The working 

group will be expected to provide a 

report that addresses the following low 

speed alerting technical questions, 

relative to new aircraft designs (Phase 1 

task—new Part 25 standards), and 

provides the rationale for their 

responses. If there is disagreement 

within the working group, those items 

should be documented, including the 

rationale from each party and the 

reasons for the disagreement. 

• How much time is needed to alert 

the crew in order to avoid stall warning 

or excessive deviation below the 

intended operating speed? 

• What would make the alerting 

instantly recognizable, clear, and 

unambiguous to the flightcrew? 

• How could nuisance alerts be 

minimized? 

• Could the alerting operate under all 

operating conditions, configurations, 

and phases of flight, including icing 

conditions? 

• Could the alerting operate during 

manual and autoflight? 

• Could the system reliability be 

made consistent with existing 

regulations and guidance for stall 

warning systems? 

• Are there any regulations or 

guidance material that might conflict 

with new standards? 

• What recommended guidance 

material is needed? 

• After reviewing airworthiness, 

safety, cost, and other relevant factors, 

including recent certification and fleet 

experience, are there any additional 

considerations that should be taken into 

account? 

• Is coordination necessary with 

other harmonization working groups 

(e.g., Human Factors)? (if yes, 

coordinate and report on that 

coordination) 

The working group will be also be 

expected to provide a report that 

addresses the following low speed 

alerting technical questions, relative to 

existing aircraft designs (as a lead-in to 

the Phase 2 task—retrofit standards), 

and provides the rationale for their 

responses. If there is disagreement 

within the working group, those items 

should be documented, including the 

rationale from each party and the 

reasons for the disagreement. 

mstockstill on DSKH9S0YB1PROD with NOTICES

Federal Register / Vol. 75, No. 63 / Friday, April 2, 2010 / Notices 16903 

• How timely is the airplane in 

alerting the crew of flight below the 

intended operating speed? How timely 

relative to stall warning? 

• Is alerting instantly recognizable, 

clear, and unambiguous to the 

flightcrew? 

• How are nuisance alerts 

minimized? 

• Does the alerting operate under all 

operating conditions, configurations, 

and phases of flight, including icing 

conditions? 

• Does the alerting operate during 

manual and autoflight? 

• After reviewing airworthiness, 

safety, cost, and other relevant factors, 

including recent certification and fleet 

experience, are there any additional 

considerations that should be taken into 

account? 

• Is coordination necessary with 

other harmonization working groups 

(e.g., Human Factors)? 

• If improvements are needed for low 

speed alerting in the existing fleet, 

should the FAA adopt a design approval 

holder (part 26) requirement to mandate 

development of design changes, or 

would an operational rule be sufficient? 

In responding, the working group 

should address the factors set forth in 

‘‘FAA Policy Statement: Safety—A 

Shared Responsibility—New Direction 

for Addressing Airworthiness Issues for 

Transport Airplanes’’ (70 FR 40166, July 

12, 2005). 

The ARAC working group should 

provide information that could lead to 

standards for low speed alerting that can 

be satisfied with practical design 

approaches. 

Schedule 

The required completion date is 9 

months after the FAA publishes the task 

in the Federal Register. 

ARAC Acceptance of Task 

ARAC accepted the task and assigned 

it to the existing Avionics Systems 

Harmonization Working Group in the 

Transport Airplane and Engine Issue 

Area. The working group serves as staff 

to ARAC and assists in the analysis of 

assigned tasks. ARAC must review and 

approve the working group’s 

recommendations. If ARAC accepts the 

working group’s recommendations, it 

will forward them to the FAA. 

Working Group Activity 

The Avionics Systems Harmonization 

Working Group must comply with the 

procedures adopted by ARAC. As part 

of the procedures, the working group 

must: 

1. Recommend a work plan for 

completion of the task, including the 

rationale supporting such a plan for 

consideration at the next meeting of the 

ARAC on Transport Airplane and 

Engine Issues held following 

publication of this notice. 

2. Give a detailed conceptual 

presentation of the proposed 

recommendations prior to proceeding 

with the work stated in item 3 below. 

3. Draft the appropriate documents 

and required analyses and/or any other 

related materials or documents. 

4. Provide a status report at each 

meeting of the ARAC held to consider 

Transport Airplane and Engine Issues. 

Participation in the Working Group 

The Avionics Systems Harmonization 

Working Group is composed 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. 

If you have expertise in the subject 

matter and wish to become a member of 

the working group, write to the person 

listed under the caption FOR FURTHER

INFORMATION CONTACT expressing that 

desire. Describe your interest in the task 

and state the expertise you would bring 

to the working group. We must receive 

all requests by May 3, 2010. The 

assistant chair, the assistant executive 

director, and the working group cochairs will review the requests and 

advise you whether or not your request 

is approved. 

If you are chosen for membership on 

the working group, you must represent 

your aviation community segment and 

actively participate in the working 

group by attending all meetings and 

providing written comments when 

requested to do so. You must devote the 

resources necessary to support the 

working group in meeting any assigned 

deadlines. You must keep your 

management chain and those you may 

represent advised of working group 

activities and decisions to ensure that 

the proposed technical solutions do not 

conflict with your sponsoring 

organization’s position when the subject 

being negotiated is presented to ARAC 

for approval. Once the working group 

has begun deliberations, members will 

not be added or substituted without the 

approval of the assistant chair, the 

assistant executive director, and the 

working group co-chairs. 

The Secretary of Transportation 

determined that the formation and use 

of the ARAC is necessary and in the 

public interest in connection with the 

performance of duties imposed on the 

FAA by law. 

Meetings of the ARAC are open to the 

public. Meetings of the Avionics 

Systems Harmonization Working Group 

will not be 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 working group 

meetings. 

Issued in Washington, DC, on March 29, 

2010. 

Pamela Hamilton-Powell, 

Executive Director, Aviation Rulemaking 

Advisory Committee. 

[FR Doc. 2010–7402 Filed 4–1–10; 8:45 am] 

BILLING CODE 4910–13–P 

DEPARTMENT OF TRANSPORTATION 

Federal Aviation Administration 

Public Notice for Waiver of 

Aeronautical Land-Use Assurance 

Dayton-Wright Brothers Airport; 

Dayton, OH 

AGENCY: Federal Aviation 

Administration, DOT. 

ACTION: Notice of intent of waiver with 

respect to land. 

SUMMARY: The Federal Aviation 

Administration (FAA) is considering a 

proposal to change a portion of the 

airport from aeronautical use to nonaeronautical use and to authorize the 

release of 10.829 acres of airport 

property for permanent public roadway 

use. The land consists of portions of 4 

original airport acquired parcels. These 

parcels were acquired under grants 5– 

39–0030–01, 5–39–0030–02, 5–39– 

0030–03, 5–39–0030–04, 5–39–0030–05, 

and 3–39–0030–01. There are no 

impacts to the airport by allowing the 

City of Dayton to sell the property. The 

land is not needed for aeronautical use. 

Approval does not constitute a 

commitment by the FAA to financially 

assist in the sale of the subject airport 

property nor a determination of 

eligibility for grant-in-aid funding from 

the FAA. The disposition of proceeds 

from the sale of the airport property will 

be in accordance with FAA’s Policy and 

Procedures Concerning the Use of 

Airport Revenue, published in the 

Federal Register on February 16, 1999. 

In accordance with section 47107(h) of 

title 49, United States Code, this notice 

is required to be published in the 

Federal Register 30 days before 

modifying the land-use assurance that 

requires the property to be used for an 

aeronautical purpose. 

DATES: Comments must be received on 

or before May 3, 2010. 

ADDRESSES: Written comments on the 

Sponsor’s request must be delivered or 

mailed to: Irene R. Porter, Program 

Manager, Detroit Airports District 

mstockstill on DSKH9S0YB1PROD with NOTICES