Plan a VFR cross-country end to end: enter the airports and the aircraft, put checkpoints on the route by name or by clicking the chart, and let the flight computer fill in the course, the heading, the ground speed, the times and the fuel. Confirm what you agree with; it tells you when a figure stops matching its own arithmetic.

Around that: METAR and TAF weather, winds aloft, a terrain profile, controlled airspace and VFR reporting points, a printable sheet, and an export the simulator can load. With an account, a plan you keep follows you to the next machine, and a tour binds many flights into one long journey.

If you would rather see one than plan one, there is a finished nav log — Stockholm-Bromma to Jönköping, already worked through, with one cell deliberately disagreeing with its own arithmetic so you can see what that looks like. Make it mine turns it into an ordinary flight of your own.

• Tours are new. The binder, the outline, marking a flight flown, and calling a tour completed, archived or deleted all work. The travelogue, the per-point notes and photographs do not exist yet, and a journey you have already flown cannot be entered after the fact.
• There is no example flight. The only way to see a finished nav log is to plan one.
• A narrow window chooses for you. The sheet and the map only fit side by side above about 1140 pixels of window width. Narrower than that and the window opens with the sheet alone, the map waiting a click away on the rail — because the sheet would otherwise lose most of its columns to make room. Dragging the divide where you want it is not built yet.

Almost every number here comes from somebody else's freely given data, and how good it is depends entirely on where you are flying. The About page says who each source is; this is what their coverage means in practice.

• Charts. A real VFR chart exists for much of western, central and northern Europe and for the United States. Everywhere else — Spain and the United Kingdom included — you get the worldwide aviation overlay over a plain map, which shows airspace and airfields but is not a chart.
• Reporting points. Published VFR reporting points are loaded per country, and their coverage is best in Europe. A country with none is not an error.
• Airfields. Worldwide, and better for airports than for private strips. A field with no published runway data is drawn differently rather than guessed at.
• Weather. METAR and TAF wherever a station reports them; winds aloft from a global forecast model, so they exist everywhere and are a forecast everywhere.

This is not a sandbox that gets wiped. Your account, the plans you keep and the tours you start are stored the same way they will be after the beta, and settings has both an export of everything and a delete that means it.

When the beta ends, nothing happens to what you have made. Your account stays an account, the plans you kept and the tours you started are kept with it, and nothing that is free today moves behind payment. There is no date at which beta data is cleared, and no migration you have to survive — the beta ending is a label coming off, not an event your work has to get through.

An account keeps one unsaved flight and twenty saved plans. The unsaved one follows you between machines, and two windows can no longer overwrite each other's work — if you see a strip saying a flight is not being saved, that is the application being careful rather than something breaking.

Please do. A beta whose reports do not arrive is just traffic. Report a problem is in the header of every page once you are signed in, and it attaches what we would otherwise have to ask you for: the flight you had open, its route, the page, the build and the browser. You see all of it before it is sent.

It asks for an account because a report is worth more when it can be answered and when the plan it names can be looked at. Without one, info.simnavlog@virtualvoid.se reaches the same person — say what you were doing, what you expected, and the route you were planning.

Corrections to the data are worth sending to the people who publish it, and the About page says how for each source. A wrong runway or a missing airfield fixed upstream is fixed for everyone, in every application.