User Tools

Site Tools


leon:fw-jl

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
leon:fw-jl [2021/03/25 14:01]
rafal [Importing MVT Messages]
leon:fw-jl [2024/02/01 08:33] (current)
rafal [Flight Watch]
Line 7: Line 7:
 ===== Flight Watch ===== ===== Flight Watch =====
  
-[{{ :leon:schedule-fw:Flight watch - d1.png?200|Flight Watch data entrance panel}}]+[{{ :leon:flight-flight-watch:fw_-_update_with_history.png?200|Flight Watch data entrance panel}}]
  
 By clicking on FW & JL column Leon opens the tab in the right-hand side filter. If there is no Journey Log added Leon opens FW tab. If there is a Journey Log added (even if it is partly filled in) Leon opens JL tab. By clicking on FW & JL column Leon opens the tab in the right-hand side filter. If there is no Journey Log added Leon opens FW tab. If there is a Journey Log added (even if it is partly filled in) Leon opens JL tab.
Line 13: Line 13:
 FW contains several fields where you can input details such as: FW contains several fields where you can input details such as:
  
 +  * {{:leon:icons:notes-history.png?nolink|}} - this button, located in the top-right corner of the FW tab, allows accessing the FW history
   * **CTOT** - calculated takeoff time - if it is the only detail added to FW in Flights List Leon shows  **S**.   * **CTOT** - calculated takeoff time - if it is the only detail added to FW in Flights List Leon shows  **S**.
-  * **ETD** - estimated time of departure - if added to FW Leon shows **D**.+  * **ETD** - estimated time of departure - if added to FW Leon shows **D**. ETD will be automatically removed in case STD is changed by more than 1 hour, unless BLOFF or T/O is entered
   * **BLOFF** - block off time - if added to FW Leon shows **A**.   * **BLOFF** - block off time - if added to FW Leon shows **A**.
   * **T/O** - take off time - if added to FW Leon shows **A**.   * **T/O** - take off time - if added to FW Leon shows **A**.
-  * **EET** - estimated endroute time (T/O + EET should equal ETA. i.e. T/O 12:00, EET 02h30m, so ETA should be 14:30). The value is diaplyed in the format:HHhMMm, i.e. 12h15m.+  * **EET** - estimated enroute time (T/O + EET should equal ETA. i.e. T/O 12:00, EET 02:30, so ETA should be 14:30). The value is displayed in the format HH:MM, i.e. 02:15.
   * **ETA** - estimated time of arrival.   * **ETA** - estimated time of arrival.
   * **LDG** - landing - if added to FW Leon shows **+**.   * **LDG** - landing - if added to FW Leon shows **+**.
   * **BLON** - block on time - if added to FW Leon shows **+**.   * **BLON** - block on time - if added to FW Leon shows **+**.
 +  * **TTO** - Target Time Over an aerodrome or a point on the route of flight.
 +  * **TOBT** - Target Off-Block Time - the time that an aircraft operator / handling agent estimates that an aircraft will be ready to start up / push back immediately after receiving ATC clearance.
 +  * **TAXITIME** - The average taxiing time for the runway in use at the airport of departure, used to calculate take-off times from the off-block times.
 +  * **REGUL+** - the identifier of the most penalising regulation imposed on the flight. 
 +  * **REGCAUSE** - the reason for the most penalizing regulation imposed on the flight. 
   * **Pax** - number of passengers.   * **Pax** - number of passengers.
   * **DIV** - diversion - insert the code of the airport to which the flight was diverted.   * **DIV** - diversion - insert the code of the airport to which the flight was diverted.
   * **Cargo** - cargo weight.   * **Cargo** - cargo weight.
   * **Delay** - delay code and the delay time can be inserted (the format: code/delay i.e. 14/0010 where 0010 means 00:10 minutes) - if added to FW Leon shows **D**.   * **Delay** - delay code and the delay time can be inserted (the format: code/delay i.e. 14/0010 where 0010 means 00:10 minutes) - if added to FW Leon shows **D**.
 +  * **Confirmation of data correctness** - with Cew App in mind, this checkbox can only be selected by the CPT who certifies that all above details are inserted correctly
   * **Notes** - add notes which can be read by OPS or crew.   * **Notes** - add notes which can be read by OPS or crew.
 +  * **Internal notes** - additional notes for internal use that are not included in the MVT Messages. The 'Internal notes [FW]' column is available in the Report Wizard > scope 'Flight'
  
 [{{ :leon:schedule-fw:FW - date4.png?nolink|Date input in the Flight Watch}}] [{{ :leon:schedule-fw:FW - date4.png?nolink|Date input in the Flight Watch}}]
