B4UFLY Smartphone App

ICR 201508-2120-004

OMB: 2120-0764

Federal Form Document

Forms and Documents
Document
Name
Status
Supplementary Document
2015-08-26
Supporting Statement A
2015-08-21
Supplementary Document
2015-08-18
IC Document Collections
IC ID
Document
Title
Status
217906 New
ICR Details
2120-0764 201508-2120-004
Historical Active
DOT/FAA
B4UFLY Smartphone App
New collection (Request for a new OMB Control Number)   No
Emergency 08/28/2015
Approved without change 08/27/2015
Retrieve Notice of Action (NOA) 08/21/2015
In accordance with 5 CFR 1320.13 this information collection is approved for 6 months. OMB requests that when the ICR package is submitted for the public version of the app that FAA use the data collected during the beta test to update the burden and cost estimates and inform the final version of the app. OMB also requests that FAA publish the 60-day notice for public comment in the federal register on the public version of the app as soon as possible after the publication of the emergency request notice in the federal register. OMB requests that approval of this emergency request be limited to just beta testing and that the public version of the app be submitted to OMB for review prior to its release.
  Inventory as of this Action Requested Previously Approved
02/29/2016 6 Months From Approved
45,000 0 0
1,485 0 0
0 0 0

The FAA's B4UFLY smartphone app will provide situational awareness of flight restrictions – including locations of airports, restricted airspace, special use airspaces, and temporary flight restrictions – based on a user's current or planned flight location. In order to maintain NAS safety in proximity to airports, air traffic control personnel would need certain basic information about a UAS operator's intended flight in order to assess whether the UAS may disrupt or endanger manned air traffic. The data collected by the B4UFLY app during the initial 60-day beta test will help the FAA determine procedures for managing more widespread public use of the B4UFLY app.
AVS requests that AFN seek emergency clearance from OMB to collect information from members of the public beta testing the FAA’s B4UFLY smartphone app. The FAA has documented over 675 pilot and law enforcement reports of unmanned aircraft ‘events’ in 2015. In comparison, the FAA received 238 of these reports in the entirety of 2014. This increase in reports, particularly in close proximity to airports, suggests that many unmanned aircraft system (UAS) operators are unaware of safety guidelines and policies and are unaware of the potential hazards these operations may pose to manned aircraft operations. The FAA’s B4UFLY smartphone app will provide situational awareness of flight restrictions – including locations of airports, restricted airspace, special use airspaces, and temporary flight restrictions – based on a user’s current or planned flight location. The risk posed to the National Airspace System (NAS) by increasingly unsafe UAS operations makes the immediate release of this app vital. The app is planned for beta release in August 2015. In addition, Public Law 112-95, Section 336 requires model aircraft operators to notify the airport operator and air traffic control tower (if one is located at the airport) prior to operating within 5 miles of an airport. Currently, there is no established process to facilitate this exchange of information. The B4UFLY app’s initial concept included providing phone numbers for users to call air traffic control towers (ACTCs) to fulfill this notification requirement. However, further analysis showed that frequent calls to an ACTC could disrupt normal tower functions and possibly create a safety risk. Therefore, the FAA will develop an electronic notification process using functionality in the B4UFLY app. The app is planned for beta release in August 2015 Users will not be able to fulfill the statutory requirement for notification using the beta version of B4UFLY. This initial version will collect flight data from users, which will help the FAA develop automated procedures for accomplishing electronic notification when Version 1 of B4UFLY is released to the general public (targeted by December 2015). Electronic notification in this manner will ultimately give air traffic personnel real-time information about potentially unsafe UAS operations around airports, enabling immediate safety mitigation activities. It will also make notification easier for the public, and thus increase compliance with the law. To ensure that flight safety is not compromised within the U.S. National Airspace System, it is imperative that the FAA receive approval from OMB to conduct this collection of information as soon as possible.

PL: Pub.L. 112 - 95 336 Name of Law: FAA Modernization and Reform Act of 2012
  
None

Not associated with rulemaking

No

1
IC Title Form No. Form Name
B4UFLY Smartphone App

  Total Approved Previously Approved Change Due to New Statute Change Due to Agency Discretion Change Due to Adjustment in Estimate Change Due to Potential Violation of the PRA
Annual Number of Responses 45,000 0 0 45,000 0 0
Annual Time Burden (Hours) 1,485 0 0 1,485 0 0
Annual Cost Burden (Dollars) 0 0 0 0 0 0
Yes
Miscellaneous Actions
No
This is a new collection activity, therefore it is a program change.

$810
No
No
No
No
No
Uncollected
Erik Amend 202 267-8282

  No

On behalf of this Federal agency, I certify that the collection of information encompassed by this request complies with 5 CFR 1320.9 and the related provisions of 5 CFR 1320.8(b)(3).
The following is a summary of the topics, regarding the proposed collection of information, that the certification covers:
 
 
 
 
 
 
 
    (i) Why the information is being collected;
    (ii) Use of information;
    (iii) Burden estimate;
    (iv) Nature of response (voluntary, required for a benefit, or mandatory);
    (v) Nature and extent of confidentiality; and
    (vi) Need to display currently valid OMB control number;
 
 
 
If you are unable to certify compliance with any of these provisions, identify the item by leaving the box unchecked and explain the reason in the Supporting Statement.
08/21/2015


© 2024 OMB.report | Privacy Policy