An Atlanta Production Coordinator's Map of Airports, Film Offices, Parks, Stadiums, and Private Property

The fastest way to lose time on an Atlanta drone production is to ask, “Which permit do we need?” before identifying who controls the places and activities in the shot. A production coordinator may be dealing with federal airspace, a private campus, a City street, a park, a stadium operator, a studio security team, and a location agreement at the same time. None of those parties automatically speaks for the others.

A better method is to draw a controller map. Put the aircraft operation in the center. Around it, place the aviation authority, launch-site controller, filming or occupancy authority, venue operator, event command, neighboring property, and media-clearance owner. Then connect each desired shot to the approvals and operating conditions it actually needs. The map often inspires a stronger idea: instead of forcing one impossible continuous move, a production can build a sequence of separately controlled visual chapters that edits as one confident Atlanta story.

This guide gives coordinators, agencies, location managers, property teams, and producers a current planning framework. It is not legal advice and does not guarantee approval. Rules, property policies, airspace, emergency activity, and event conditions can change. The remote pilot and responsible production contacts must verify the exact address, date, altitude, ground position, and activity in current official sources. Once the controller map is assembled, the Atlanta project request form can be used for a location-specific feasibility conversation.

Draw the controller map before promising the shot

Start with a one-page location card

Create a card for every proposed operating area. Record exact coordinates, street address, parcel or venue name, proposed launch and landing zone, intended flight area, requested altitude, date and time, crew footprint, ground-control need, subject, and desired move. Attach a map and current reference photographs. Do not use “near downtown,” “by the stadium,” or “at the campus” as operational descriptions.

Add the name of the person who appears to control each physical space. The property owner may control a parking lot while a tenant controls interior access. A building manager may control the roof but not the neighboring plaza. A venue may control its campus while a City department controls the curb lane requested for production vehicles. The card should show unknowns rather than bury them.

The controller map turns a vague creative request into a responsibility plan. It also gives the director early choices. If a preferred launch point depends on an uncertain public-space approval, the treatment can include an alternate reveal from owner-controlled property. If an event window makes a moving crowd impractical, the production can capture the exterior before gates open and combine it with ground coverage later.

Separate seven kinds of authority

Use distinct rows for:

1. federal operating rules and airspace authorization;
2. launch-and-landing property permission;
3. City film, street, sidewalk, parking, or park process;
4. venue, campus, studio, or facility operating approval;
5. event, stadium, emergency, or security restrictions;
6. people, traffic, and ground-safety controls; and
7. rights, releases, confidentiality, and publication clearance.

One document may inform several rows, but it rarely resolves all seven. A location agreement does not authorize controlled airspace. An FAA authorization does not reserve a sidewalk. A marketing director’s approval does not necessarily give roof access. A film permit does not promise that the remote pilot can operate safely under current conditions.

Mark every row verified, pending, conditional, or blocked

“Pending” means an identified process and owner are actively working. “Conditional” means the shot can proceed only if a named condition is met. “Blocked” means the current concept should not remain in the guaranteed deliverable list. This vocabulary keeps optimism from becoming a production promise.

Set a decision deadline for every pending item. If the deadline passes, activate the approved alternative. A controller map is valuable only when it changes the schedule or creative plan.

Name the approval owner, not merely the organization

“Client handles permits” is not a responsibility assignment. Name the individual or role, the required submission, supporting documents, due date, confirmation method, and escalation contact. If the agency owns the City film process while the aerial provider owns aviation review, put that division in writing. If the property manager owns tenant notice and roof access, identify both deliverables.

A production coordinator should maintain one evidence folder containing applications, approvals, insurance certificates, maps, contacts, operating conditions, notices, and the current creative version. The call sheet should summarize what the crew needs, not replace the evidence.

Complete the aviation screen with exact coordinates

Confirm the federal operating framework

Most commercial small-drone photography and video is conducted under the Federal Aviation Administration’s Part 107 framework. The FAA’s Part 107 overview covers remote-pilot certification, aircraft registration and condition, visual line of sight, operating limits, people and vehicles, and the remote pilot’s responsibility. The person acting as remote pilot in command retains authority over the flight decision.

Confirm the proposed aircraft, operator, and operating rule. Ask whether any requested activity falls outside routine Part 107 conditions and, if so, what specific authorization or waiver path is proposed. Do not treat the production’s importance as a reason for the pilot to exceed a condition.

The federal screen should reach the creative team. If the requested altitude, people environment, line of sight, or flight path cannot support the exact concept, the right response is a redesign. A cut, ground-camera handoff, stabilized reveal, longer lens, or different time can preserve the story without pretending the rule disappeared.

Check Atlanta’s full aviation context

Review the exact operating point in current official tools. Hartsfield-Jackson Atlanta International Airport is only one influence. DeKalb-Peachtree Airport, Fulton County Airport-Brown Field, Dobbins Air Reserve Base, Cobb County International, Peachtree City-Falcon Field, heliports, medical operations, temporary flight restrictions, and other traffic can matter at different metro locations.