Line 33: Line 41:
  
 At the bottom of the panel Leon will show information **"Last modified by"** showing Eurocontrol or SITA and UTC time of the change.  For manual changes Leon will show user's name/surname and UTC time of the change. At the bottom of the panel Leon will show information **"Last modified by"** showing Eurocontrol or SITA and UTC time of the change.  For manual changes Leon will show user's name/surname and UTC time of the change.
 +
 +Additionally, the following **Flight Watch progress indicators** are displayed in the 'Table' view:
 +
 +  * {{:leon:schedule-fw:fw_-_bloff_ind.png?nolink|}} - BLOFF inserted
 +  * {{:leon:schedule-fw:fw_-_to_ind.png?nolink|}} - T/O inserted
 +  * {{:leon:schedule-fw:fw_-_ldg_ind.png?nolink|}} - LDG inserted
 +  * {{:leon:schedule-fw:fw_-_blon_ind.png?nolink|}} - BLON inserted
 +
  
 <box> **Details such as BLOFF, T/O, LDG and BLON can be copied to Journey Log by clicking {{:leon:schedule:copy.png|}} in the tab JL** </box> <box> **Details such as BLOFF, T/O, LDG and BLON can be copied to Journey Log by clicking {{:leon:schedule:copy.png|}} in the tab JL** </box>
Line 58: Line 74:
  
 **Movement messages** can be imported to Leon if they are being sent to email address [[mvt@leon.aero]] and if they are in one of the below formats: **Movement messages** can be imported to Leon if they are being sent to email address [[mvt@leon.aero]] and if they are in one of the below formats:
- 
-  * SITA format message 
-  * SATCOM format message 
  
  
Line 66: Line 79:
  
 <html> <html>
-<span style="color:red;font-size:150%;">Departure message format</span>+<span style="color:red;font-size:100%;">Departure message format</span>
 </html> </html>
  
Line 78: Line 91:
   * **ACREG** - aircraft registration number   * **ACREG** - aircraft registration number
   * **STN** - departure airport (in this case it is London Stansted)   * **STN** - departure airport (in this case it is London Stansted)
-  * **AD1200/1300** - actual departure. BLOFF at 1200, airbourne at 1300+  * **AD1200/1300** - actual departure. BLOFF at 1200, airborne at 1300
   * **EA1600** - estimated arrival time. There have to be spaces before EA and after 1600   * **EA1600** - estimated arrival time. There have to be spaces before EA and after 1600
   * **AMS** - arrival airport (in this case it is Amsterdam)     * **AMS** - arrival airport (in this case it is Amsterdam)  
Line 87: Line 100:
  
 <html> <html>
-<span style="color:red;font-size:150%;">Arrival message format</span>+<span style="color:red;font-size:100%;">Arrival message format</span>
 </html> </html>
  
Line 101: Line 114:
  
 ------ ------
