This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Previous revision Next revision Both sides next revision | ||
leon:table [2019/11/22 14:35] |
leon:table [2019/12/19 13:02] rafal [Simulators] |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== TABLE ====== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | The philosophy of working in the section **Table** is to use filters to display desired activities in the middle section of the screen and then modify selected properties of those activities using the right-hand panel. Date range and format of displayed information can be altered using the top bar. By clicking **TODAY** Leon shows current day activities as well as other days. | ||
+ | |||
+ | You can select a number of days for flights view in the drop-down box (top-right corner of the screen), or leave as 'No Limit' to see as many flights as the screen can fit. | ||
+ | |||
+ | The refresh screen icon can be used for manual page refreshing, although Leon refreshes the screen every 2 minutes itself. | ||
+ | |||
+ | You can view flights and positionings duties. Legs of the same trip are marked with the thick, blue line. Positioning duties added from a section Crew > Duties (selected from the bottom of the duties list) also appear in Table. | ||
+ | |||
+ | When adding Positioning duty from Table, it is possible to add it as an option - it will appear in stripes (see screenshot on the right). | ||
+ | |||
+ | Leon will display type of flight by marking **Flight no.** column with the relevant colour. When you hover the mouse over the flight number Leon will show **notes** inserted into a tab **FLIGHT** (both: OPS & SALES). | ||
+ | |||
+ | {{: | ||
+ | |||
+ | You will also see **Aircraft colour** in **ACFT** column - the colour can be defined in a section Settings > Fleet. | ||
+ | |||
+ | If the flight is added as **Ambulance, | ||
+ | |||
+ | |||
+ | **Tip**: when you set the filter to show desired type of information, | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== Editing trip ===== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | If you click {{: | ||
+ | |||
+ | If the selected activity is a flight, the whole trip (series of flights) will open in the bottom window with the selected leg in shaded green. You can edit each column (Flight No., Date, STD/STA or PAX) and modify it. STA field will show an estimated time of arrival based on GCD and the aircraft speed data inserted in its profile (which can be defined in a [[leon: | ||
+ | |||
+ | You can also add a new leg in this section by clicking **+** or delete a leg by clicking{{: | ||
+ | |||
+ | While you are editing a trip in the bottom panel, you can still use the right properties panel to access given sector details and modify them. | ||
+ | |||
+ | Apart from the standard schedule information, | ||
+ | |||
+ | An additional option in Editing Trip panel is possibility of entering **Cargo** value. Switch to Cargo or PAX & Cargo in Settings > Flight Editing section in **Trip edit scheme** drop-down. | ||
+ | |||
+ | ==== Positionings ==== | ||
+ | |||
+ | |||
+ | The transferring of a non-operating crew member from one place to another, at the behest of the operator, is an important thing in aviation industry. In Leon you can add **positioning** duties and assign crew in 2 easy ways. | ||
+ | |||
+ | **Positionings in OPS** | ||
+ | |||
+ | [{{ : | ||
+ | [{{ : | ||
+ | |||
+ | You can add **Positioning** by clicking {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | When a new window shows, enter details such as: | ||
+ | |||
+ | Clicking on **Crew** field allows you to select designated crew member from a drop-down box, or type-in his/her name or a code. | ||
+ | |||
+ | When adding Positioning duty from Table, it is possible to add it as an **Option** - it will appear in stripes, as all options in Leon. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Positioning duties added from a section Crew > Duties (selected from the bottom of the duties list) also appear in Table. | ||
+ | |||
+ | |||
+ | |||
+ | The right-hand filter contains **3** tabs: | ||
+ | |||
+ | * **Checklist** - default items are: Crew aware of flight, crew transport & hotel. You can manually add more items by clicking a button **ADD ITEM**. | ||
+ | * **FTL** - FTL Calculation Summary showing most important FTL regulations displayed in 2 columns: **Limit** & **Actual**. | ||
+ | * **Notes** - an option to insert relevant notes for the particular positioning. | ||
+ | |||
+ | |||
+ | **Multiple Positioning sectors** | ||
+ | |||
+ | {{: | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | |||
+ | To add **multiple** Positioning sectors you have to: | ||
+ | |||
+ | - Click on 'NEW POSITIONING' | ||
+ | - Make sure that {{: | ||
+ | - Click ' | ||
+ | |||
+ | In order to save the **last Positioning**, | ||
+ | |||
+ | < | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Simulators ==== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | To add a new **Simulator** click on {{: | ||
+ | |||
+ | Once a pop-up window shows, fill it in with details such as: Aircraft type, Date, ADEP, ADES, BLOFF, T/O, LDG, BLON, Landings, Crew (CPT and FO), Pilot flying, Approach and Notes. All these details (apart from Notes) must be filled in in order to add SIM duty. | ||
+ | |||
+ | Added SIM duty will appear in OPS views with already filled in Journey Log. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | Added Simulator flight can always be edited and its details can be changed. | ||
+ | |||
+ | In order to **edit** the Simulator, you need to click on it and the pop-up 'Edit Simulator' | ||
+ | |||
+ | |||
+ | ----- | ||
+ | |||
+ | ===== Adding a New Trip ===== | ||
+ | |||
+ | |||
+ | In **OPS** you can add a new trip regardless section you work with: TABLE, CALENDAR or TIMELINE. | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Click button **NEW TRIP** to add 1 or more legs. Select an aircraft, flight number (Leon assign it automatically if ' | ||
+ | |||
+ | In section **CALENDAR** you can also add a new trip by right-clicking the mouse over the square. | ||
+ | |||
+ | [{{: | ||
+ | |||
+ | Buttons **UTC** & **LT** allow to switch between times while adding a new trip. | ||
+ | |||
+ | Leon suggests **STA** if a particular aircraft speed details are added in fleet edition section, using **GCD** and/or average winds. STA suggestion can also be based on minimum 5 same historical routes. | ||
+ | |||
+ | To add more legs to the trip click **+** and to delete a leg click {{: | ||
+ | |||
+ | You can also add a new **positioning**, | ||
+ | |||
+ | **Aircraft max range alert** | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | We have added an alert if the **max range** of the aircraft is exceeded. | ||
+ | |||
+ | In order to get the warning working you need to make sure that the following fields are filled in in the Fleet section: | ||
+ | |||
+ | * **Capacity** | ||
+ | * **Max range with PAX** | ||
+ | * **Max range with 0 PAX** | ||
+ | * **Aircraft speeds** | ||
+ | |||
+ | When adding a flight, Leon will show a max range alert if: | ||
+ | |||
+ | * field ' | ||
+ | * field ' | ||
+ | |||
+ | If the range is exceeded Leon will also mark the aircraft **red** in the OPS view. | ||
+ | |||
+ | ---------- | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== View Settings ==== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Each Leon user can define his **own view** of the schedule list. It is possible to add or remove **columns**, | ||
+ | |||
+ | To access the panel click {{: | ||
+ | |||
+ | === Columns === | ||
+ | |||
+ | Leon allows to add more **columns** to the overall schedule view (apart from the default ones, such as: FW & JL, Flight No., Day, Date, STD, ADEP, ADES, STA, ACFT, PAX, Tags) - click ' | ||
+ | |||
+ | === Colours === | ||
+ | |||
+ | Here you can define if Leon should colour **Flight No.** column and/or **ACFT** column, as well if Leon should dim ferry legs. By marking a checkbox **Entire leg row** Leon will colour an entire row, either with the flight type colour (if ' | ||
+ | |||
+ | === Warnings === | ||
+ | |||
+ | All **warnings** in Leon are displayed in red. Here, you can mark particular (or all) checkboxes and if i.e.:PAX passport is expired, crew FTL violated or crew endorsement is expired - Leon will show PAX number value in red {{: | ||
+ | |||
+ | === Cautions === | ||
+ | |||
+ | Here you can mark checkboxes for particular cautions, i.e.: PAX passport missing, Airport cat B or HIL restriction, | ||
+ | Hover the mouse over the alerted item to see details. | ||
+ | |||
+ | === Notices === | ||
+ | |||
+ | Notices are dislpayed in the Table page in white {{: | ||
+ | Hover the mouse over the alerted item to see details. | ||
+ | |||
+ | === Preferred airport code === | ||
+ | |||
+ | Switch between **ICAO** & **IATA** airport codes to be displayed in the OPS section (Table, Calendar or Timeline). | ||
+ | |||
+ | === Timezone === | ||
+ | |||
+ | Here you can choose if Leon should show STD & STA times in **UTC**, **LT** (at ADEP/ADES airports) or **Base Time** (defined in an user's profile). | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== CAMO limits ==== | ||
+ | |||
+ | Once there has been an aircraft **maintenance** scheduled in Leon (described in [[leon: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Example: current TAH 450:00 TAC 150; Maintenance limits: TAH 480:00 TAC 165; warning margins: TAH 20:00 TAC 10 | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Example: current TAH 470:00 TAC 160; Maintenance limits: TAH 480:00 TAC 165; warning margins: TAH 20:00 TAC 10 | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Example: current TAH 482:00 TAC 167; Maintenance limits: TAH 480:00 TAC 165 | ||
+ | |||
+ | |||
+ | You can check the exact TAH & TAC **details** when you hover the mouse over one of these three icons: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | < | ||
+ | |||
+ | ==== Flight documents ==== | ||
+ | |||
+ | To print **documents** you need to mark particular leg/legs of the trip (in the checkbox) right-click of the mouse and select documents from the list. | ||
+ | |||
+ | |||
+ | Leon allows you to select different flights performed on **the same aircraft** - even if they are not on the same day - to the same ' | ||
+ | |||
+ | Tick flights in the first column on the left, right-click with the mouse (it does not matter where you point the mouse-arrow) and a pop-up window will show up. Select the documents and it will get printed. | ||
+ | |||
+ | If you select only one leg of a multiple-legged trip and right-click with the mouse, you will see 2 available buttons on top: TRIP and LEG. Select LEG to print documents for just that marked leg. | ||
+ | |||
+ | It is also possible to send the documents to CrewBriefing. More information can be found [[leon: | ||
+ | |||
+ | < | ||
+ | |||
+ | ---- | ||
+ | |||
+ | === Flight Order === | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | **Flight Order** is an internal document generated for each trip required by CAA. In Leon, the format of this document can be customised. The Flight Order number looks like a date format, however, its number is a consecutive ' | ||
+ | |||
+ | |||
+ | Flight Order pattern available in Leon is filled in by the data entered while adding a new flight: | ||
+ | |||
+ | * Aircraft type & registration | ||
+ | * Type of flight | ||
+ | * Crew details | ||
+ | * Supplementary information | ||
+ | * Schedule details | ||
+ | * After-flight report (data imported from ' | ||
+ | |||
+ | The other columns/ | ||
+ | |||
+ | * Crew duties/rest details | ||
+ | * Flight order attachments (tick appropriate boxes) | ||
+ | * Remarks | ||
+ | * COM signature | ||
+ | |||
+ | ---- | ||
+ | |||
+ | === General Declaration === | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | This document lists __inbound and outbound flight details__ and crew names. It is being requested by the __immigration authorities__ at some airports of arrival. | ||
+ | |||
+ | |||
+ | The pattern of ' | ||
+ | |||
+ | < | ||
+ | |||
+ | ---- | ||
+ | |||
+ | === Trip Sheet === | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | This document includes basic information about the flight, which is important for the crew and must be acknowledged by the crew before the flight. | ||
+ | |||
+ | 'Trip Sheet' in Leon is divided into two sections: **Trip Sheet** and **Flight Service Notices** - both can be listed either on the same page or on separate pages (this can be set in [[leon: | ||
+ | |||
+ | * **Trip Sheet** - information such as: crew names & functions, FDP details, clients, registration marks and call signs of the aircraft, OPS contact data, flight schedule details, handling agents contact details, fuel info and overflight/ | ||
+ | * **Flight Service Notices** - PAX names, passport numbers & expiry dates, nationality details. Information about PAX catering, transport, special requests, crew HOTAC, crew transport and additional info can also be included. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | === Pax Manifest === | ||
+ | |||
+ | This document shows all **PAX information** including: name & surname, D.O.B., passport no. & expiry date, nationality. All these details need to be entered in the 'Pax Database' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | If you add passengers information to Leon **manually** (which means you don't use Pax Database data added to Leon in the section ' | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Go to [[leon: | ||
+ | |||
+ | If you hover the mouse over the ' | ||
+ | expiry date nationality. Columns have to be separatedd by comma.**' | ||
+ | |||
+ | The below example explains how it works. | ||
+ | |||
+ | * **Add pax details in the 'Legs Info' section** | ||
+ | |||
+ | **1, Surname Name, DoB, Passport No, Date of Expiry, Country of Issue** | ||
+ | |||
+ | for example: | ||
+ | |||
+ | **1, Mr, Smith John, 01-01-2000, ABC1235786, 31-12-2020, U.K.** | ||
+ | |||
+ | The **gender** will be displayed as: | ||
+ | |||
+ | - **M** if inserted as **Mr** | ||
+ | - **F** if inserted as **Mrs**, **Miss** or **Ms** | ||
+ | - **CHD** if inserted as **Child** | ||
+ | - **INF** if inserted as **Infant** | ||
+ | |||
+ | * **Go to Flights List page** - mark appropriate flight/ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | === Pax Information === | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Some operators require an __extra document__ for their passengers with a brief information about the upcoming flight. | ||
+ | |||
+ | The document includes: | ||
+ | |||
+ | * Trip number | ||
+ | * Flight information: | ||
+ | * Airport information & schedule times | ||
+ | * Airport handling details: agents names & phone numbers | ||
+ | * Passengers details: for all sectors | ||
+ | * Catering provision | ||
+ | * Crew information: | ||
+ | |||
+ | If you are sending **OPS documents** Leon will automatically populate e-mail addresses of the Crew assigned to this flight. E-mails are taken from **Work email** in User Profile section. **From** email address is imported from **work email** of the person sending the documents. | ||
+ | |||
+ | |||
+ | |||
+ | ---------- | ||
+ | |||
+ | ==== Journey Log ==== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | In Leon you can add the Journey Log data in **2** ways: | ||
+ | |||
+ | - In the right-hand filter, tab **FW & JL** - here you can add data leg by leg, described in [[leon: | ||
+ | - By using {{: | ||
+ | |||
+ | The 2nd way is useful if a trip has 2,3,4 or more legs, as Leon shows a Journey Log window for the entire trip, where you can easily enter post-flight data leg after leg. If you need more items to be displayed in your Journey Log you can add them in a section Settings > Flight Editing. | ||
+ | |||
+ | Flight times are mandatory to be inserted into the **EDIT LOG** panel for each leg, in order the trip Journey Log to be saved. If you have an option **Allow not completed JL to be entered** switched on in Settings section, you are able to save the Journey Log without **fuel** data (such input appears in the **TABLE** view as an orange dot, instead of green dot). | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Trip changes history ==== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | To check all **changes** done in the trip you need to right-click with the mouse over a selected flight and click a link {{: | ||
+ | |||
+ | In the changes history window Leon shows **chronological** list of all changes (the latest on top). The colours indication shows added data in green, changed data in yellow and removed data in red. | ||
+ | |||
+ | When you click on the changed detail, Leon highlights previous entrances of the same detail. On the screenshot below you can see highlighted STA 15:55, then also 15:43 (previous STA) and 14:42 (initial STA). | ||
+ | |||
+ | {{: | ||
+ | |||
+ | If the flight has been deleted in Leon you can still check its history (as long as the option to keep deleted flights as crossed-out is enabled) in case you want to know who deleted it and when. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Sending documents to CrewBriefing in PPS ==== | ||
+ | [{{ : | ||
+ | |||
+ | It is now possible to upload the documents to PPS directly from the Document Menu in the OPS. | ||
+ | |||
+ | It is possible to send: | ||
+ | [{{ : | ||
+ | |||
+ | * **one particular document** - by clicking on the 'PPS icon' next to the document | ||
+ | * **batch of marked documents** - by marking the documents you would like to send and clicking on the 'PPS icon' by the main section (OPS or SALES) in the document dropdown menu | ||
+ | |||
+ | **The process** of sending the documents is as follow: | ||
+ | |||
+ | - Open the ' | ||
+ | - Choose if you wish to send the documents per TRIP or per LEG. | ||
+ | - Choose the documents you would like to send. | ||
+ | - Click on the relevant 'PPS icon', depending on whether you wish to do that for 1 document or for the bunch. | ||
+ | - A window will pop up with the chosen documents. Click on ' | ||
+ | - Once all send, you should be anle to view them in CrewBriefing in PPS. The documents sent form Leon are merged into a file generated for Crew in CrewBriefing page. | ||
+ | |||
+ | It also is possible to upload files for **multiple trips**. To do so simply mark the trips you would like to send the documents for, open the documents menu and click on the relevant 'PPS icon'. If some of the documents fail to upload, the window will display message as per below | ||
+ | |||
+ | {{: | ||
+ | |||
+ | When sending documents to PPS you have an option between doing it for **First Flight** or **Per Flight**. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **First Flight** will attach all the documents to the first leg of the trip in the CrewBriefing. **Per Flight** option will match the relevant documents to the responding flights in the CrewBriefing | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | --------- | ||
+ | |||
+ | ==== GCR Messages ==== | ||
+ | |||
+ | GCR messages (General Aviation Slot Clearance Request) allow to reserve slots at airports. They use internationally valid format described below. To send a GCR right-click on the flight and select **SHOW SCHEDULE**. In the drop-down box select **GCR**. The content window automatically displays the default information basing on the selected flight. | ||
+ | |||
+ | To send the message you need to add the recepient' | ||
+ | |||
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | < | ||
+ | The GCR message only uses ICAO codes for aircraft and airports and displays UTC times only. | ||
+ | **</ | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | __GCR FORMAT:__ | ||
+ | |||
+ | **GCR** | ||
+ | |||
+ | **/REG** or **/FLT** - aircraft registration or flight number | ||
+ | |||
+ | **EPWA** - airport at which slots are being requested | ||
+ | |||
+ | **N BARTI 02MAR 001F900 0800EPPO P** - flight details: **N** (action code) **BARTI** (flight identification) **02MAR** (date of operation) **001F900** (PAX number + Aircraft type) **0800EPPO** (Origin airport (ICAO) + Scheduled Time of Arrival) **P** (type of flight) | ||
+ | |||
+ | **SI ...** - (optional) additional information in free text | ||
+ | |||
+ | **GI BRGDS** - general information in free text | ||
+ | |||
+ | For an arrival slot, there is NO blank between the action code and the flight identification (**NBARTI**) . The scheduled time of arrival is stated AFTER the airport of origin, without a blank in between. | ||
+ | |||
+ | For a departure slot, there is A BLANK between the action code and the flight identification (**N BARTI**). The scheduled time of departure is stated BEFORE the destination airport, without a blank in between. | ||
+ | |||
+ | The action code defines the exact intention of the GCR message sender and is always at the beginning of the line. | ||
+ | Depending on the sender, the following codes are possible: **N**– New Schedule; **D**– Delete Schedule; **C**– Schedule to be changed; **R**– Revised Schedule. | ||
+ | |||
+ | Flight types: | ||
+ | **D**- General Aviation Flight; **W**- Military Flight; **I**- Air ambulance; **P**- Positioning/ | ||
+ | [{{ : | ||
+ | |||
+ | On the attached screenshots you can find examples of GCR messages. | ||
+ | |||
+ | * **Flights on the same day** - select the airport and Leon will show all flights from/to that airport. | ||
+ | * **Flights on different days** - Leon will show only flights on the next day, omitting the following days. | ||
+ | * **Flights on the following day/days** - when marking 2,3 days (or more) and selecting an airport, if flights are not on the first marked day but on the following day/days - Leon will show flights i.e. on the 2nd marked day omitting the 3rd marked day. | ||
+ | |||
+ | You can find an example of GCR message email in the screenshot on the right-hand side. | ||
+ | |||
+ | |||
+ | |||
+ | If the format of the GCR message is invalid, Leon will highlight the content in red and will show a warning: < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | The default message content can be inserted manually, however, the format still applies. | ||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== SCR Messages ==== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | Format **SCR** (Slot Clearance Request/ Response) can be used by right-clicking with the mouse and selecting **SHOW SCHEDULE**. When a pop-up window appears, you can change the format from 'Plain Text' to SCR. | ||
+ | |||
+ | The message **must** be in the format as on the screenshot - it can not be customized. | ||
+ | |||
+ | **__EXAMPLE__** | ||
+ | |||
+ | **SCR** (type of request) | ||
+ | |||
+ | **W17** (indication of season) | ||
+ | |||
+ | **21DEC** (date of the day) | ||
+ | |||
+ | **LTN** (Airport at which slots are being requested) | ||
+ | |||
+ | **N 124 21DEC21DEC 0000500 011GJ4 1400WAW C** (flight details, see explanation below) | ||
+ | |||
+ | **N** - action code; **123** - flight number; | ||
+ | |||
+ | * W - Military - type ICAO ' | ||
+ | * I - Ambulance Flight - type ' | ||
+ | * T - Technical Test - type ' | ||
+ | * K - Training Flights - type ' | ||
+ | * P - Positioning Flights – Non Revenue (ferry/ | ||
+ | * J - Scheduled – Passenger Normal Service - type ICAO ' | ||
+ | * F - Scheduled – Cargo and/or Mail - type ICAO ' | ||
+ | * H - Charter – Cargo and/or Mail - type ICAO ' | ||
+ | * C - Charter – Passenger only - all other types | ||
+ | |||
+ | **SI** - free text | ||
+ | **GI BRGDS** - free text | ||
+ | |||
+ | It is possible to change type of the action by selecting an appropriate option from the drop-down box: | ||
+ | |||
+ | * N - New Schedule | ||
+ | * D - Delete Schedule | ||
+ | * C - Schedule to be changed | ||
+ | * R - Revised Schedule | ||
+ | * A - Accept an offer | ||
+ | * P - Accept an offer with pending request time | ||
+ | * Z - Decline an offer | ||
+ | |||
+ | Another drop-down box allows to select between **airports**. | ||
+ | |||
+ | < | ||
+ | |||
+ | --------- | ||
+ | ==== Filter - Tab SCHEDULE ==== | ||
+ | This tab is divided into several sections, such as: | ||
+ | * **Show on schedule** - select which type of activities should get displayed: flights, positionings, | ||
+ | * **Group schedule by** - there are 3 ways you can group flights in the table view: | ||
+ | * None - flights will not be grouped and the order they will be sorted by STD | ||
+ | * Day and registration - all flights are grouped by aircraft registration and then sorted by STD | ||
+ | * Day and trip - all flights are grouped by trip number and then sorted by STD (typical OPS setting) | ||
+ | * **Flight type** - select which type of flights should be displayed. | ||
+ | * **Commercial type** - option to see either ' | ||
+ | * **Flight status** - shows confirmed and/or not confirmed flight (options), or opportunity (to sell the flight). | ||
+ | * **Show** - you can narrow your view by excluding ferry, cancelled, journey log or flight watch. Unticking the **' | ||
+ | * **Preferred airport code** - select ICAO or IATA codes to be displayed. | ||
+ | * **Preferred time zone** - select UTC, LT or Base Time to be used. | ||
+ | |||
+ | |||
+ | ==== Filter - Tab MORE ==== | ||
+ | |||
+ | * **Days** - select which day of the week you want activities to be displayed on the list. | ||
+ | * **ICAO type** - denotes the type of flight as follows: **S** for Scheduled Air Service, **N** for Non-scheduled Air Transport Operation, **G** for General Aviation, **M** for military flights and **X** for everything else. | ||
+ | * **Flight number** - search for specific a flight number.Minimum 3 characters required. | ||
+ | * **Trip number** - search by a trip number. Minimum 3 characters required. | ||
+ | * **Airport** - allows you search for flights TO and FROM a specific Airport. Leon will suggest ICAO/IATA when you insert the name. You can also filter flights by FIR codes (i.e. EP* for all flights To/From Poland or EG* for England). | ||
+ | * **Client** - allows you to search for flights made for specific client. If you start typing Leon will suggest Client' | ||
+ | * **Crew member** - searches for flights where indicated Crew member was assigned to.It also possible to filter by **multiple crew members**. Simply choose the crew from the Crew Member search box and once you have the list of crew click ' | ||
+ | * **Tags** - allows to search for tagged flights. | ||
+ | |||
+ | ---- | ||
+ | ==== Aircraft ==== | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | |||
+ | **Aircraft** panel allows to define for which tails Leon should show flights in a section OPS. On the options-bar click {{: | ||
+ | |||
+ | Use ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | ----- | ||
+ | |||
+ | ===== Integrations ===== | ||
+ | |||
+ | Leon is integrated with numerous **partners** in order to automate the process of **data exchange**. | ||
+ | |||
+ | Leon can send your **empty legs** and **aircraft avalibility** to different online platforms allowing to reach more customers for your charter flights. | ||
+ | We have partnered with: **Avinode**, | ||
+ | |||
+ | Leon can export flight data for further **flight preparation**. We also closely cooperate with [[http:// | ||
+ | |||
+ | We are integrated with **IFS** (International Flight Support), which allows to automatically log flight figures into **post flight** database in Leon. | ||
+ | |||
+ | Pilots can export their flights into **logbook** software: **MccSuppoort** or **Coradine**. | ||
+ | |||
+ | Leon can export post flight data to **CAMP** (airframe, engines and APU) for further maintenance tracking in CAMP. | ||
+ | |||
+ | Import of **movements** can be automatically imported into flight watch module from **Eurocontrol**. | ||
+ | |||
+ | You can order various services within Leon like handling, catering or fuel through **MyHandling**, | ||
+ | |||
+ | Leon is also integrated with **AC-U-KWIK** - worldwide airport and FBO / Handler data. | ||
+ | |||
+ | An on-line quoting & scheduling can be done with a help of **SchedAero**, | ||
+ | |||
+ | < | ||
+ | |||
+ | ---- | ||
+ | |||
+ | **See also**: | ||
+ | |||
+ | * [[leon: | ||
+ | * [[leon: | ||
+ | |||