Can movement times be filled in automatically in Flight Watch?
Yes, movement times (off-block, takeoff, landing, on-block) can populate automatically from integrated sources such as Eurocontrol or connected EFB/flight-tracking systems. Manually entered times always take precedence, and any automatic source can be limited if it interferes with your reporting times.
Can Leon send MVT (movement) messages automatically?
Yes, MVT messages can be generated and sent automatically to configured recipients when movement times are recorded in Flight Watch. The message layout follows the standard MVT format and can carry your operator identification; if branding elements duplicate (for example two logos), the template needs a one-time correction by Support.
Why are EB (estimated block) timings present in some MVT messages and missing in others?
MVT content depends on which times exist in Flight Watch at the moment of sending, so a missing element means the corresponding time had not been recorded for that flight. Ensure the relevant times are filled (manually or by integration) before the message is triggered.
Are ASM messages sent when an aircraft is changed?
ASM (Ad-hoc Schedule Message) generation depends on your scheduled-messaging configuration, and only changes covered by the configured triggers produce a message. If an aircraft change did not generate an ASM, verify that equipment-change events are included in your ASM trigger set and that the flight belongs to a schedule covered by the messaging setup.
Can Leon export the schedule as a SSIM file?
Yes, Leon can produce SSIM schedule exports for scheduled operations. For a correct export, flights must carry proper flight-level attributes (service type, commercial flags) — schedules grouped into multi-day trips may need restructuring so each flight keeps its own attributes.
Why does an automatic movement update change the crew reporting time?
When movement data arrives from an external source, dependent times recalculated from it can shift — including reporting times derived from STD/ETD rules. If external movement data should not affect crew reporting, restrict the integration scope (for example CTOT only) or fix reporting times manually on affected duties.