Flight system

[Unknown98]

There will be either a time limit or a miles limit. Not sure which one to use yet.

My plan was for the time to be local departure time at the origin airport. So if your route starts in Paris and you put 8am start time, when you click "fly" or whatever the route will become "active" so to speak and once it turns 8am in Paris the route will start flying. So if it's 10am and you start at 8am, the route won't fly until the next morning.

[USA]

I'd say a time limit so it can be somewhat comparable between short and long haul flights. My question is how this will work with in terms of scheduling the next flights up. Meaning after the JFK-CLT leg are you going to be able to set a departure time for the CLT-ATL leg and will there be some sort of turnaround expectation? So is it just going to be automatic (no ground time), a set time per aircraft type (no customization), or are people going to be able to set a ground time in which case what will that number be compared to do determine likelihood that the next flight leaves on-time, etc.?

[Unknown98]

I was just going to have it automatically calculate the departure time for the rest of the legs. Turnaround times would depend on aircraft type. Then later on down the road once we start to think about delays and such maybe I can set up a feature that lets you decide how much extra turnaround time to add to all of the flights on the route as a buffer.

That's the plan anyway. I didn't know how much automation we want to try and implement so I figured this is probably a good start.