The FAA describes LAANC as an authorization pathway for eligible controlled-airspace operations. Published facility-map values can inform the process but are not themselves permission. An authorization may include altitude, time, area, notification, or other conditions. The pilot must interpret those conditions for the proposed shot.

Do not rely on a screenshot from an old project or the statement that another crew flew nearby. Airspace classification is only part of the answer, and current conditions matter. Keep the approval reference and applicable conditions with the location card.

Convert the aviation result into a visual envelope

For each hero shot, state the maximum usable altitude, practical horizontal area, available sight line, people or vehicle limitations, and time condition. Draw that envelope on the scout map. The director can then compose inside a real operating space.

This is more productive than asking an operator to “get as high as possible.” A lower, layered move may reveal architecture, trees, and city context with more depth than a generic high skyline view. Constraint can improve the image when it is translated early.

Recheck temporary and event-driven conditions

Use the FAA’s current where-can-I-fly resources and the remote pilot’s required preflight sources for the actual date. Temporary flight restrictions, emergency response, security movement, wildfire activity, stadium events, or other notices can change the plan after a scout.

Atlanta productions near stadiums or major events need schedule-aware review. The same location can have a different operating answer on a quiet morning and during a game or high-security event. Build a final aviation check into the call sheet and a day-of authority check into the pilot’s workflow.

Resolve the ground and municipal production layers

Verify private-property authority in writing

Ask who can authorize launch, landing, crew presence, equipment staging, roof use, parking, pedestrian controls, and access to restricted areas. A broker, tenant, venue marketer, or agency contact may support the project without controlling those spaces. The location agreement should identify the approved zone, operating window, insurance, security, restoration, neighbor limits, confidentiality, and cancellation authority.

At studios and corporate campuses, site rules may include credentials, equipment lists, escorted areas, radio restrictions, non-disclosure terms, or content review. At occupied properties, building operations may require tenant communication and an alternate date. At construction sites, the general contractor may control safety induction and daily access even when the owner commissioned the work.

The Atlanta real-estate aerial service can help shape a property story, while the Atlanta industrial documentation service frames exterior visual-record needs. Neither service description replaces permission from the actual controller.

Use Atlanta’s film process for the activity it controls

The City of Atlanta’s current film-permitting page explains that a filming permit may be required for specified activities, including filming on public property, certain street or sidewalk closures, temporary structures, and particular nighttime impacts. A producer should review the current guidance and contact the responsible office for the proposed facts.

Map City-controlled activity precisely. Is the crew standing on a sidewalk? Reserving parking? Placing a monitor or cones? Holding pedestrians? Using a park? Requesting a street or lane closure? Each answer can change the local production pathway. A private-property agreement does not cover an overflow crew or vehicle footprint on public space.

Do not ask the film office to approve federal airspace; that is not the same authority. Likewise, do not treat an aviation authorization as permission to occupy City property. The controller map should keep both confirmations visible.

Treat parks, trails, and state-managed locations as specific properties

A green space is not an unowned launch pad. City parks, BeltLine-adjacent areas, state parks, federal sites, trails, gardens, and institutional landscapes can have different stewards and commercial-filming processes. Identify the legal property name and managing organization, then verify current rules directly.

Georgia State Parks publishes a commercial filming and photography process for state-managed properties. It should be reviewed for a proposed state-park location rather than generalized to a City park or federal site. Scenic resemblance does not create shared authority.

The best alternative is often creative, not evasive. An owner-controlled foreground with a legally captured distant landscape may communicate place better than a high, generic panorama. A ground-camera sequence can carry the intimate park experience while the aerial unit provides context from a separately approved site.

Coordinate campuses, venues, stadiums, and public interfaces

Add an operating-organization layer

Property permission may still be insufficient at an active venue, studio, airport-area facility, rail property, university, hospital, utility, or stadium. The organization running the site may control security, safety, brand, tenants, event schedules, credentials, or restricted views. Add its operations contact to the controller map.

For a studio or corporate campus, ask about confidential areas, live productions, employee privacy, radio or communications constraints, and distribution review. For a hospital or university, ask about heliport activity, emergency access, occupied courtyards, and communications with campus safety. For a logistics property, identify truck circulation, yards, gates, and tenant operations.

These are not reasons to abandon an idea. They reveal when a controlled pre-opening window, weekend capture, restricted lens direction, or staged activity can produce cleaner and more distinctive work.

Plan stadium and event work as phases

An event exterior can be divided into load-in, clean venue, sponsor activation, guest arrival, peak activity, and strike. Each phase has different people density, vehicle movement, security posture, light, and creative value. The Atlanta event aerial service is most effective when the producer chooses which phases deserve aerial coverage instead of asking for continuous presence.

Stadium-related airspace restrictions may depend on the event and timing. Event command can also impose rules beyond ordinary property access. Put the game, concert, festival, or conference schedule on the aviation and site-control timeline. A permit or agreement obtained weeks earlier does not eliminate day-of coordination.

Create a red-window / amber-window / green-window schedule

Red windows are unavailable because of restrictions, uncontrolled crowds, critical operations, or absent authority. Amber windows may work only with specific controls, staffing, or final confirmation. Green windows are the preferred, approved periods for essential capture. Tie every hero shot to a green window and keep amber ideas as conditional options.

