Communicating With ATC When Required
This closing lesson ties the module together: it identifies the specific, limited circumstances where a Part 107 operation actually requires direct communication with air traffic control, and explains how to conduct that communication correctly using the phraseology built in earlier lessons. As with every radio-related lesson in this module, the starting point is the same: Part 107 does not create a general requirement to communicate with ATC for every flight — the requirement, when it exists, comes from something specific about a particular operation.
Most Part 107 operations near controlled airspace don't require a live radio call
A remote pilot operating in controlled airspace near a towered airport typically satisfies 14 CFR 107.41's airspace authorization requirement through LAANC (Low Altitude Authorization and Notification Capability) or a manual DroneZone application — both of which are electronic, automated or semi-automated processes that do not, by themselves, involve a live two-way radio conversation with a tower controller. For the large majority of authorized operations near a towered airport, the authorization itself is the extent of the required interaction with the airspace's controlling authority.
Scenario one: a specific authorization condition requires it
Some airspace authorizations, particularly for operations closer to a primary runway or in more complex or busy airspace, are issued with specific conditions attached — which can include a requirement to contact the relevant ATC facility before commencing the operation, or to provide a phone number the facility can use to reach the remote pilot directly during the operation. When an authorization includes a condition like this, complying with it is mandatory; it becomes a specific, operation-level requirement layered on top of Part 107's general framework, not something the remote pilot can treat as optional.
Scenario two: an in-flight emergency
14 CFR 107.21 addresses in-flight emergencies, giving the remote pilot in command the authority to deviate from any rule in Part 107 to the extent necessary to meet that emergency. If an in-flight emergency during an sUAS operation genuinely requires coordination with ATC — for example, an uncontrolled aircraft behavior creating an immediate hazard to manned traffic near an airport — contacting ATC directly, even without a prior authorization condition requiring it, may be the correct and necessary action to help resolve the emergency safely.
What ATC communication is not: a substitute for airspace authorization
Calling a tower and speaking with a controller is not, by itself, a substitute for obtaining a proper airspace authorization under 107.41 before flying in controlled airspace. A remote pilot can't simply call the tower, describe an intended flight, and treat a friendly response as equivalent to a LAANC or DroneZone authorization — the authorization process and any direct communication requirement it might impose are separate, and both apply independently when relevant.
Direct ATC communication for a Part 107 operation is required in two specific circumstances: a stated authorization condition, or an in-flight emergency.
View LargerApplying the phraseology structure from earlier in this module
When a remote pilot does need to contact ATC directly, the same four-part structure covered in the radio phraseology lesson applies: who you're calling (the specific facility, by name), who you are (identifying yourself and the operation, since a remote pilot doesn't have a traditional aircraft call sign the way a manned pilot does — identifying as the remote pilot for a specific authorized sUAS operation is appropriate), where you are and what you're doing (your operating location and the nature of your authorized flight), and confirming the facility has received and understood the information, similar to the readback concept covered earlier.
Worked scenario: fulfilling an authorization condition
Your LAANC authorization for a rooftop inspection near a towered airport's Class D surface area includes a condition requiring you to call the tower before beginning the flight and provide a phone number for the duration of the operation. Before launch, you call the published tower phone number (not the radio frequency — ground-based phone coordination for this kind of condition is common precisely because it doesn't require radio equipment), identify yourself as the remote pilot for the specific authorized operation, confirm the details match your authorization, and provide your phone number as required. This satisfies the specific condition; it does not require you to carry or use an aviation radio at all.
Clarity and brevity matter more than perfect phraseology
If direct communication with ATC does become necessary — particularly in an emergency — clear, brief, accurate information matters far more than flawless standard phraseology. A controller would always rather receive a slightly non-standard but clear and accurate message than have a remote pilot hesitate or struggle trying to phrase something in perfect aviation-standard language during a time-sensitive situation. The phraseology structure is a tool for clarity, not a barrier to communicating when it actually matters.
Bringing the module together: awareness first, communication when it's actually called for
This module built in a deliberate order for a reason: understanding the airport environment (Lesson A), reading its visual language (Lesson B), predicting manned traffic through the pattern (Lesson C), and building radio literacy (Lessons D and E) all support situational awareness that, in the overwhelming majority of Part 107 operations, is sufficient on its own to satisfy 107.37 and 107.43 without ever requiring a live ATC conversation. Direct communication, covered in this final lesson, is the exception that applies in specific, identifiable circumstances — not the default expectation for every flight near an airport.
Fulfilling an ATC Communication Condition
Follow this sequence whenever an airspace authorization includes a communication requirement.
Read the authorization condition carefully before the mission
Confirm exactly what's required — a phone call, a specific timing, a specific facility — well before arriving on site.
Use the published contact method, not an improvised one
Many conditions specify a phone number rather than a radio frequency; use exactly the method specified in the authorization.
Identify yourself and the specific authorized operation clearly
State that you are the remote pilot for a specific Part 107 sUAS operation, and reference the authorization if useful for the facility.
Confirm the facility has what it needs before proceeding
Don't launch until you've confirmed the communication requirement is genuinely satisfied, not just attempted.
Remain reachable for the duration specified
If the condition requires being reachable throughout the operation, keep the specified phone or radio available and monitored until the flight is complete.
| Scenario | Is direct ATC communication required? | Governing basis |
|---|---|---|
| Standard LAANC-authorized flight, no special condition | No | Authorization itself satisfies 14 CFR 107.41 |
| Authorization includes a specific communication condition | Yes | Condition of the specific authorization |
| In-flight emergency requiring coordination | Yes, if genuinely necessary | 14 CFR 107.21 |
| Routine flight outside controlled airspace | No | No controlling authority involved |
| Mistake | Why it happens | Correct understanding | Regulation / source |
|---|---|---|---|
| Believing every Part 107 flight near controlled airspace requires a live radio call to ATC | "Controlled airspace" sounds like it implies active radio coordination | Most authorized operations satisfy 107.41 through LAANC or DroneZone alone; direct communication is required only in specific circumstances. | 14 CFR 107.41 |
| Treating a friendly phone or radio conversation with a controller as equivalent to an airspace authorization | Getting a positive response feels like informal permission | Communication and authorization are separate requirements; a conversation does not substitute for a proper LAANC or DroneZone authorization. | 14 CFR 107.41 |
| Hesitating to contact ATC during a genuine emergency out of concern for imperfect phraseology | Fear of sounding unprofessional or using incorrect terminology | Clear, accurate communication matters far more than perfect phraseology, especially in a time-sensitive emergency. | 14 CFR 107.21 |
Does every LAANC authorization near a towered airport require calling the tower?
No. Most LAANC authorizations are satisfied electronically with no separate communication requirement. A communication condition, when present, is specific to that particular authorization and will be stated explicitly in its terms.
If I call ATC and describe my planned flight, does that count as an airspace authorization?
No. A phone or radio conversation with ATC is not a substitute for a proper LAANC or DroneZone authorization under 14 CFR 107.41. Both requirements, when applicable, must be satisfied independently.
What authority allows a remote pilot to deviate from Part 107 rules during an in-flight emergency?
14 CFR 107.21 gives the remote pilot in command authority to deviate from any rule in Part 107 to the extent necessary to meet an in-flight emergency, which can include contacting ATC directly if that genuinely helps resolve the situation.
Test Your Knowledge
Answer the questions below to check your understanding. Every answer can be found in the lesson above.