Today the logger watches your flight and files the report. Next we want to put the rest of the airline around you: a cabin crew you can talk to, a dispatcher who answers, slots to make and delays to explain. An aeroplane with people in it.
And none of it compulsory. If you want to load up, fly, and have the sector logged with nothing interrupting you, that is exactly what you will get. This page is where you tell us which of it is worth building.
One switch, and everything below is off. The logger does what it does today: watches the flight, scores it, files the report, says nothing.
Crew on the interphone, dispatch on the radio, a slot to make and a delay to answer for. As much of it as you want, and only what you switch on.
Not a list of features: the moments they would actually happen in. Every one of these is optional on its own, and none of them can take a point off you. None of it is air traffic control, either. Clearances, levels and routings stay between you and whoever is controlling, on the network or in the sim.
50 pilots have voted. The order here decides what gets built.
The vote here says what we should build. The part we cannot get from a vote is how you want it to work, and that is the part that decides whether it is any good. Every idea on this list has a thread of its own in the 2.0.0 forum on our Discord: say how you would want to use it, what would annoy you, what we have got wrong.
Your feedback is what this is built on. Tell us how you would like to see these ideas actually work.
Open the 2.0.0 forumThe people behind you, and what you say to each other.
Cabin secure. Service complete. A passenger who is unwell. A door that has not armed. Short, timed to what is actually happening on your aircraft, and never while you are busy on the approach.
Tell the cabin to stow and be seated, and the service stops where it was. Tell them it is over and it resumes. The passengers notice both, and so does the report.
A cabin crew you can actually speak to, from the flight deck: ask for the cabin to be secured, ask how the passengers are, tell them to hold the service. They answer in the airline language, in the voice they already have.
The pre-flight briefing an airline actually does: passenger count, anything loaded that you should know about, expected turbulence, when the crew would like to run the service. Two minutes at the gate, skippable.
A passenger taken ill, an overhead bin that will not close, a broken seat. Not emergencies for the sake of it: the ordinary cabin problems that make a captain choose between carrying on and doing something about it.
It kills the immersion when a Purser announces the safety briefing and all other cabin announcements associated with a passenger flight. Could the JSV Logger be programmed to elimenate these announcements during cargo and charter flights? Or at the very least, have a toggle on/off feature to be able to stop the announcments from occuring.
The company on the other end of the radio.
The airline talking to you rather than the other way round: the weather turning at destination, a gate change, a slot, a suggestion to take more fuel. Text you can read when you have a moment, not a pop-up over the flight director.
Company messages that arrive the way they do on a real flight deck rather than in a chat box: uplinks you read, acknowledge and file. Where you are flying on a network that has real controllers and real CPDLC, the logger stays out of their way and never speaks to ATC for you.
The last figures, sent to the aircraft the way they are on the line: final passengers and bags, the weights, the trim. Late changes arrive as a revision, which is exactly when they arrive in real life.
Ensure that the phases of groundhandling match with GSX
Ask the company for more fuel, a second look at the weather, an opinion on the destination or whether to carry the extra alternate, and get an answer that means something. The answer is grounded in the flight you are actually on: the plan, the weather and the aircraft. What to do about it with ATC is still yours.
Destination below minima, the alternate closing, a hold you cannot afford. Ask the company and get a re-clearance with the fuel figures behind it, and the paperwork follows the decision.
Tell dispatch where you are going and why, get handling and a stand at the other end, and have the report record the whole conversation as the reason. The diversion already works; this is the part where somebody knows about it.
When booking your flight, it should remember your aircrafts and airline preference instead of updating it every time
This kind of calls into company ACARS messaging, but I know a lot of outstation personnel are rarely directly connected to it. Usually when close to their destination, the pilot calls the company ops frequency on the ground, telling them how far out they are, relaying anything of importance, requests, and asking for any changes like gates, etc.
Dispatch always builds the flight plan for you in SimBrief. Pilots who have already built their own OFP, or who fly an add-on aircraft with an airframe profile that our dispatch does not offer, have to throw that plan away and take the generated one. The ask is an import: paste a SimBrief flight ID, or pull the pilot's latest plan from their SimBrief account, and attach it to the booking as the briefing for the flight.
Being somewhere at a time, and what happens when you are not.
Boarding, fuelling, catering, loading, pushback approval: each with a duration you can watch and, when something is late, a reason. The turnaround stops being a countdown and starts being a sequence.
A calculated take-off time with a window either side of it, handed to you by the company when the network is busy and your route says so. Nothing is said to a controller on your behalf: it is a time to be ready by, and the turnaround and the crew work back from it.
Going out late, and getting it back.
A quicker turnaround, catering skipped, boarding closed early, an aircraft swap. What the airline can do about a late departure, which is a real part of the job and nothing in the sim currently notices. Anything that belongs to a controller stays with the controller.
Go out late and your next departure is under pressure, exactly as it would be. The roster already carries the slack; this makes it visible while you are still flying, and lets you see the moment you have got it back.
Every delay carries an IATA code and a cause, from the stand to the report. The roster already does this for a duty; 2.0.0 brings it to the single flight and to everything the company does around it.
The promises that make the rest of it safe to build.
Immersion is set on the flight, not on the account, so a long-haul on a free evening can have the full company around it and a quick sector after work can have none of it. The setting travels with the flight and can be changed at any point.
Everything below is optional. One switch turns the whole of it off and the logger goes back to what it does today: it watches the flight, scores it and files the report, and nothing ever interrupts you. This is the promise the rest of 2.0.0 is built against.
A pilot who never opens the message centre finishes the flight with exactly the same score as one who answers everything. Immersion may earn recognition of its own, but it will never be a way to lose what you have.
Me and my friends would love to fly twith the Animawings A320/A220 and with A321/330 from Hisky. These are the most famous low cost carriers in Romania. Thank you and hope you will see our ideea.
Allow members to purchase a small plane or fly GA flights in a "free" mode. Perhaps reduce or don't count the hours towards airline credit hours. I don't know how complicated this would make things.
What the rest of it stands on.
Everything interactive has to survive a dropped connection the way the logger already does, holding what it could not send and carrying on. If immersion breaks the flight when the wifi drops, it is not worth having.
The crew and the company can speak, in the languages the cabin already has, or stay silent and write. Set once, changed whenever, and the choice is per channel: a talking purser and a written dispatcher is a perfectly reasonable way to fly.
A message centre in the app that holds the cabin, the company and the ground on one screen, with a clear unread mark and nothing that steals focus. Everything above arrives here.
Every idea is read by a human. The ones that go on the list carry your name, and get a thread in the Discord 2.0.0 channel to be picked apart.
Sign in to add an idea, so we can credit it to you and come back to you about it. Reading the list needs nothing at all.
Sign in Join JetStream VirtualThe build goes to test pilots at the end of October, two or three weeks before it is released. You fly your normal flights on it and tell us what is wrong. It is the real app, your flights count as usual, and you can go back to the released version whenever you like.
Sign in to volunteer Join JetStream VirtualNothing here is a promise except the first one: whatever we build, Just Fly keeps working.
Vote for everything you would use, argue about it in the 2.0.0 channel on Discord, and send in what is missing. Votes are only counted here, so it stays one pilot one vote.
What gets built is what you voted for, against what is honestly buildable by November. Whatever does not make it is published, with the reason.
Work happens on the 2.0.0 branch, and every committed item has an issue on the tracker you can follow.
The build goes to the test pilots. Your flights count as usual, and what they find is what stops it going out broken.
Put your name down →Released the way 1.13.0 was: the app updates itself, and the release notes say plainly what changed.