-=== SATCOM format ===+=== Satcom Direct - 1-st format ===
  
 __Takeoff Report__ and __Landing Report__ messages imported to Leon need to be in **specific formats**. Once such messages are received they will be automatically added to '**Flight Watch**' in Leon (**BLOFF when Takeoff Report sent and BLON when Landing Report sent**). See the example of the flight below. __Takeoff Report__ and __Landing Report__ messages imported to Leon need to be in **specific formats**. Once such messages are received they will be automatically added to '**Flight Watch**' in Leon (**BLOFF when Takeoff Report sent and BLON when Landing Report sent**). See the example of the flight below.
  
 <html> <html>
-<span style="color:red;font-size:150%;">Takeoff Report format</span>+<span style="color:red;font-size:100%;">Takeoff Report format</span>
 </html> </html>
  
-**subject**+**Subject:** ''Takeoff Report for AC-REG''
  
-Takeoff Report for AC-REG+**Message**:
  
-**message**: +<code>Takeoff Report
- +
-Takeoff Report+
  
 Off Time: 11-Jun-2013 0700 UTC / 11-Jun-2013 0900 LCL Off Time: 11-Jun-2013 0700 UTC / 11-Jun-2013 0900 LCL
Line 123: Line 134:
 Destination Airport: LIRA - CIAMPINO Destination Airport: LIRA - CIAMPINO
  
-ETA 11-Jun-2013 0800 UTC / 11-Jun-2013 1000 LCL+ETA 11-Jun-2013 0800 UTC / 11-Jun-2013 1000 LCL</code>
  
 <html> <html>
-<span style="color:red;font-size:150%;">Landing Report format</span>+<span style="color:red;font-size:100%;">Landing Report format</span>
 </html> </html>
  
-**subject**:  +**Subject**: ''Landing Report for AC-REG''
- +
-Landing Report for AC-REG+
  
-**message**: +**Message**: 
  
-Landing Report+<code>Landing Report
  
 On Time: 11-Jun-2013 1000 UTC / 11-Jun-2013 1200 LCL On Time: 11-Jun-2013 1000 UTC / 11-Jun-2013 1200 LCL
Line 141: Line 150:
 Departure Airport: LIML - LINATE Departure Airport: LIML - LINATE
  
-Destination Airport: LIRA - CIAMPINO+Destination Airport: LIRA - CIAMPINO</code>
 ------------------- -------------------
 +
 +=== Satcom Direct - 2-nd format ===
 +The second format of the Satcom Direct MVT message is an updated version of the first one, with a slightly changed layout and graphical content added. The **[** and **]** brackets represents graphical elements of a message (images) added automatically by the service.
 +
 +<html>
 +<span style="color:red;font-size:100%;">Takeoff Report format:</span>
 +</html>
 +
 +**Subject:** ''Takeoff Report for AC-REG''
 +
 +**Message:** 
 +
 +<code>[Satcom Direct Logo]
 +[Title Image]
 +Takeoff Report for AC-REG
 +[Tracker Image]
 +[Flight Progress]
 +ETA: 10-Feb-2021 23:31 UTC
 +Off Time:
 +10-Feb-2021 1503 UTC / 10-Feb-2021 1603 LCL
 +Departure Airport:
 +LZIB - M.R. STEFANIK
 +Destination Airport:
 +VRMM - VELANA INTL
 +ETA: 10-Feb-2021 2331 UTC / 11-Feb-2021 0431 LCL
 +[SD Pro (logo)]</code>
 +
 +<html>
 +<span style="color:red;font-size:100%;">Landing Report format:</span>
 +</html>
 +
 +**Subject:** ''Landing Report for AC-REG''
 +
 +**Message:**
 +
 +<code>[Satcom Direct Logo] 
 +[Title Image] 
 +Landing Report for AC-REG 
 +[Tracker Image] 
 +[Flight Progress] 
 +ETA: 20-Feb-2021 15:14 UTC 
 +On Time: 20-Feb-2021 1508 UTC / 20-Feb-2021 2008 LCL 
 +Departure Airport: UAKK - KARAGANDA 
 +Destination Airport: VRMM - VELANA INTL 
 +[SD Pro (logo)]</code>
 +------
 +
 +=== Satcom Direct - 3-rd format ===
 +
 +<html>
 +<span style="color:red;font-size:100%;">Takeoff Report format:</span>
 +</html>
 +
 +**Subject:** ''ACREG OFF LSGG 02/25 1010Z 1110LCL''
 +
 +**Message:**
 +
 +<code>ACREG OFF LSGG 02/15 1010Z 1110LCL 
 +OFF RPT 
 +DEP:: LSGG - GENEVA 
 +DEST:: LEST - ROSALIA DE CASTRO 
 +ETA: 02/15 1201Z 1401LCL 
 +FUEL: 10000 </code>
 +
 +<html>
 +<span style="color:red;font-size:100%;">Landing Report format:</span>
 +</html>
 +
 +**Subject:** ''ACREG ON LEST 02/15 1202Z 1402LCL''
 +
 +<code>ACREG ON LEST 02/15 1202Z 1402LCL 
 +ON RPT 
 +DEP: LSGG - GENEVA 
 +DEST: LEST - ROSALIA DE CASTRO 
 +FUEL: 5600 </code>
 +------
  
 === ACARS format === === ACARS format ===
