Dispatch checklists that lock the record
Dispatch is the moment the Pilot in Command accepts the flight. Fleet Centr turns that into a customisable checklist with a declaration and signature, and once it is complete the manifest and loading are locked to everyone except the PIC.
Checklist items customised in company settings
PIC declaration and signature captured on the record
Manifest and loading lock once dispatch is complete
What dispatch covers
Your checklist, not ours
Customise the dispatch checklist items in company settings so it reflects your exposition and the way your operation actually releases a flight.
PIC accepts responsibility
The declaration and signature record that the Pilot in Command warrants the statements are true and the flight has been planned in accordance with company and regulatory requirements.
Locks the manifest and loading
After dispatch, users other than the PIC cannot unlock the flight to edit the manifest or the loading. What was dispatched stays dispatched.
Record keeping by default
The completed checklist stays attached to the flight, so dispatch compliance evidence accumulates without anyone filing anything.
The end of the pre-flight chain
Manifest, then weight & balance, then dispatch. Each step builds on the last and all three hang off the same flight log.
Available over API and MCP
Dispatch data sits alongside the rest of the flight record, so automated compliance checks and reporting can reach it.
Releasing a flight
Dispatch is the gate between planning and flying.
Pre-flight is complete
The flight log exists, the manifest is built, and the weight & balance has been run against the aircraft configuration.
Work the checklist
The PIC works through your dispatch items — airworthiness, weather, manifest and loading, fuel, and flight and duty limits.
Sign and lock
The PIC signs the declaration. The flight is released and the manifest and loading are locked to everyone else.
Dispatch Checklist questions
Yes. Dispatch checklist items are customisable in company settings, so you can align them with your exposition and operating procedures.
Only the Pilot in Command can unlock a dispatched flight. Other users cannot change the manifest or the loading once dispatch is complete.
Yes. The declaration and the PIC signature are stored against the flight, so the evidence that responsibility was accepted stays with the flight record.
No. Flight logs work on their own. Dispatch, manifests, and weight & balance are part of the same Aviation Tools add-on and are there when your operation needs them.
Make dispatch a record, not a ritual
Start the 30-day Operations trial, then add Aviation Tools for dispatch, manifests, weight & balance, and flight logs.