This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
leon:mx-fleet [2019/04/17 13:03] bartek [Oil Consumption] |
leon:mx-fleet [2022/11/18 06:44] rafal [Next maintenance due] |
||
---|---|---|---|
Line 2: | Line 2: | ||
- | [{{ : | ||
- | The difference between | + | In this panel Leon shows all aircraft |
+ | |||
+ | The filter allows | ||
+ | |||
+ | [{{ : | ||
+ | [{{ :leon:mx-fleet: | ||
+ | |||
+ | Leon converts values into decimal with a **pattern**: | ||
+ | * 00-03:59 min = 0.0 | ||
+ | * 04-09:59 min = 0.1 | ||
+ | * 10-15:59 min = 0.2 | ||
+ | * 16-21:59 min = 0.3 | ||
+ | * 22-27:59 min = 0.4 | ||
+ | * 28-33:59 min = 0.5 | ||
+ | * 34-39:59 min = 0.6 | ||
+ | * 40-45:59 min = 0.7 | ||
+ | * 46-51:59 min = 0.8 | ||
+ | * 52-57:59 min = 0.9 | ||
+ | * 58-59:59 min = 1.0 | ||
- | **Aircraft status** - to change, it go to Settings > Fleet and open drop-down box **Status** at the bottom of the screen. | ||
- | By clicking on any tail you have access to **2** tabs. | + | By clicking on a particular |
===== Documents ===== | ===== Documents ===== | ||
- | Here you can see **all documents** assigned only to the particular registration. You can add documents **details** (number, date of issue, expiry date, notes) as well as add **scan** of the document (pdf max. of 12MB). | ||
- | The list of documents can be defined in a section [[leon: | + | [{{ :leon:mx-fleet:general-view.png? |
+ | Here you can see **Fleet documents** assigned to the particular registration. You can add documents **details** (number, date of issue, expiry date, notes) as well as add **scan** of the document (pdf max. of 12MB). | ||
+ | |||
+ | The list of documents can be defined in a section [[leon: | ||
+ | ---- | ||
===== CAM ===== | ===== CAM ===== | ||
- | < | ||
- | Here you can define such values for each aircraft, as: | + | Here you can define such values for aircraft |
* **Start date** - the date of the first flight. | * **Start date** - the date of the first flight. | ||
Line 28: | Line 46: | ||
* **Start TAC** - total number of accumulated cycles. | * **Start TAC** - total number of accumulated cycles. | ||
- | The filter allows you to view flights with/ | ||
- | [{{ : | ||
- | [{{ : | ||
- | Leon converts values into decimal with a pattern: | ||
- | * 00-03:59 min = 0.0 | ||
- | * 04-09:59 min = 0.1 | ||
- | * 10-15:59 min = 0.2 | ||
- | * 16-21:59 min = 0.3 | ||
- | * 22-27:59 min = 0.4 | ||
- | * 28-33:59 min = 0.5 | ||
- | * 34-39:59 min = 0.6 | ||
- | * 40-45:59 min = 0.7 | ||
- | * 46-51:59 min = 0.8 | ||
- | * 52-57:59 min = 0.9 | ||
- | * 58-59:59 min = 1.0 | ||
Line 70: | Line 73: | ||
**Example** - if APU start TAH was 100:00 then after one sector APU was 01:00 - you should add in your Journey Log into APU field a total value of 101:00 as it needs to be the summary value (start APU + sector one). | **Example** - if APU start TAH was 100:00 then after one sector APU was 01:00 - you should add in your Journey Log into APU field a total value of 101:00 as it needs to be the summary value (start APU + sector one). | ||
- | If **APU** Hours input in [[leon:journey-log|Journey Log]] are lower than the value from previous JL or the minimum value indicated in Settings > Fleet, Leon will show the warning: | + | If **APU** Hours input in [[leon:fw-jl|Journey Log]] are lower than the value from the previous JL or the minimum value indicated in Settings > Fleet, Leon will show the warning: |
< | < | ||
<span style=" | <span style=" | ||
</ | </ | ||
+ | |||
+ | ------------------------ | ||
+ | ==== Next maintenance due ==== | ||
+ | [{{ : | ||
+ | In the **Limits** subsection, it is possible to insert the limits for the next maintenance. | ||
+ | |||
+ | This subsection contains 3 fields: | ||
+ | |||
+ | * **TAH** - TAH limit of the next required maintenance | ||
+ | * **TAC** - TAC limit of the next required maintenance | ||
+ | * **Date** - date of the next required maintenance | ||
+ | |||
+ | Based on the values inserted in the abovementioned fields, Leon will check planned and performed flights against the limits, as per below: | ||
+ | |||
+ | * if all fields are empty, the limits aren't changed | ||
+ | * if the ' | ||
+ | * if the ' | ||
+ | |||
+ | In addition, the 'Next maintenance due' limits will overwrite ' | ||
+ | [{{ : | ||
+ | __**EXAMPLE**__ | ||
+ | |||
+ | Based on the first screen, the date of the limits is set to 01-12-2022 with the TAH value set to 4835:00 and the TAC value set to 2343. | ||
+ | |||
+ | The scheduled maintenance is planned for 29-11-2022 with the higher limits of TAH value set to 4850:00 and TAC value set to 2350. | ||
+ | |||
+ | Calculated TAH/TAC limits on 24-11-2022 are as per below: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | When adding the flight on 24-11-2022 and considering the dates and limits set in the Fleet and Scheduled Maintenance, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The calculations are based on more restrictive limits from 29-11-2022, as per below: | ||
+ | |||
+ | * **TAH** - 4875:27 - 40:27 = 4835:00 | ||
+ | * **TAC** - 2346 - 3 = 2343 | ||
+ | |||
------------------------- | ------------------------- | ||
Line 99: | Line 141: | ||
* **Journey Log input** | * **Journey Log input** | ||
- | In [[leon:operator-settings|Settings]] > **Flight Editing** | + | In [[leon:flight-editing|Flight editing]] section |
In your Journey Log you will get a new field **Oil uplift** where you can add oil consumption data for engines and APU (see sreenshot). | In your Journey Log you will get a new field **Oil uplift** where you can add oil consumption data for engines and APU (see sreenshot). |