Line 150: Line 235:
 Below you can find appropriate formats which should be used. Below you can find appropriate formats which should be used.
  
-  * **OFF REPORT extended version**+<html> 
 +<span style="color:red;font-size:100%;">OFF REPORT extended version</span> 
 +</html>
  
-Subject: A-BCDE OFFRP (where A-BCDE is acft reg number)+**Subject:** ''A-BCDE OFFRP (where A-BCDE is acft reg number)''
  
-To: mvt@leon.aero+**To:** ''mvt@leon.aero''
  
-**Content**+**Content:**
  
-10-JUN-2015 15:00:00+<code>10-JUN-2015 15:00:00
  
 OFF EVENT REPORT OFF EVENT REPORT
Line 172: Line 259:
 FUEL ON BOARD: 0430 FUEL ON BOARD: 0430
  
-ETA: 1554+ETA: 1554</code>
  
-  * **OFF REPORT simplified version**+<html> 
 +<span style="color:red;font-size:100%;">OFF REPORT simplified version</span> 
 +</html>
  
-Subject: A-BCDE OFFRP (where A-BCDE is acft reg number)+**Subject:** ''A-BCDE OFFRP (where A-BCDE is acft reg number)''
  
-To: mvt@leon.aero+**To:** ''mvt@leon.aero''
  
-**Content**+**Content:**
  
-A-BCDE OFF REPORT+<code>A-BCDE OFF REPORT
  
 ORIG: WAW ORIG: WAW
Line 188: Line 277:
 DEST: AMS DEST: AMS
  
-TIME: 1456+TIME: 1456</code>
  
-  * **IN REPORT extended version**+<html> 
 +<span style="color:red;font-size:100%;">IN REPORT extended version</span> 
 +</html>
  
-Subject: A-BCDE INRP (where A-BCDE is acft reg number)+**Subject:** ''A-BCDE INRP (where A-BCDE is acft reg number)''
  
-To: mvt@leon.aero+**To:** ''mvt@leon.aero''
  
 **Content** **Content**
  
-10-JUN-2015 16:00:00+<code>10-JUN-2015 16:00:00
  
 IN EVENT REPORT IN EVENT REPORT
Line 210: Line 301:
 IN TIME: 1610 IN TIME: 1610
  
-FUEL ON BOARD: 0470+FUEL ON BOARD: 0470</code>
  
-  * **IN REPORT simplified version**+<html> 
 +<span style="color:red;font-size:100%;">IN REPORT simplified version</span> 
 +</html>
  
-Subject: A-BCDE INRP (where A-BCDE is acft reg number)+**Subject:** ''A-BCDE INRP (where A-BCDE is acft reg number)''
  
-To: mvt@leon.aero+**To:** ''mvt@leon.aero''
  
 **Content** **Content**
  
