A pilot recently shared a story that should be required reading for anyone flying a drone in or near a city. He had done everything the apps tell you to do. His drone was registered with the FAA. He had his TRUST certificate. He pulled a LAANC authorization before launch. He picked a quiet Monday morning, brought someone along as a visual observer, and when a group of dog walkers came through he walked over and offered to hold off if the drone would spook the animals.
He was in the air for about five minutes when a park ranger pulled up. The ranger glanced at the LAANC authorization, asked for ID, and wrote a $500 civil summons. The LAANC made no difference, because he was flying in a city park, and that park bans drones under its own rules.
If your first reaction is "but he had authorization," you have found the exact trap. It is one of the most common and most expensive misunderstandings in recreational and Part 107 flying, and it comes down to a single distinction.
Airspace is federal. The ground is not.
The FAA controls the airspace. It does not control the land underneath it. Those are two different jurisdictions with two different sets of rules, and a drone flight touches both at once.
UAS SkyCheck
Check your exact location: airspace class, TFRs, restricted zones, live weather, and a 0-100 safety score.
LAANC, the Low Altitude Authorization and Notification Capability, lives entirely on the federal side. It is how the FAA grants near-instant authorization to fly in controlled airspace near an airport, up to a published altitude ceiling. It is genuinely useful and, for what it does, excellent.
But the land you take off from, land on, and fly over belongs to someone: a city, a county, a state, a federal land agency, a homeowners association, a private owner. Any of them can set rules about drones on their property, and those rules exist completely independently of the airspace above.
What LAANC actually covers, and what it does not
It helps to be precise about the boundary.
LAANC covers: authorization to operate in controlled airspace near a participating airport, and the maximum altitude you are cleared to fly within that grid.
LAANC does not cover: permission to take off or land from a specific piece of land, a city or park drone ordinance, a state park ban, a special event closure, or any other local rule. A LAANC approval is the FAA saying the sky is available. It is not anyone saying the ground is.
This is why the pilot in the story was both authorized and fined at the same time. Nothing about those two facts is contradictory. The FAA cleared his airspace. The parks department never cleared his takeoff.
You usually need two separate yeses
The mental model that keeps pilots out of trouble is that a legal flight often requires two independent approvals:
| Layer | Who controls it | What clears it |
|---|---|---|
| Airspace | FAA | LAANC, or no authorization needed in uncontrolled (Class G) airspace |
| The land below | City, county, state, federal agency, HOA, or private owner | The land manager's own rules or permit |
Getting one does not satisfy the other. A LAANC authorization in controlled airspace says nothing about whether the park allows drones. A park that allows drones says nothing about whether you still need LAANC for the airspace. You have to clear both before the flight is actually legal.
Why this is so easy to miss
The popular airspace apps are not wrong. They are answering a narrower question than pilots think they are. They tell you, accurately and quickly, whether the FAA needs to authorize your airspace and whether it will. That is the federal layer, and they do it well.
The problem is that "LAANC approved" feels like a green light for the whole flight. It is not. It is a green light for one of the two layers. When the only tool in your hand answers the airspace question, it is natural to assume the airspace question is the whole question. It almost never is, especially anywhere near a population.
It is not just New York
New York City is an extreme case. Its parks rules effectively prohibit drone takeoff and landing except at a small number of designated model aircraft fields, and the city as a whole is unusually restrictive. But the pattern is everywhere:
- Chicago restricts drones along much of its lakefront and parks.
- Many state park systems ban drone takeoff and landing across the entire system.
- Countless city and county parks set their own policies, which range from "fine, go ahead" to "permit required" to "absolutely not."
- Beaches, nature preserves, stadiums, and HOA-governed communities all add their own layers.
The rules vary enormously from one jurisdiction to the next, they change, and there is no single federal map that captures all of them. That is precisely what makes them so easy to fly into without warning.
How to not get the $500 summons
A few habits close most of the gap:
- Treat LAANC as the airspace check, not the final word. When it clears you, you have settled the federal question and nothing else.
- Identify who controls the ground at your exact takeoff and flight area, then check their rules. For a park, that is the parks department. For a beach or preserve, the managing agency. In a neighborhood, possibly the HOA.
- When you cannot find a clear rule, assume one might exist and confirm before you fly. Silence is not permission.
- Remember that enforcement is local and discretionary. A ranger does not have to issue a warning, and as this pilot learned, many will not.
This split is the entire reason UAS SkyCheck exists. A UAS SkyCheck result layers known local restrictions, city ordinances, park bans, state-level rules, on top of the airspace and LAANC answer, so you see both layers in one place. And because no dataset can map every municipal rule in the country, every result also carries a standing reminder to confirm local rules with the land manager, so an airspace-clear result never quietly reads as legal to fly. The goal is to make sure the federal yes is never mistaken for the only yes.
The bottom line
Airspace clear is not the same as legal to fly. LAANC answers a federal question about the sky. The park ranger answers a local question about the ground. Both have to say yes before you launch. The pilot who got fined had one of those two answers and assumed it was the whole story. The fix is not more authorizations. It is knowing there are two questions, and asking the second one before you take off.