Scene 01Take 1●
Four stops make three legs
The sample connects Toronto, Montreal, Quebec City and Halifax in 17 seconds. Each stop pauses for two seconds, and each of the three moves lasts three seconds: 4 × 2 + 3 × 3 = 17. The numbered markers identify the cities; the same regional passenger-jet symbol carries each leg.
This is an illustrative connection between approximate city centres. It is not a flight schedule, airport-to-airport routing, recorded aircraft track or claim that these services operate. The curved line describes the animation, not the airspace an aircraft would use.
The four-stop flight animation uses renderer sources from NASA, Natural Earth, Flagpedia and HYG v3 (David Nash / Astronomy Nexus), adapted from Geographical Adventures by Sebastian Lague. This named local movie and its poster are shared under CC BY-SA 2.5. Keep the map-source credits and change notes with copies. The record identifies any separate factual-data credits; it does not license other complete videos or hosted exports.
| Time | Action | Timing control |
|---|---|---|
| 0:00–0:02 | Toronto: marker 1 | Two-second stop pause |
| 0:02–0:05 | Toronto → Montreal | Three-second outgoing Fly leg |
| 0:05–0:07 | Montreal: marker 2 | Two-second stop pause |
| 0:07–0:10 | Montreal → Quebec City | Three-second outgoing Fly leg |
| 0:10–0:12 | Quebec City: marker 3 | Two-second stop pause |
| 0:12–0:15 | Quebec City → Halifax | Three-second outgoing Fly leg |
| 0:15–0:17 | Halifax: marker 4 | Two-second final pause; no outgoing move |
Scene 02Take 1●
Choose what your line represents
For a memory video, a city-to-city connection may be enough. For a story about particular airports, select and verify those airport locations instead. A recorded track needs an actual track source and a tool that can reproduce it; do not label a pair of selected endpoints as flight-tracking data.
Keep a route sheet with the intended place, the public-facing label and what the connection means. The GPX and route-import guide explains the separate distinction between a recorded path and manually chosen stops. Removing a private departure address is often more useful than adding another decimal place.
Scene 03Take 1●
Use the controls to make the sample readable
The render uses top-down framing, camera altitude 70, field of view 18 and zero latitude/longitude camera angles at the stops. Highlights are off and opening/ending bookends are None. These are the sample’s settings, not a universal camera recipe: a longer route or a portrait frame needs a separate review.
Set the outgoing movement to Fly, keep the aircraft choice consistent, and give each departure its travel duration. A pause belongs to a stop; travel time belongs to the move that follows it. The last stop needs a pause but no outgoing journey.
The tested route walkthrough shows current website controls and a separate hosted preview/export test. The four-stop video here was rendered locally with the same checked renderer source and additional numbered image markers. Its files should not be described as a downloaded hosted export.
Scene 04Take 1●
Frame the leg, then check the whole sequence
- Review the first departure and arrival together so the direction is understandable.
- Check all three moving legs. The aircraft should remain visible and should not unexpectedly change model.
- Pause at each destination and confirm that the name and marker remain legible.
- Watch the final frame. Decide whether the viewer needs a longer hold or a separate destination scene.
- Export to the intended aspect ratio and repeat the test on the device where it will be watched.
A symbol that looks clear in a wide frame may become small on a phone. Prefer fewer visible labels or a closer leg view before making the aircraft disproportionately large. Extending the destination pause is usually clearer than making every flight slower.
Scene 05Take 1●
Use the map as a bridge into the memory
After arrival, a photograph, short clip or spoken memory can explain why the destination matters. Keep that material in its own timing budget. The 17-second example contains only the map sequence; it does not include an arrival scene, music, captions or a closing card.
For the transition into another chapter, see the road-trip structure and map handoff. For the wider travel edit, use the travel video with an animated map guide rather than expanding this flight tutorial into another general production checklist.
End card
That’s a wrap
Helpful answers
Frequently asked questions
Is the curved line an actual flight track?
No. It is an illustrative arc between approximate city-centre points. A real track requires a suitable recorded source and a tool that reproduces that track.
Why are four stops needed for three legs?
Each leg joins two consecutive stops: Toronto–Montreal, Montreal–Quebec City and Quebec City–Halifax.
Does the 17-second sample include destination photos?
No. It contains map movement, numbered markers and an aircraft symbol. Add separate time for photos, messages or closing cards.