-A-BCDE IN REPORT+<code>A-BCDE IN REPORT
  
 ORIG: WAW ORIG: WAW
Line 228: Line 321:
 TIME: 1600 TIME: 1600
  
-FOB: 0470+FOB: 0470</code> 
 +------
  
 +=== Honeywell GDC format ===
  
 +<html>
 +<span style="color:red;font-size:100%;">Takeoff Report format:</span>
 +</html>
 +
 +**Subject:** ''[Departed]: ACREG OFF at 12:22Z, VRDA > OMDW''
 +
 +**Message:** 
 +
 +<code> Departure Report 
 + Tail Number ACREG 
 +Status Departed 
 +Departure Airport VRDA - MAAFARU INTL 
 +Departed at 07-Feb-2021 12:22 UTC 
 + 07-Feb-2021 17:22 (05:22 PM) Local 
 +Arrival Airport OMDW - DUBAI/AL MAKTOUM INTL 
 +ETA 07-Feb-2021 15:59 UTC 
 + 07-Feb-2021 19:59 (07:59 PM) Local 
 +Fuel on board 18730 lbs 
 + 8494 kgs 
 +Reported Time 07-Feb-2021 12:22 UTC </code>
 +
 +<html>
 +<span style="color:red;font-size:100%;">Landing Report format:</span>
 +</html>
 +
 +**Subject:** ''[Landed]: ACREG ON at 16:01Z,VRDA > OMDW''
 +
 +**Message:**
 +
 +<code> Landing Report 
 + Tail Number ACREG 
 +Status Landed 
 +Departure Airport VRDA - MAAFARU INTL 
 +Departed at 07-Feb-2021 12:22 UTC 
 + 07-Feb-2021 17:22 (05:22 PM) Local 
 +Arrival Airport OMDW - DUBAI/AL MAKTOUM INTL 
 +Arrived at 07-Feb-2021 16:01 UTC 
 + 07-Feb-2021 20:01 (08:01 PM) Local 
 +Fuel on board 9070 lbs 
 + 4113 kgs 
 +Reported Time 07-Feb-2021 16:02 UTC </code>
  
 <box> The format of the 'subject' & 'message' **MUST** be always the same, which means, that if you add anything to the text in either 'subject' or 'message' format, the message **WILL NOT** get imported into the 'Flight Watch'.</box> <box> The format of the 'subject' & 'message' **MUST** be always the same, which means, that if you add anything to the text in either 'subject' or 'message' format, the message **WILL NOT** get imported into the 'Flight Watch'.</box>
Line 249: Line 385:
 If the Operator ICAO code in the section Settings > General Settings tab is the same as registered with Eurocontrol, the integration will be completed upon saving changes. If the ICAO code in Leon doesn't match the one registered with Eurocontrol, you will see an error message saying "Operator ICAO not recognized by Eurocontrol". If the Operator ICAO code in the section Settings > General Settings tab is the same as registered with Eurocontrol, the integration will be completed upon saving changes. If the ICAO code in Leon doesn't match the one registered with Eurocontrol, you will see an error message saying "Operator ICAO not recognized by Eurocontrol".
  
-When the integration is completed, **Flight Watch** in Leon will start receiving flight times from Eurocontrol servers. You will recognise them by opening a Flight Watch and hovering the mouse over the time value, as shown in the screenshot above. Eurocontrol will only send Takeoff, EET, ETA and Landing times plus PAX number.+Operator's ICAO designator must be included in the flight plan's item 7 (Aircraft Identifier), or item 18 (Other Information), sub-field OPR/. In the second case, no other remarks should be added in the OPR/ sub-field, besides ICAO designator. 
 + 
 +If your flight numbers in Leon are based on IATA codes instead of ICAO codes, fill the IATA code field in General Settings.  
 + 
 +When the integration is completed, **Flight Watch** in Leon will start receiving flight times from Eurocontrol servers. You will recognise them by opening a Flight Watch and hovering the mouse over the time value, as shown in the screenshot above. Eurocontrol will only send CTOT, ATD, EET, ETA, ATA times and REGCAUSE  plus PAX number.
 ===== Journey Log ===== ===== Journey Log =====
  
