This is an old revision of the document!
Click on TIMELINE icon in order to access live flight information. This section is particularly useful for flight-watching, when you want to see the realization of the planned schedule.
FBO's and Users having access to more than one operator can see alll the fleet for all Operators by choosing “All *” in Leon Menu.
As you can see in the screen on the right, there are number of time-filtering options, such as (from the left):
You can also see Reservations added from Planned Flights screen (Purple colour) or Maintenances added from Scheduled Maintenance section (Brown colour or Red if it is AOG Maintenance).
If there is airport discontinuity between airport A and B - a red line will highlight ADEP without continuity with ADES of the last flight.
Right click of the mouse on the flight or an option strip will open a window with access to flight documents as well as Show crew, Show schedule, and Notify Crew functions. This works in exactly the same way as in Calendar and Table sections. CTRL + right click of the mouse on chosen sectors will allow you to print document for these sectors.
Flight Support Companies will have the the Operator Code displayed below the Aircraft registration. The colour of the background is set in Operator Colours section.
On the left you can see the fleet sorted by aircraft registration. The first row represents scheduled flight times. This strip may also include flights added as options - they will be distinguished by striped line. The second row represents the realization of the flight (Flight Watch and later Journey Log data, if entered), which shows only when Flight Watch is filled in.
There are colour codes in terms of data inserted into the Flight Watch:
Once these times are exported to Journey Log and full Journey Log is saved, this lower bar turns grey.
Clicking on any strip allows you to access flight details and edit the flight in the same way as in TABLE, or CALENDAR sections.
In a section SCHEDULE, tab FLIGHT, we have added a new field Rotation - minimum time on the ground needed for unloading & loading the aircraft as well as fueling and cleaning, etc…
The first step to enable this functionality is defining a Default Rotation Time in a section Settings > Flight Editing. Right now that default time is set as 01:00 (which you can over-write to appropriate value).
Once it's defined, when you add a trip (i.e. 3 legs), in a section TIMELINE Leon will show legs where all legs - apart from the first one - have already added flight-times belts. They remain with scheduled times until Flight Watch details are filled in (see example below).
The logic behind this option is to monitor if the current leg is delayed and if time between landing and BLOFF of the next leg exceeds Rotation time. If so, Leon will delay next legs by that difference. Below you can find examples describing possible situations.
The screenshot below shows a case where BLOFF is 09:16 where scheduled STD of the 2nd leg is 12:10. That means that the rotation time defined as 01:00 would be less than this value. That is why Leon “pushed” 2nd leg's flight time bar to 12:16.
By inserting a value EET (Estimated Endroute Time) Leon autimatically calculates ETA. The screenshot below shows a case where EET is 02:00 hence Leon “pushed” 2nd leg's flight time bar to 12:26 taking also into consideration Taxi In time at the GVA airport (which is defined as 00:10). As you can notice, Leon also pushed 3rd leg's flight time bar by 00:01 to 16:16 because the rotation time would not be 01:00.
Leon shows a red bar on the flight times belt if CTOT is filled in in the Flight Watch section.
On the screenshot attached you can see a situation where:
If you add EET to the Flight Watch, Leon will show flight times belt as on the screenshot below: it shows MAD time as 12:40 because of Taxin In at MAD defined as 10 minutes.
In TIMELINE view you have 3 tabs with filtering options: