There are three required components for every flight – the flight itself, loads, and a payment record for each load. (Some loads may not have a payment record until the flight is completed and uploaded. At that point the record will be created automatically.) Each of these has its own unique record number. Depending on how the flight is requested or created, the process varies slightly for associating all three components. In this lesson we’ll look at creating just the flight. Creating loads and payment records will be covered in separate lessons.
Scheduling Payments and Requested Flights
You can drag and drop a payment or a flight request from the request column to any date and any aircraft at 10 minute time increments on the calendar. The flight length on the calendar corresponds to the length of the flight plus the aircraft’s standard ground time between stops. The flight will be gray with a small D in the upper right corner to indicate the flight’s status is ‘Draft’.
For payments or flight requests with an associated account number or payment record, when you drop the flight, FlightSpan™ Ops will ask whether or not you want to create a manifest. Manifests are explained in more detail here.
If you wish to combine more than one payment or flight request into one flight, drag and drop the additional payment(s) or flight request(s) on top of the first already scheduled flight. FlightSpan™ Ops will ask if you want to add the load to the manifest. You can add the new load to an existing manifest, create a new one, or add the load without a manifest.
FlightSpan™ Ops will combine the flights in the most efficient manner possible. The flight will expand on the calendar to include estimated flight and ground times. In the example below, a flight request from WAJJ-NOI was dragged onto a flight from WAJJ-KAS.
You can override the routing created by FlightSpan™ Ops by clicking on one of the gray arrow icons and dragging the leg up or down.
Note: You are dragging the destination airport to the new position, not the entire route.
If a shorter route exists, a yellow Use Shorter Route button appears on the Schedule Detail page.
In this case, the shorter route would eliminate the training leg from NOI-NOI.
Change the departure time by dragging on the calendar, or from the Schedule Details by editing the departure time on the first leg of the flight.
Hover over the blue information buttons to get basic information about a leg.
Scheduling a Flight from Scratch
Double click on the Scheduling Calendar, and begin adding legs. The default route is home base to home base. Clicking on the Save or Back to home base buttons will open the Schedule Detail page with the date, time, and aircraft where you clicked pre-filled.
Add crew, and click on the pencil icon in the Scheduled Legs section to add crew roles. Click here for more details on crew assignment.
Use the green plus button to add more legs to the route.
Scheduling Training Flights
If local training is required, create a flight or add a leg from the departure point back to the same departure point.
The default setting in FlightSpan™ Ops is for training flights to last six minutes, but from the Aircraft EFB Preferences tab, you can set a different default for each aircraft type.
Using the blue pencil button to edit, you can enter additional flight time and click Save.
Total Flight Time and Leg Time will be replaced, and estimated duty time will be updated.
Additional flight time will be indicated on the Schedule Detail with a plus symbol.