Interagency Aviation Information Bulletin 23-06 Non-Agency, Non-Cooperator UAS TFRs (91.137(a)(1))

· DOI Office of Aviation Services

Public domain · DOI Office of Aviation ServicesAviation Safety Documents

Overview

The Interagency Aviation Information Bulletin 23-06 Non-Agency, Non-Cooperator UAS TFRs (91.137(a)(1)) () is a public-domain DOI Office of Aviation Services aviation safety document, republished here as a free chaptered HTML edition with a linked table of contents and the official PDF.

Publisher: DOI Office of Aviation Services
Document
Pages: 3
Chapters: 4

Key points

The FAA will assist in mitigating conflicts with Non-Agency, Non-Cooperator UAS Temporary Flight Restrictions (TFRs) starting September 1, 2023.
Local dispatch centers must contact the FAA System Operations Support Center (SOSC) to report conflicts with BVLOS TFRs.
BVLOS UAS TFRs are more restrictive than wildland fire TFRs and prohibit wildland fire agencies from entering those airspaces.
Pilots are advised to regularly check TFRs and obtain all NOTAMs before launching.
The duration of BVLOS UAS TFRs will be limited to daylight hours but may be in effect for multiple days.

Frequently asked questions

What is the purpose of the Non-Agency, Non-Cooperator UAS TFRs?

The purpose is to mitigate potential conflicts with UAS operations associated with BVLOS Special Government Interest waivers.

How should pilots respond to TFRs during flight planning?

Pilots should regularly check and monitor TFRs and obtain all NOTAMs for their flight route prior to launching.

What should a local dispatch center do if there is a conflict with a BVLOS TFR?

The local dispatch center should contact the FAA SOSC to inform them that the TFR needs to be cancelled.

What types of operations may be eligible for BVLOS UAS TFRs?

Eligible operations include firefighting, search and rescue, utility restoration, damage assessments, and media coverage.

What is the implementation date for the new procedures regarding UAS TFRs?

The planned implementation date for the new procedures is September 1, 2023.

Coordinated FAA and Agency Procedures

Next: FAA Procedures for understanding →

FAA Procedures for understanding

Next: Internal Notification and Coordination Procedures →

Internal Notification and Coordination Procedures

Next: In the event of a cancellation request →

In the event of a cancellation request

No. IA IB 23-06 Date: August 28, 2023 Page 3 of 3 Coordinated FAA and Agency Procedures FAA Procedures for understanding 1. BVLOS TFR requests go to SOSC from outside entities.

2. SOSC validates request by asking the following: a. Jurisdiction b. 107 or COA c. Statement of work if applicant is contractor.

d. Launch and Recovery Site e. Cell coverage for duration of flight 3. SOSC publishes BVLOS TFR which includes geographic volumes and applicable pilot contact information.

4. SOSC sends BVLOS TFR notification to COD@blm.gov with Subject Line: (a)(1) City/State Internal Notification and Coordination Procedures 1. NICC COD sends to respective GACC with follow up phone call.

2. GACC sends notification to respective Local Dispatch Center with follow up phone call.

3. Local Dispatch Center notifies local Aviation Resources of the BVLOS SGI TFR In the event of a cancellation request 1. Responding Aviation Resource or Dispatch identifies location of incident is in alignment with location of BVLOS SGI TFR.

2. If discovered by Aviation asset request local dispatch to contact SOSC and cancel TFR in order to take aerial suppression action.

3. If discovered by Local Dispatch Center contact responding resources and notify them that deconfliction needs to take place prior to engagement.

4. Contact made by local dispatch to SOSC with cancellation request.

5. SOSC verifies projected duration of suppression action.

6. SOSC contacts outside entity UAS pilot to ground aircraft.

7. SOSC calls local Dispatch Center and verifies UAS is on the ground and TFR is cancelled.

8. If incident evolves into an extended attack, consider a 91.137 (a)(2) Wildland Fire TFR 9. If incident does not evolve, please contact SOSC with an update.

/s/ /Keith Raley /s/ Lori Clark Keith Raley Lori Clark Chief, Aviation Safety, Program Evaluation, Branch Chief - Aviation Safety Management and Quality Management Systems DOI, Office of Aviation Services USDA, Forest Service