Line 284: Line 424:
   * **Uplift** - fuel value before the takeoff. It is possible to select a unit in which you would like to insert the uplift. The default uplift unit can be selected in [[leon:fleet-setup|Fleet]] setup section.   * **Uplift** - fuel value before the takeoff. It is possible to select a unit in which you would like to insert the uplift. The default uplift unit can be selected in [[leon:fleet-setup|Fleet]] setup section.
   * **Uplift density (kg/L)** - inserted by default depending on the fuel type (JET A-1 - 0.81556862 kg/L and AVGAS - 0.69559241 kg/L).   * **Uplift density (kg/L)** - inserted by default depending on the fuel type (JET A-1 - 0.81556862 kg/L and AVGAS - 0.69559241 kg/L).
-  * **Pilot flying** - insert a pilot's code who has performed the trip. If a captain has done takeoff and a first officer has done the landing, insert both codes in the format: CPT/FO. 'Pilot flying' field is used to calculate crew currency (explained in more details [[leon:crew-currency|here]]). +  * **Pilot flying** - insert a pilot's code who has performed the trip. If a captain has done takeoff and a first officer has done the landing, insert both codes in the format: CPT/FO. The 'Pilot flying' field is used to calculate crew currency (explained in more detail [[leon:crew-currency|here]]). 
-  * **Approach** - there are different types of approaches available: ILS cat I, ILS cat II, ILS cat III, GPS, VOR or NDB, Visual, PNB, RNP AR.+  * **Pilot monitoring** - option to insert the code of a monitoring pilot. If different crews were monitoring the take-off and the landing, both crew codes should be inserted in the format CREW1/CREW2. The 'Pilot monitoring' field is included to calculate crew currency for monitoring pilots (explained in more detail [[leon:crew-currency|here]]). 
 +  * **Approach** - there are different types of approaches available: ILS cat I, ILS cat II, ILS cat III, RNP (LNAV/VNAV, LNAV, AR, LPV), GPS, GLS, LDA, PAR, LOC, VORNDB, SRA, Visual, PNB, EFVS-A or EFVS-L.
   * **Approach type** - types available are: LVO, Precision, Non-precision, Visual, 2D, 3D, CDI and AZI   * **Approach type** - types available are: LVO, Precision, Non-precision, Visual, 2D, 3D, CDI and AZI
-  * **HUD/EVS** - Head Up Display/Enchanced Vision System approach. +  * **HUD/EVS** - Head Up Display/Enhanced Vision System approach. 
-  * **Discretion** - if there was FDP extension due to Commander's Discretion, mark this checkbox, then if you edit crew member's FTL Sheet in a column 'CD' you will see how much time beyond permitted FDP was used as the Commander's Discretion extension.+  * **Discretion** - if there was an FDP extension due to Commander's Discretion, mark this checkbox, then if you edit crew member's FTL Sheet in a column 'CD' you will see how much time beyond permitted FDP was used as the Commander's Discretion extension.
   * **Custom Code** - you can apply one of the following codes: **F** for total time for 'Ferry flight', **T** for total time for 'Training flight', **X** for total time for 'Check flight', **M** for total time for 'Maintenance' / 'Reposition' and **P** for total time for 'Passenger flight'. Once a letter is inserted in the 'Custom code' field then the data from the flight is used accordingly in 'Reports' > 'Flight statistics' > 'Fleet Statistic' report. Only one code can be used per one flight. It is also possible to insert a random code which the can be visible in the Report Wizard > 'Flight' scope and well as filter by it ('Include/Exclude Custom Code')   * **Custom Code** - you can apply one of the following codes: **F** for total time for 'Ferry flight', **T** for total time for 'Training flight', **X** for total time for 'Check flight', **M** for total time for 'Maintenance' / 'Reposition' and **P** for total time for 'Passenger flight'. Once a letter is inserted in the 'Custom code' field then the data from the flight is used accordingly in 'Reports' > 'Flight statistics' > 'Fleet Statistic' report. Only one code can be used per one flight. It is also possible to insert a random code which the can be visible in the Report Wizard > 'Flight' scope and well as filter by it ('Include/Exclude Custom Code')
 +  * **SAFA Ramp Check** - SAFA to European Programme regarding the performance of ramp inspections on aircraft used by third country operators (SAFA)
 +  * **COR/ MOR Completed** - Company Occurrence Report / Mandatory Occurrence Report
   * **Notes** - add notes for OPS or other departments.   * **Notes** - add notes for OPS or other departments.
   * **Rest Facility** - select the one used for the augmented crew - Leon then will increase MAX FDP. You can define options for RF in section Settings > Flight Editing as well as per an aircraft in section [[leon:fleet|Fleet]].   * **Rest Facility** - select the one used for the augmented crew - Leon then will increase MAX FDP. You can define options for RF in section Settings > Flight Editing as well as per an aircraft in section [[leon:fleet|Fleet]].