This schedule helps creative teams see that the best-looking moment is not always the busiest moment. A sponsor build captured before gates open can be cleaner, more legible, and more reusable than a wide crowd shot.

Protect the public-facing edge

Many Atlanta locations place the crew beside streets, sidewalks, parking circulation, trails, or neighboring businesses. Define the crew footprint, observation positions, communication method, emergency landing considerations, and boundary that the production will not cross. If pedestrian or vehicle control is required, assign it to an authorized and properly planned function rather than expecting the pilot to improvise.

The public-facing edge also affects community relations. Noise, visible equipment, blocked access, and privacy concerns can create conflict even when paperwork exists. Use notices or stakeholder communication where the controlling authority requires it, and keep the crew footprint proportional to the shot.

Run the stop/go review and hand off a usable plan

Ask ten stop/go questions

Before the call sheet is final, answer:

1. Are the exact coordinates and operating area confirmed?
2. Is the federal rule and airspace pathway identified?
3. Are authorization conditions compatible with the hero shots?
4. Does the production have written launch-and-landing permission?
5. Does any City film, park, street, sidewalk, or parking process apply?
6. Has the active venue, campus, studio, or facility approved the operation?
7. Are event and temporary restrictions checked for the actual time?
8. Can the ground environment be controlled without relying on the pilot alone?
9. Are releases, confidentiality, and publication rights assigned?
10. Does every conditional shot have an approved substitute and decision deadline?

A single “no” does not always cancel the project. It may change the shot, ground position, schedule, crew, or deliverable. An unknown without an owner is the real stop sign.

Package the plan for crew and client

The field packet should include approved location cards, controller map, airspace evidence and conditions, property agreements, City or agency documents, insurance, site maps, contacts, red/amber/green schedule, shot priorities, alternate concepts, weather decision, and communication protocol. Keep sensitive documents in the proper controlled channel rather than attaching everything to a broadly distributed call sheet.

The client-facing summary should show what is approved, what remains conditional, and what the production will deliver if conditions change. That transparency helps a creative stakeholder make decisions without learning aviation jargon.

Maintain an approval ledger through wrap

The controller map is a planning view; the approval ledger is the audit trail. Give every item a unique identifier and record the location, controller, request owner, submission date, current status, applicable conditions, evidence link, expiration, and final closeout action. Store the original approval and a plain-language interpretation together, while making clear that the original document controls.

Review the ledger at three checkpoints. At treatment lock, confirm that each guaranteed shot has a plausible path. At call-sheet lock, confirm that required approvals are in hand or explicitly conditional with a substitute. At the day-of briefing, confirm current aviation notices, property access, event activity, weather, and contact availability. A last-minute text from an enthusiastic stakeholder is not a substitute for the required written authority.

After capture, close the loop. Note whether the operation followed the approved area and conditions, record material deviations or cancellations, return badges or access devices, release reserved public space as required, and route media through the agreed review channel. If a condition limited publication—for example, a restricted view or confidential campus feature—carry that restriction into the asset metadata and editor notes.

This ledger also improves future work without turning past approval into present permission. A producer can see which controllers were involved, how long coordination took, and which creative alternatives worked. The next project still needs current review for its address and date, but it starts with institutional knowledge instead of folklore.

For multi-day work, add a daily change log. Record schedule movement, location revisions, new event conflicts, shifts in crew footprint, and any approval that must be amended. The log makes it possible to explain why a shot changed without blaming the operator or hiding the decision from the client.

Include the creative version number in each ledger review. Treatments evolve, and an approval for a static exterior may not cover a later request for traffic control, a different launch point, a larger crew, night work, or a move across a property boundary. The coordinator should compare the current shot description with the activity actually submitted. If the facts changed, ask the controller whether an amendment or new review is required.

Use the ledger to manage expirations and narrow conditions. Insurance endorsements, reserved parking, credentials, access windows, and approvals may apply only to named dates, aircraft, operators, or locations. Highlight those limits in the field summary. A document stored in the folder is not useful if the crew assumes it covers more than it says.

At wrap, give the producer a short lessons record: which controller paths were straightforward, which required additional lead time, which alternatives preserved the story, and which concepts should not be repeated without a different operating strategy. This is not permission for future work. It is a better starting hypothesis for the next scout.

Have the production manager approve that record while memories are current. Include unanswered questions and the source that should be consulted next time. If a property or agency contact asks that information not be reused, honor that limitation in the record. Institutional knowledge should improve coordination without becoming a shadow permit system or an excuse to skip current verification.

Use constraints to design a more Atlanta-specific sequence

The controller map is not only compliance paperwork. It is a creative instrument. It might suggest a dawn architectural chapter on a private campus, a controlled studio exterior at a scheduled production break, a graphic top-down logistics pattern from an approved parcel, and a low, layered skyline reveal that connects them. The edit can feel larger because every piece was designed for its real place.

For a location-specific review, send the address, coordinates if known, proposed dates, desired shots, property contact, event schedule, and intended channels through the Atlanta project request form. The goal is not to promise an approval. It is to identify the actual controllers early enough to build a feasible and original production.