Seattle drone planning works best as a route from shore to sky. Begin with the physical place where the crew will stand. Move outward through the property controller, City or agency rules, active transportation or maritime operations, and public impacts. Only then connect the plan to federal airspace and the remote pilot’s operating responsibility. Reversing that order often produces an airspace answer with nowhere lawful or workable to launch.

This matters in a city where a single composition can include a park edge, ferry route, Port facility, roadway, heliport influence, occupied building, and public waterfront. “Approved in Seattle” is not a meaningful status. The production needs an authority route for the exact ground zone and a flight envelope that the creative team understands.

This guide is a planning tool for producers, location managers, agencies, property teams, and event leaders. It is not legal advice and does not promise approval. Verify current rules and conditions for the exact address, date, activity, and operating point. Seattle’s official guidance is unusually helpful, but it still applies to defined property and production facts. Use the Seattle project request form when the route is mapped and an address-specific feasibility discussion is needed.

Begin at the launch-and-landing ground

Record the exact launch and landing area, crew position, observation positions, equipment, parking, public interface, and emergency options. Add coordinates, photographs, parcel or facility name, and a map. A scenic label such as “waterfront” is not enough; adjacent spaces can have different controllers.

Ask who can authorize the physical activity. A tenant may approve marketing but not a roof. A building manager may control a terrace while the City controls the sidewalk below. A Port tenant may control interior operations without controlling adjacent Port property. A venue operator may need security and event approval in addition to the property agreement.

Write the footprint in operational terms: two crew members on a private loading area, no public-space occupation, no traffic hold, approved arrival window, controlled access, and named property contact. If cones, monitors, vehicles, talent, or pedestrian control extend beyond that footprint, revise the authority route.

Classify the ground controller

Use one of these categories: private owner, City property, Seattle park, Port property, Washington State property, federal property, tribal property, transportation facility, venue, or another named public authority. Do not infer ownership from appearance or public access.

Seattle’s commercial UAS filming page explains when a City Master Film Permit may be required for UAS work, including takeoff or landing on City-owned property or control of City property. It also lists examples where the City says that permit is not required, while emphasizing federal compliance and the scope of City authority.

The City’s film-permit page states that permits cover City-owned property and provides current processing guidance, including additional time for UAS projects. Check the current page when scheduling; do not preserve a lead-time number in a template and assume it remains current.

Put permission evidence beside the map

Store the location agreement, City or agency permit, insurance evidence, security requirements, and contact confirmation with the exact site map. Note the date, activity, aircraft or operator limits, crew footprint, and conditions. If an approval applies only to one phase, do not generalize it to the full production.

Use a boundary test before moving equipment

Ask whether any person, cone, vehicle, monitor, battery station, observer, or landing contingency crosses into space controlled by someone else. A crew that launches from private property can still create a City-property need if it occupies or controls a sidewalk. The boundary test catches that change before the call sheet becomes the de facto plan.

Build the federal flight envelope

Confirm operator and aircraft responsibility

Commercial small-drone work commonly operates under the Federal Aviation Administration’s Part 107 rules. The FAA’s Part 107 overview covers remote-pilot certification, registration, aircraft condition, visual line of sight, operating limits, people and vehicles, and the remote pilot’s authority. Confirm who will serve as remote pilot in command and which aircraft are proposed.

The production can set creative goals and property rules. It cannot transfer the pilot’s regulatory decision to a client, director, or venue. Put that authority in the call sheet and briefing. A schedule delay does not make an unsafe or noncompliant move acceptable.

If the concept depends on an operation outside routine Part 107 conditions, identify the precise issue and proposed approval path. Keep that shot conditional until the relevant authorization and production controls are confirmed.

Screen airports, heliports, seaplanes, and temporary conditions

Use exact coordinates and current official sources. Seattle-Tacoma International Airport, Boeing Field, Renton Municipal, Paine Field, heliports, seaplane activity, and other aviation operations can influence different locations. Water does not mean empty airspace, and distance from a runway on a tourist map is not an authorization analysis.

The FAA’s LAANC information explains an authorization service for eligible controlled-airspace operations. Facility-map values are not themselves approval. An authorization may limit altitude, area, time, or other conditions. The remote pilot should translate those terms into a mapped operating envelope.

Recheck the actual date for temporary restrictions, emergency activity, and notices. The FAA’s where-can-I-fly resources provide official starting points. Current preflight information and on-site observation remain necessary.

Draw the envelope for the director

Mark approved or feasible altitude, lateral boundary, ground position, sight-line limits, public or traffic constraints, and unavailable zones. Then place each requested shot inside that envelope. If a move cannot fit, redesign it before the crew arrives.

Replace the impossible move with an editorial handoff

A continuous flight is not the only way to communicate a spatial relationship. A low architectural rise can cut to a ground-camera waterfront detail. A shore-parallel move can hand off to a ferry or vessel captured from an appropriate non-drone camera position. A campus reveal can connect through matching direction and motion rather than physically crossing uncontrolled space.

