Published 10 March 2026, Updated 10 March 2026
This guide explains how front users use the a device, also shown on screen as the Flight record Signature PAD. It is the shared tablet or mobile signature device used to review an activity that is waiting for signatures before it can continue through the normal flight-record process.
The device is not a planning page and it is not the full dispatcher screen. Its job is narrower and simpler:
- show activities that are waiting for PAD action
- let the user open the correct activity
- show the important flight details and aircraft warnings
- collect the required signature or approval on the device
- save that signature and, in some cases, request supervisor PIN authorization
What the device is for
Use this device when someone asks you to sign or acknowledge an activity on the shared PAD. In most cases, this happens before the activity is fully completed in the flight-record workflow.
Depending on the activity type and your organization settings, the PAD may ask for:
- an Instructor and Student signature
- a Pilot in Command signature and a Supervisor or delegate approval
- only one Member signature
Sometimes one of those approvals is already saved before you open the page. In that case, the PAD shows the saved signature instead of an empty signature box.
Before you start
Before using the PAD, make sure you have the right activity and the right people at the device.
You should normally know:
- which flight or activity must be signed
- who is signing on the PAD
- whether a second approval is needed
- whether the organization uses a supervisor PIN instead of a second handwritten signature in some cases
If the aircraft has open warnings or deferred items, read them before signing. The PAD shows those items on purpose so the signer sees them during acknowledgement.
First-time device connection
If the device has not been authorized yet, it cannot open the active list. Instead, it shows a message explaining that the device is not an authorized signature PAD.
[SCREENSHOT: mbfdsv-not-authorized | Capture: Unauthorized PAD message on the home page with the Connect button visible.]
In that case:
- Tap Connect.
- Enter the access code given by a flight records responsible.
- Enter or confirm the device name.
- Review the displayed fingerprint. This is an identification string for the device.
- Tap Connect!
[SCREENSHOT: mbfdsv-connect-page | Capture: PAD sync page showing the Access code field, Device name field, Fingerprint value, and Connect button.]
After that, the device returns to the PAD home page.
Important points:
- The access code must come from a flight-record responsible.
- If the code is wrong, expired, or the organization already reached its allowed number of PAD devices, the connection will not complete correctly.
- If the connection page keeps failing, ask flight records staff to generate a new code or remove an old PAD registration.
Opening the waiting list
Once the device is authorized, the home page shows the company title and a Refresh button.
[SCREENSHOT: mbfdsv-home-list | Capture: Main PAD waiting list page with company title, Refresh button, and the activity list.]
The main page is a waiting list of activities that currently need PAD action. Each row helps you identify the activity before opening it. The exact content varies, but it is designed to help you recognize the correct record quickly.
Use Refresh when:
- you expect a new activity to appear
- someone just signed on another screen
- the list looks outdated
- the connection was interrupted and you want to force a reload
Tap the correct activity row to continue.
[SCREENSHOT: mbfdsv-list-row | Capture: One waiting-list row showing the activity summary a front user uses to identify the correct item before opening it.]
Optional agreement page
Some organizations configure an agreement page before the signature screen opens. If it appears, read the message carefully and then tap:
I agree and I’m ready to acknowledge
[SCREENSHOT: mbfdsv-agreement-page | Capture: Agreement page with the acknowledgement text and the I agree and I’m ready to acknowledge button.]
This step does not save anything by itself. It only moves you to the signature page.
What you see on the signature page
The signature page is designed to give the signer enough context before saving.
1. Exercises section
If exercises are linked to the activity, they appear at the top of the page. This helps the signer confirm the training context before signing.
[SCREENSHOT: mbfdsv-exercises-section | Capture: Signature page exercises section showing exercise items linked to the activity.]
If no exercises are attached, that section may stay empty or be hidden.
2. Activity details
The page shows a compact summary that can include:
- activity type
- lesson title
- number of passengers
- departure point
- arrival point
This is the quick identity check. If these details do not match the activity you expect, stop and go back to the list instead of signing the wrong record.
[SCREENSHOT: mbfdsv-details-section | Capture: Activity details area showing activity type, lesson, passenger count, departure, and arrival.]
3. Resource information and open squawks
The resource section shows the aircraft or other resource involved in the activity. If there are open squawks or maintenance warnings, they appear here with their status.
[SCREENSHOT: mbfdsv-resource-section | Capture: Resource section showing the aircraft or resource identification on the signature page.]
You may see labels such as:
- Warning
- Grounded
- postponed information
- time or maintenance window information
Read these items before signing. They are not decorative. They are shown specifically to make the signer aware of aircraft status at the time of acknowledgement.
[SCREENSHOT: mbfdsv-open-squawks | Capture: Open Squawks area showing warning or grounded items with their explanatory text.]
4. Alert area
If the system has an additional warning message for this activity, it appears in the Alert box.
Treat this area as a final caution message. Read it before you sign.
[SCREENSHOT: mbfdsv-alert-box | Capture: Alert box on the signature page showing an additional warning message to the signer.]
Understanding the signature blocks
The signature area changes depending on the activity type.
Training or ground activities
The two blocks are usually labeled:
- Instructor
- Student
This is the most straightforward case: each person signs in the box assigned to them, unless that signature is already saved.
[SCREENSHOT: mbfdsv-training-signature-layout | Capture: Signature page showing the Instructor and Student signature blocks for a training activity.]
Flights requiring command plus supervision
The blocks are usually labeled:
- Pilot in Command
- Sup or delegate
In this flow, the second approval may be handled in more than one way depending on system setup:
- a saved supervisor approval may already be shown
- the second approval may be entered as a signature
- the second approval may be handled through a unique supervisor PIN instead of a handwritten signature
- the PAD may ask you to select the supervisor or delegate by name first
[SCREENSHOT: mbfdsv-pic-sup-layout | Capture: Signature page showing the Pilot in Command and Sup or delegate blocks.]
Single-member activities
Some activities only require one signer. In that case, the PAD hides the second block and only one signature area remains visible.
[SCREENSHOT: mbfdsv-single-signer-layout | Capture: Signature page layout where only one signer block is visible for a single-member activity.]
Existing signatures and PIN approvals
If a signature was already saved earlier, the PAD shows the saved image instead of an empty signature box.
If an approval was saved by PIN rather than handwriting, the PAD shows a PIN indicator instead of a handwritten signature image.
[SCREENSHOT: mbfdsv-existing-signature | Capture: Signature block showing an already saved handwritten signature image.] [SCREENSHOT: mbfdsv-pin-indicator | Capture: Signature block showing a PIN approval indicator instead of a handwritten signature.]
This means the approval already exists and usually does not need to be drawn again on the PAD.
How to sign on the device
When a signature box is empty, sign directly in the box with your finger or stylus.
[SCREENSHOT: mbfdsv-empty-signature-box | Capture: Empty signature pad ready for a user to sign.] [SCREENSHOT: mbfdsv-signed-box | Capture: Signature pad after a user has drawn a signature.]
Good practice:
- sign inside the visible rectangle
- use one continuous signature rather than short marks
- check the result before saving
The PAD is meant to collect the approval quickly, but you should still make sure the activity details, aircraft warnings, and signer labels are correct first.
When a supervisor or delegate must be selected
In some activities, the second approval is not pre-filled. Instead, the page shows a search field where you can type the name of the supervisor or delegate.
[SCREENSHOT: mbfdsv-sup-search-field | Capture: Supervisor or delegate name search field shown on the signature page.]
How to use it:
- Start typing the person’s name.
- Wait for the suggestion list to appear.
- Tap the correct name from the list.
- Confirm that the picture and displayed name match the right person.
[SCREENSHOT: mbfdsv-sup-search-results | Capture: Supervisor or delegate suggestion list displayed after typing part of a name.] [SCREENSHOT: mbfdsv-sup-selected | Capture: Signature page after the correct supervisor or delegate has been selected from the search list.]
The suggestion list starts working only after you type enough characters, so do not expect results from only one or two letters.
Depending on your setup, you may also see a PIN field such as Enter PIN or or PIN…
[SCREENSHOT: mbfdsv-sup-pin-field | Capture: PIN entry field shown for supervisor approval when the organization uses PIN authorization.]
What a grey signature block means
Sometimes a signature block appears visually greyed out. This means the related person has a blocking issue that the PAD is taking into account, such as a qualification or authorization problem.
[SCREENSHOT: mbfdsv-greyed-signature-block | Capture: Greyed-out signature block indicating a blocked or restricted signer state.]
In practical terms, this means:
- the PAD still shows who the person is
- the block is being marked as restricted
- a mandatory signature may not be accepted there in the normal way
If you see a greyed block and are not sure whether you should continue, stop and check with flight records staff or dispatch.
Saving the activity on the PAD
Use the Save button in the top-right corner when the required signature work on the page is complete.
[SCREENSHOT: mbfdsv-save-button | Capture: Signature page header with the Save button highlighted in the top-right corner.]
What Save does depends on the situation:
- it stores the handwritten signature entered on the PAD
- it preserves already existing signatures that are shown on screen
- in some supervisor-approval cases, it also triggers a supervisor PIN authorization request instead of only collecting a second handwritten signature
Minimum rule before Save
The PAD will not accept a completely empty approval.
At least one approval must exist, for example:
- a pilot or instructor signature
- a student signature
- a supervisor PIN approval already entered
If nothing valid has been entered, the PAD shows an error explaining that at least one signature is required.
[SCREENSHOT: mbfdsv-signature-required-error | Capture: Error popup shown when the user tries to save without any valid signature or approval.]
Back button behavior
Use Back when you opened the wrong record or want to stop before saving.
[SCREENSHOT: mbfdsv-back-button | Capture: Signature or agreement page header with the Back button visible.]
The Back button returns you:
- from the signature page to the agreement page, if your organization uses one
- otherwise back toward the list flow
If the connection to the server has been lost, going back may also force the device to reconnect and reload the list.
Common real-life flows
Example 1: instructor and student both sign
You open a training activity, confirm the lesson and route, read the aircraft warnings, then the instructor signs in the first box and the student signs in the second box. Tap Save when both signatures look correct.
[SCREENSHOT: mbfdsv-example-training-complete | Capture: Training activity example where both Instructor and Student signature boxes are completed and ready to save.]
Example 2: pilot signs and a supervisor PIN is needed
You open an activity that shows Pilot in Command and Sup or delegate. The pilot signs on the PAD. The second approval is handled by supervisor authorization rather than a second handwritten signature. After saving, the system proceeds with the PIN request workflow used by your organization.
[SCREENSHOT: mbfdsv-example-pic-pin | Capture: Example activity where the Pilot in Command signs and the second approval is handled through the supervisor PIN flow.]
Example 3: one approval already exists
You open the activity and notice that one signature is already displayed as an image or PIN symbol. In that case, only the missing signer needs to complete the remaining approval on the PAD.
[SCREENSHOT: mbfdsv-example-one-existing-approval | Capture: Example activity where one approval is already present and only the remaining signer must complete the page.]
Common problems and what to do
| Situation | What it means | What to do |
|---|---|---|
| Device says it is not an authorized PAD | The shared device has not been synchronized yet | Tap Connect and use an access code from flight records staff |
| The waiting list is empty but you expected an activity | The device may be out of date or the activity is not ready for PAD action yet | Tap Refresh and check again |
| You do not see the right second signer | The person may not be pre-assigned or not enough letters were typed in the search field | Type more of the name and select from the suggestions |
| A signature block is greyed out | The PAD sees a blocking issue for that signer | Stop and ask dispatch or flight records staff before continuing |
| Save shows a signature error | Nothing valid was entered yet | Add the required signature or approval and try again |
| The page shows aircraft warnings or grounded status | The resource has open operational or maintenance information | Read it before signing and follow local procedures if the warning blocks the flight |
| The device shows a connection error | The PAD lost contact with the server | Refresh the page; if the problem continues, contact the administrator or flight records staff |
[SCREENSHOT: mbfdsv-connection-error | Capture: Connection error popup shown when the PAD cannot reach the server.]
Good habits
Use the PAD in this order:
- Confirm you opened the correct activity.
- Read the activity details.
- Read the aircraft warnings and alert box.
- Check who is expected to sign.
- Add only the missing signature or approval.
- Save once the page is complete.
Do not sign first and review later. The page is intentionally structured so the details and warnings are seen before the approval is stored.
Quick reminder
The mbfdsv device is a shared signature checkpoint, not a full editing screen. Its purpose is to make sure the right activity is being acknowledged, the signer sees the important operational warnings, and the required signature or supervisor approval is captured in a simple, controlled way.