Differences

This shows you the differences between two versions of the page.

--- leon:flight-documents [2019/04/13 14:32]
+++ leon:flight-documents [2019/04/13 14:45]
rafal [Flight Documents]
@@ Line 1: / Line 1: @@
+====== Flight Documents ======
+[{{ :leon:schedule:Documents menu.png?200|Available flight documents in Leon}}]
+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 'Flight Order' or 'Trip Sheet'. The same applies to 'General Declaration' (if you tick i.e. 5 flights - 5 separate documents will get printed), 'Pax Manifest' or 'Pax Information'.
+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:trip|here]].
+<box>**If the trip is booked from the [[leon:sales|Requests/Quotes]] section, the 'SALES' part of the 'Documents Menu' will NOT be available (will not display). In such case, it will only be possible to print and send the Sales Documents available in the [[leon:sales|Requests/Quotes]] section of Leon.**</box>
+--------------------
+===== Flight Order =====
+[{{ :leon:flights-documents-for-flights:flight-order.png?200|Example of Flight Order document}}]
+'**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' number issued in a particular month, i.e. **6-07-2013** means, that it is the 6th consecutive 'Flight Order' issued in July.
+Flight Order is issued for the **entire trip** (all sectors of the trip) so it does not matter which leg link is used to create the 'Flight Order'.
+'Flight Order' pattern available in Leon is filled in by the data entered in the 'Edit Flight' screen:
+  * Aircraft type & registration
+  * Type of flight
+  * Crew details
+  * Supplementary information
+  * Schedule details
+  * After-flight report (data imported from 'Journey Log')
+The other columns/fields need to be filled in manually:
+  * Crew duties/rest details
+  * Flight order attachments (tick appropriate boxes)
+  * Remarks
+  * COM signature
+<box> If anything regarding the trip is **changed** after 'Flight Order' has been issued, its number will be displayed in red (i.e.<html>
+<span style="color:red;font-size:100%;">8-07-2013</span>
+</html>) to make the dispatcher aware about the changes. Red colour will turn black once the 'Flight Order' is printed again and the page is refreshed.</box>
+===== General Declaration =====
+[{{ :leon:flights-documents-for-flights:general dec.png?200|General Declaration document}}]
+This document lists __inbound and outbound flight details__ and crew names. It is being requested by the __immigration authorities__ at some airports of arrival.
+<box> **In some countries, such as China, General Declaration requires an extra information including: title, gender, passport number & expiry date or nationality. We can add it to your General Declaration sheet, if required. We can also add a General Declaration which contains PAX details** (please email [[support@leonsoftware.com]]).</box>
+The pattern of 'General Declaration' also includes 'Declaration of Health' with the space for notes and signatures along with the general declaration signature signed by PIC. The text can be modified upon request.
+Leon will show **Place of Birth** on GenDec if it has been added into crew profile.
+<box>**GenDec can also be attached to a Handling Requests email by marking a checkbox **Attach GenDec** at the bottom of the HR sheet.**</box>
+===== Trip Sheet =====
+[{{ :leon:flights-documents-for-flights:trip sheet.png?200|Trip Sheet - crew, schedule and checklist items data}}]
+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:documents-setup|Documents Setup]] - **Flight editing** tab - 'On Trip Sheet set "Flight Service Notices" as a separate page'.
+  * **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/landing permissions.
+  * **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.
+If it happens that cockpit crew have **different reporting times**, Leon will show them on Trip Sheet as separate columns (as on the example below).
+{{:leon:flights-documents-for-flights:fdp section on TS.jpg|}}
+===== 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' in the [[leon:phonebook|Phonebook]] before they can be further used in Leon.
+{{ :leon:flights-documents-for-flights:pax info.png?nolink |}}
+If you add passengers information to Leon **manually** (which means you don't use Pax Database added to Leon in the section 'Phonebook > Pax Database') it is still possible to view it on '**Pax Manifest** document.
+[{{ :leon:flights-documents-for-flights:PAX manual input.png?300|Manually added pax data on 'Pax Manifest' document}}]
+Go to [[leon:documents-setup|Documents Setup]] and enable this option by ticking the "Show on Pax Manifest" checkbox (at the bottom of the page).
+If you hover the mouse over the '**?**' the information will show up: '**Show pax list in the text mode on Pax Manifest document. Correct data has to be entered in the format: No. gender surname name date-of-birth passport no. passport
+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/flights in the 1st column, right-click of the mouse and select **Pax Manifest** document to get pax data.
+<box>**Leon will show 'Place of Birth' on 'Pax Manifest' document if it has been added into the passenger's profile.**</box>
+===== Pax Information =====
+[{{ :leon:flights-documents-for-flights:pax information.png?200|Pax Information - flight brief for passengers }}]
+Some operators require an __extra document__ for their passengers with a brief information about the upcoming flight.
+The document includes:
+  * Trip number
+  * Flight information: flight date and aircraft type & registration
+  * Airport information & schedule times
+  * Airport handling details: agents names & phone numbers
+  * Passengers details: for all sectors
+  * Catering provision
+  * Crew information: names, functions & contact phone numbers

Leonsoftware Wiki

User Tools

Site Tools

Differences

Page Tools