FAA PowerPoint from UAS Action Summit – Looking to the Future

Federal AviationAdministration

UAS Action SummitUAS 2020 – Looking to the Future

June 2, 2011

Dean Fulmer, Acting Manager, Unmanned Aircraft Systems Group, AJV-13

Richard Prosek, Manager,

Unmanned Aircraft Program Office, AFS-407

Federal AviationAdministration 2

UAS Action Summit: UAS 2020 – Looking to the Future

Grand Forks, ND

June 2, 2011

Overview

• Recent Changes at FAA on Unmanned Aircraft Systems (UAS)

• Updates:– FAA UAS Activities– small UAS (sUAS) Rule– FAA Reauthorization Bills

• Test Range Considerations



Grand Forks, ND

June 2, 2011

UAS Offices at FAA (changes/new)

• Aviation Safety (AVS)– Unmanned Aircraft Program Office, AFS-407– Next Generation Air Transportation System (NextGen) branches

in the 8 Flight Standards Service regions• Air Traffic Organization (ATO)

– UAS Group, AJV-13– Service Areas (Eastern, Central, Western)

• Other Stakeholders– NextGen and Operations Planning – Now under the

Deputy Administrator (ADA)– Research & Technology Development, AJP-6

Federal Aviation Administration

05/02/2011

J. Randolph BabbittAOA-1

Administrator

Paula NouragasManager, AJP-65

Engineering Development Services Group

Rick DucharmeSenior Vice President, AJN-O

OperationsJohn Allen

Director, AFS-1Flight Standards Service

Leslie SmithManager, AFS-400

Flight Technologies and Procedures Division

Victoria CoxSenior Vice President, AJP-O

NextGen and Operations Planning

Dean FulmerActing Manager, AJV-13

Unmanned Aircraft Systems Group

Paul FontaineDirector, AJP-6

Office of Aviation Research

Elizabeth Lynn RayVice President, AJV-O

Mission Support Services

Richard ProsekManager, AFS-407

Unmanned Aircraft Program Office

Dennis RobertsDirector, AJV-1

Airspace Services

Offices Co-Located withMilitary and Other

Government UAS Liaisons

Michael HuertaADA-1

Deputy Administrator

Peggy GilliganAssociate Administrator, AVS-1

Aviation Safety

David Grizzle Acting Chief Operating Officer, AJO-O

Air Traffic Organization



Grand Forks, ND

June 2, 2011

Evolution of UAS NAS Integration

• Accommodation– Certificates of Waiver or Authorization (COAs) for Public

Operators• 264 active COAs / 85 Proponents / 82 Aircraft

– Special Airworthiness Certificate – Experimental Category (SAC-EC) for Civil

• 88 issued since 2005• Currently 15 active on 14 different aircraft types

– AC 91-57 (Model Aircraft Operating Standards) for modelers

• Integration into the National Airspace System (NAS)• Integration into the NextGen NAS



Grand Forks, ND

June 2, 2011

Highlights of Past Year (sampling)

• Dedication of the NextGen Integration and Evaluation Capability (NIEC) (Tech Center) – 6/10

• Revision to FAA Order 8130.34A (Experimentals: added optionally-piloted aircraft) – 10/10

• Federal Public NAS Integration Plan submitted to Congress in response to National Defense Authorization Act (NDAA) requirements – 10/10

• Sense and Avoid Workshop II Kickoff – 11/10



Grand Forks, ND

June 2, 2011

Highlights of Past Year Continued(sampling)

• Traffic Collision Avoidance System (TCAS) on UAS Study – Completed 3/11

• Start up of the first Ground-based Sense and Avoid (GBSAA) system at El Mirage, CA – 4/11

• small UAS Rule Final Team Concurrence –5/11



Grand Forks, ND

June 2, 2011

Current Work• Update to Interim Guidance Material 08-01• Stand up of the UAS Aviation Rulemaking

Committee (ARC)– Mechanism to bring in input from industry

along with the other Government partners– First product will be an update to the FAA

Civil/Public UAS Roadmap for UAS NAS Integration



Grand Forks, ND

June 2, 2011

Current Work Continued• Development of FAA Concept of Operations

(ConOps)• Development of UAS Research and

Development (R&D) Management Plan– OMB passback language to all NextGen

Partners (FAA, Department of Defense (DOD), Department of Commerce (DOC), National Aeronautics and Space Administration (NASA), Department of Homeland Security (DHS), etc.)

– Due September 30, 2011

Today 2025

Regulation Standards Certification ProceduresFAA UAS Integration Roadmap: Identifies what products & milestones are needed to get there (ARC)

Interdependencies between Civil/Public UAS Roadmap and ConOps

FAA UAS R&D Plan: Identifies the R&D needed to develop products & milestones

UASConOpsJPDO R&D Plan: Considers Collective Interagency R&D Needs

Common R&D ElementsJoint R&D EffortsLeverage data & results

Current NAS

COAs

Limited Civil UAS Ops

Existing Policy and Regs

