Can a Journey Log be corrected after it has been filled in?
Yes, users with the appropriate permissions can edit a filled-in Journey Log, and every change is tracked. Be aware that corrections may affect downstream data such as crew logbooks, FTL calculations, and reports, which recalculate from the updated values.
Can we choose which fields appear in the Journey Log?
Yes, the Journey Log is configurable — optional fields (for example Instrument time, fuel uplift details) can be enabled or disabled per operator. Contact Leon Support or your administrator to adjust the JL field set.
Can fuel uplift be recorded in a different unit (litres instead of kilograms)?
Yes, fuel units in the Journey Log are configurable, and uplift can be entered in litres, kilograms, or other supported units with automatic conversion using the configured fuel density. Ask your administrator to change the default unit if needed.
Why is data missing from the Journey Log section?
Journey Log entries depend on data flowing from Flight Watch, integrations, or manual entry, so missing values usually mean the source (for example an EFB integration or crew input in the Crew App) has not delivered them yet. Check whether the flight's Flight Watch data is complete and whether the responsible crew member has submitted their JL.
Can the Journey Log be closed or finalized via the API?
No, there is currently no dedicated GraphQL mutation to close or finalize a Journey Log — the API allows opening and updating JL data, but final closure is done in the application. If your integration requires this capability, raise it with Leon Support as a development request.