This approach can create a more sophisticated sequence because each visual tool does what it handles best. Compliance becomes part of design instead of a postproduction apology.

Route maritime and transportation interfaces

Separate Port property from water and City space

A waterfront concept may involve a private facility, Port of Seattle property, City property, a park, state-managed space, or another controller. Identify the shore position and the subject separately. If the crew or aircraft activity affects an operational facility, obtain the appropriate facility and property approvals.

Port and airport environments can add security, credentialing, insurance, prohibited areas, vessel or ramp activity, and operational contacts. The Port of Seattle publishes current SEA drone operations information for activity associated with the airport. Review the appropriate source for the actual Port facility rather than treating all Port properties as equivalent.

Do not describe ordinary visual media as a marine inspection or operational clearance. Aerial images can show visible context, traffic patterns at a moment, exterior conditions, and spatial relationships. They do not establish navigational safety, structural adequacy, security compliance, or regulatory condition.

Treat ferries as active transportation, not scenery

A ferry-related composition requires more than knowing the timetable. Identify the property controller, terminal operations, vessel relationship, public environment, aviation context, and whether the production needs any control of space. Never assume a public schedule grants filming access or a safe flight path.

Plan the story in layers: terminal context, shore activity, water relationship, vessel passage, and destination context. Some layers may be aerial; others may use ground, long-lens, licensed library, or partner material. The edit can remain coherent without placing the aircraft where the story does not require it.

Account for roads, rail, bridges, and heliports

Transportation infrastructure may be controlled by different City, county, state, federal, Port, rail, or private organizations. A bridge in the composition is not necessarily available as a crew position. A rail-adjacent property agreement does not authorize entry onto rail property. A hospital marketing contact may not control heliport operations.

The location record should note nearby routes, moving vehicles, trains, public access, emergency operations, and any requested control. Assign each approval and safety function to the responsible party. Avoid a generic line such as “traffic handled by production.”

Build an interface clock

Place ferry movements, vessel windows, rail activity, traffic peaks, bridge or road impacts, heliport concerns, event times, and property access on one timeline. Mark green, conditional, and unavailable periods. This interface clock often reveals a quiet ten-minute window that matters more than an entire unscheduled day.

Coordinate parks, public space, and occupied properties

Follow the City process for City-controlled activity

Seattle’s official UAS page states that a Master Film Permit is required in specified circumstances involving City-owned property or control of City property, and it lists current documentation expectations for applicable UAS film work. Those materials include operator and aircraft information, aviation insurance, and a site plan. The City also clarifies that its review of a flight plan is for property and production coordination; it does not approve federal airspace.

Use the official page for current requirements and contact the Film Office when facts are unclear. The City’s film-permit page describes its role as a point of contact for City property. Do not independently assume that a recognizable landmark, pier, market, stadium, or attraction is City-controlled; the page specifically distinguishes City property from other locations.

Treat parks as managed production environments

Seattle’s film manual and UAS guidance explain the pathway for commercial UAS filming in City parks through the applicable process. A park can still present public activity, trails, vegetation, wildlife, events, and limited operating areas. The permit pathway does not guarantee that the remote pilot will find conditions safe or that the intended composition will be available.

For state-managed property, review Washington State Parks’ current filming requirements for the specific location. For federal or tribal land, consult the relevant manager. Property category determines the route; landscape type does not.

The Seattle real-estate aerial service may suggest ways to show neighborhood and landscape context from owner-controlled property. That alternative can be more informative than launching from a scenic public area simply because it appears close on a map.

Protect occupied campuses and private venues

Private property removes some City-property issues but can introduce tenant, employee, guest, security, and operational constraints. Obtain written control for launch and landing, then coordinate internal approvals. Identify restricted directions, confidentiality, public interfaces, emergency access, and media review.

For events, separate venue approval from event command and aviation review. The Seattle event aerial service is best planned by phase: empty venue, sponsor build, guest arrival, active program, and strike. The most useful aerial window may occur before the largest crowd.

Create public and restricted shot lists

Use one list for assets intended for external release and another for internal or restricted context. Each should have an approval owner. This prevents a technically useful roof or infrastructure image from entering a public campaign simply because it looks dramatic.

Close with a stop/go route card

Require eleven answers before call-sheet lock

Confirm the exact ground footprint, property controller, written permission, City or agency pathway, active facility approval, remote pilot, aircraft, airspace path, interface clock, public-control plan, and publication clearance. Then confirm a twelfth item: the substitute for every conditional hero shot.

Mark each answer green, amber, or red. Green means verified for the described activity. Amber means named condition and decision owner. Red means the shot cannot remain guaranteed in the current plan. A folder full of applications is not green unless the necessary approval and conditions are understood.

Issue one route card per location

The route card should fit on one page: map, ground controller, aviation envelope, approved operating window, interface clock, site contacts, crew footprint, shot priorities, restrictions, alternate concept, and go/no-go decision time. Link to the full evidence rather than crowding the page with every document.

Review the route card with the pilot, producer, location owner, and relevant operations contact. The creative lead should understand the envelope; the operations team should understand the intended activity. Misunderstanding usually appears where those two views were never reconciled.