Interim ApprovalGuidance

NextGen•Concepts•Technologies•Requirements

UAS Integration

Future Policy and Regs

Standards

Certification

Presenter

Presentation Notes

Speaker: Les This is intended to show where we are today, and where we will be in 2025 (identified in the ConOps) The various roadmaps tell us how to get there: -JPDO R&D from an interagency perspective -FAA Integration Roadmap identifies what products and milestones will be needed to get there (a few examples are listed) -FAA R&D Plan identifies the R&D needed to develop those products and milestones that support integration. There will be common elements among these, and opportunities to conduct joint R&D activities with JPDO based on shared R&D. Data and results should be shared to support mission needs and to fill in R&D gaps.

UAS R&D

Requests

Processes

FAA Communication &

Collaboration

External

Influences

COAs

JPDO

Industry

FAA UAS R&DAJV

AVS

AJP-6 Congress

NASA

Air Force Research Laboratory

Others

Presenter

Presentation Notes

Speaker: Rick Prosek This slide has been modified to depict NASA/AFRL/Others as external influences, or contributors, to UAS R&D. They may have roles in the execution/reporting of research, if the FAA determines appropriate. The FAA is working to modify its internal R&D processes, which will include project management of external partners to ensure deliverables of UAS R&D products.



Grand Forks, ND

June 2, 2011

14 CFR, Part 107 Rule: small UAS

Purpose of the regulation:• Enable small UAS to operate safely in limited portions of the

NAS• Gather data

Focus:• Enable the widest range of activity that can be safely

conducted within the shortest rulemaking timeframe

• Timeline:• Notice of Proposed Rulemaking (NPRM) – Fall 2011



Grand Forks, ND

June 2, 2011

Status of FAA Reauthorization Bill

• Senate has passed S. 223– UAS-related sections are 320 and 607

• House has passed H.R. 658– UAS-related sections are 321 through 325 & 1004

• Bills are in conference– Rules provide committee little opportunity for introduction of

new items or major changes to existing provisions

• House Transportation and Infrastructure Committee Chair John Mica’s 5/25/11 blog opines that passage of a reauthorization bill this summer is unlikely



Grand Forks, ND

June 2, 2011

International Activities• ICAO (International Civil Aviation Organization ) UAS

Study Group• EUROCAE Working Group 73• EUROCONTROL Action Plan 24

– Modeling and Simulation• FINAS (Flight In Nonsegregated Airspace)

– North Atlantic Treaty Organization (NATO) activity• JARUS (Joint Authorities for Rulemaking on Unmanned

Systems) (Netherlands + 15)• AMAP (Arctic Monitoring & Assessment Program)



Grand Forks, ND

June 2, 2011

UAS Test Range Facts

• UAS test ranges are addressed in:– H.R. 658– S. 223– NDAA, Section1098



Grand Forks, ND

June 2, 2011

UAS Test Range Questions (1)

• Will there be UAS test ranges if there is no reauthorization bill?

• Will the selection process be transparent?• Will the FAA Acquisition Management System

(AMS) be used for selection?• Will a Screening Information Request (SIR) be

used to obtain recommendations from potential offerors about site and operator requirements?



Grand Forks, ND

June 2, 2011


• Who is the intended user of test ranges – civil, public, or mix?

• Will test ranges need to:– be similar/identical?– provide conventional takeoff and landing capability?– provide opportunity for high speed flight?– provide opportunity for extremely high altitude

operations?



Grand Forks, ND

June 2, 2011


• What is the vehicle for establishment of a test range?– Cooperative Research & Development Agreement– Other?

• What is the vehicle for transiting from takeoff and landing location to working area (if required)?– COA, SAC-EC, or other?

• What will the working area look like?– Title 14, Code of Federal Regulations, Part 91, Section 305 (Flight

test area) requirements?– Underused military operations area?– New or different type of airspace?



Grand Forks, ND

June 2, 2011


• Other considerations – operator’s ability to:– Provide a detailed Concept of Operations– Manage and oversee R & D activities– Mitigate risk– Indemnify the operation (insurance)– Obtain necessary frequency spectrum



Grand Forks, ND

June 2, 2011

FAA Road Ahead • Today/Ongoing

– Improve COA guidance and process– Refine FAA Civil/Public UAS Roadmap– Plan/oversee research and development activities– Gather safety data!!

• Near term– Implement advanced mitigations (GBSAA, others)– Increase NAS access through sUAS rule

• Long term– Eliminate the preliminary and advanced mitigations and

integrate into the NextGen environment



Grand Forks, ND

June 2, 2011

Information

http://www.faa.gov/go/uas

Rick Prosek, Manager, Unmanned Aircraft Program Office(202) [email protected]

Dean Fulmer, Acting Manager, Unmanned Aircraft Systems Group(763) [email protected]

http://www.faa.gov/go/uas�

mailto:[email protected]�

mailto:[email protected]�

Documents

FAA PowerPoint from UAS Action Summit – Looking to the Future