- Help Center
- Departure/Arrival
- Dispatcher workflow in the Departure/Arrival page
-
General
-
Administration
-
Settings (account & personal)
-
User Management
-
Booking/Scheduling
-
Instructor Workflows
-
Operation Workflows
-
Rental Workflows
-
Reporting
-
Flight Tracking
-
Departure/Arrival
-
Message Center / Document Center
-
Warnings
-
CBTA Pro
-
my|FlightLogger
-
Optional Modules
-
API
-
FlightLogger Referral Program
Using the dispatch warning and blocking function
This article explains what happens when enabling the account setting "Enable warning popup when dispatching"
When using the dispatch function you have an option to let FlightLogger verify the compliance of booked resources before dispatching a flight. If any of the rules are not complied with, FlightLogger will block for dispatching the flight, until the rules are met.
You can choose which rules to verify from based on the following options:
- Block if acknowledgement is missing
- Block if authorization is missing
- Block if maintenance is missing, expired, or requiring approval
- Block if certificates are missing, expired, or requiring approval
- Block if sign off is missing
- Block if flight & duty time are above limitation
- Block if ground school warnings exist
- Block if account balance is below 0
Based on your settings, when clicking the edit icon on a departure booking, a popup appears with a summary of the resources (aircraft, student, instructor, crew, renter).
In case the flight doesn't comply with one or more of the activated rules, the flight is blocked from dispatching and the continue button is then locked.
In the below example the booking cannot be dispatched (could be because student has not acknowledged, has a missing or expired certificate or is missing to sign off a message in the message center).
In this case it is the dispatcher's responsibility to ensure compliance before the booked flight can be dispatched.