Keep current verification in the workflow

Property rules, City procedures, contact details, airspace, notices, weather, and operating conditions can change. Recheck official sources and approval status before the operation. Preserve dated evidence, but never treat an old approval as a permanent entitlement.

The shore-to-sky method remains useful even as tools evolve because it asks durable questions: Where are we standing? Who controls that activity? Which operating systems are active? What does federal authority allow? Can the creative fit the verified envelope? What happens if one condition changes?

Send the route cards, addresses, proposed dates, intended shots, and unresolved controllers through the Seattle project request form when a scoped review would help. The aim is a production that feels unmistakably Seattle because it was designed around the city’s real interfaces, not because a generic skyline was added at the end.

Rehearse four controller routes before production day

For a private downtown rooftop, the route begins with the owner or authorized building manager. Confirm roof access, structural and safety rules for crew presence, tenant or engineering coordination, approved hours, equipment, and the precise launch area. Then review the aircraft operation at exact coordinates and map the public-facing edge. If a visual observer or other crew position would occupy a sidewalk, the activity is no longer wholly contained on the private roof. The route card must reflect the expanded footprint. The creative alternative may be a tighter façade-and-context rise that remains within the controlled geometry rather than a broad orbit that depends on adjacent space.

For a City park, begin with the official City film and UAS process, not a casual site visit. Confirm that the proposed activity is eligible, submit the current required materials, and map the takeoff, landing, flight path, and any public control requested. The City’s review does not replace the remote pilot’s federal analysis, and a permit does not guarantee that crowds, weather, wildlife, or a conflicting event will make the planned moment workable. Build a low-impact alternate composition and a decision point for moving or removing the shot.

For a Port- or marine-adjacent facility, identify the property boundary and active facility authority first. A tenant contact, vessel operator, terminal function, Port property contact, and aviation authority may each answer different questions. Record security, prohibited directions, operating schedules, public shoreline, rail or road interfaces, and emergency activity. The Seattle industrial drone inspection service can help frame a visual goal, but the route card must name which elements are controlled and which are only background context. If the desired vessel relationship cannot be secured, design the sequence from a controlled shore position and use non-drone coverage for the missing layer.

For an event venue, divide the route by phase. Load-in may involve trucks and lifts. The clean-venue window may offer the best architectural frame. Guest arrival changes the people environment. Active program hours can change site rules, aviation conditions, and the value of an exterior. Strike introduces a different circulation plan. Obtain venue and event-command approval for the specific phase and keep federal review current. A permit associated with the venue is not a blanket approval for every operational period.

Compare dependencies and close each route

After rehearsing the routes, compare their dependencies. The rooftop route may be most vulnerable to access and public-edge expansion. The park route may depend on City process and public conditions. The marine route may depend on multiple active organizations. The event route may depend on schedule and people density. This comparison helps a producer order the shots: secure the most fragile hero assets early, place adaptable context later, and never let an optional shot jeopardize a controlled one.

Create a controller contact protocol. The aerial crew should not make uncoordinated calls that conflict with the location manager, and the producer should not relay technical approval conditions from memory. Name the communicator for each authority and store dated confirmation. If an agency asks for a change, the coordinator determines which route nodes must review it.

Finally, rehearse cancellation. Say out loud what happens if a ferry or vessel operation changes, the public space becomes crowded, a heliport concern arises, a roof contact is unavailable, or weather removes visibility. Identify the person who declares the creative substitute accepted. This rehearsal turns an amber route into a managed production choice instead of a day-of argument.

The four routes demonstrate why a master checklist cannot be copied from one address to another. They share a discipline—exact ground, named authority, federal envelope, active interfaces, current evidence, and alternate design—but their decisions and contacts remain place-specific. That is the standard a professional Seattle production should be able to show.

Preserve that reasoning with the final route card so the field team understands the decisions, not only the resulting restrictions.

Add a version-control rule to every route card. When the launch point, crew footprint, time, aircraft, shot path, property contact, or public-control need changes, increment the version and highlight the changed field. Send the revision to the owners responsible for the affected nodes instead of assuming a prior response still applies. Keep superseded cards in the evidence folder but mark them inactive so the field team cannot mistake an old plan for the current one.

Use a preflight evidence check that is separate from the creative review. The coordinator confirms the current route card, approval files, contacts, insurance, access, event status, and notices. The remote pilot completes the required aviation and aircraft review. The director confirms must-have shots and accepted alternatives. Each role signs off on its own responsibility; no single generic “all approved” message replaces them.

After the operation, compare the actual footprint and capture with the route card. Record canceled shots, approved substitutions, unexpected public or operational conditions, and any distribution restriction learned on site. That closeout makes the production defensible and improves the next brief without implying that today’s approval extends to tomorrow.

For agencies managing multiple Seattle locations, summarize the routes in a portfolio register. Keep each location’s controller facts separate, then compare lead times, recurring requirements, and successful alternate designs. The register can reduce repeated discovery while preserving the city’s property-by-property reality.