Understanding LAANC for Drones
LAANC (pronounced “Lance”) will provide part 101 & 107 UAS operators a streamlined solution to enable real time automated notification and authorization. That will reduce the time from 90 days down to almost instant approval. Implementation began with 50 airports in the fall of 2017, and will expand over the next few years.
LAANC will also provide a means for drone hobbyists to notify air traffic control when they plan to fly within five miles of an airport, a requirement expressed by Congress in 2012 FAA reauthorization legislation. The FAA says that LAANC is due to roll out before end of this year.
This overview will provide the student with an introduction to this new system. The FAA says that LAANC is due to roll out before end of this year.
Course length: 15 mins
Here is more information from the FAA web site: https://www.faa.gov/uas/programs_partnerships/uas_data_exchange/
LAANC is the industry developed application through which you may apply for an airspace authorization or notify the Air Traffic Control Tower of your intended flight plans.
Airspace data is provided through the UAS facility maps (UASFMs)*. The maps show the maximum altitude around airports where the FAA may authorize operations under the small UAS rule. Industry will provide these operators the ability to interact with the maps and provide automatic notification and authorization requests to the FAA.
A prototype evaluation with FAA approved UAS Service Providers will take place in Fall 2017—Spring 2018. The evaluation involves 10 Air Traffic facilities and nearly 50 airports.
A National Beta test will launch in 2018. The beta will continue to evolve and expand the number of ATC facilities and UAS Service Suppliers.
There will be two ways to apply for an airspace authorization. Neither process requires the operator to contact an Air Traffic Control Tower:
- * using the current process; or
- * applying through a FAA approved UAS Service Supplier.
FAA LAANC resource:Programs and Partnerships
Our thanks to AirMap for their kind assistance in developing this information. Other sources include John Meehan, UAS Integration Office, Safety and Integration Division, FAA.