Line 295: Line 438:
   * **Instrument Time** - time in the air spent flying by IFR. When rule I-IFR is set in OPS > FLIGHT tab, data input shows flight time (it can be over-written). If V-VFR is set - Instrument time needs to be entered manually. Instrument Time cannot be longer than Flight Time.   * **Instrument Time** - time in the air spent flying by IFR. When rule I-IFR is set in OPS > FLIGHT tab, data input shows flight time (it can be over-written). If V-VFR is set - Instrument time needs to be entered manually. Instrument Time cannot be longer than Flight Time.
   * **TAH & TAC** - total aircraft **hours & cycles**. Leon shows data ONLY if every single JL has been filled in for particular aircraft. In brackets, there are TAH displayed in **decimals restricted to one space after a comma**, i.e. 10969:43 (10969.7).   * **TAH & TAC** - total aircraft **hours & cycles**. Leon shows data ONLY if every single JL has been filled in for particular aircraft. In brackets, there are TAH displayed in **decimals restricted to one space after a comma**, i.e. 10969:43 (10969.7).
-  * **Engine rate** - numeric values of thrust set for take-off (if there was full available thrust set, or any derates used).+  * **Engine rate** - numeric values of thrust set for take-off (if there was full available thrust set, or any derates used). 
 +  * **Fuel delivery note** - text input field 
 +  * **Fuel invoice number** - text input field 
 +  * **Restricted Take Off Weight/Actual Landing Weight/Planned Landing Weight/Minimum Sector Fuel ** - fields related to the W&B of the aircraft 
 +  * **Cost center** - text input field to insert either project number or the cost center from the accountancy software 
 +  * **Price of uplift** - field allowing inserting the amount and selecting the currency 
 +  * **Fuel provider** - dropdown allows selecting the Fuel provider. The Fuel provider list in the dropdown is fed from the Fuel providers available at the ADEP in the 'FUEL' tab
   * **Upload files** - PDF and graphics files can be dragged and dropped to this section.   * **Upload files** - PDF and graphics files can be dragged and dropped to this section.
-  * **Status** - includes two selection options ('Open' and 'Closed') which allows closing the JL or keeping it open+  * **Status** - includes two selection options ('Open' and 'Closed') which allow closing the JL or keeping it open
  
 <box>**All enabled fields in Journey Log are also available when adding JL in Leon mobile app. Pilots can also add JL when in offline mode.**</box> <box>**All enabled fields in Journey Log are also available when adding JL in Leon mobile app. Pilots can also add JL when in offline mode.**</box>
leon/fw-jl.1616680872.txt.gz · Last modified: 2021/03/25 14:01 by rafal