This actually fits Dispatch Pro well as a workflow/compliance feature, rather than Dispatch Pro itself maintaining a TSA “No-Fly List.”
The regulatory basis is real: TSA's Twelve-Five requirements apply to certain scheduled/charter operations using aircraft with a maximum certificated takeoff weight over 12,500 lbs, and federal law provides for passenger information to be compared against federal watch/no-fly lists.
For a Jira feature request, I would frame it as TSA Passenger Vetting / No-Fly Clearance, because ideally Dispatch Pro sends the required information to the appropriate vetting process and records the result rather than storing a copy of a government watch list.
How I picture it working in Dispatch Pro
When a customer has the feature enabled, Dispatch Pro could determine whether TSA vetting is required based on the aircraft assigned to the request.
For example:
Aircraft configuration
TSA Vetting Required: Yes/No
Aircraft MTOW
Possibly a customer-configurable rule for which aircraft/mission types require vetting
Once an applicable aircraft is assigned, Dispatch Pro could automatically flag the request:
⚠ TSA VETTING REQUIRED
The dispatcher would then need the required identifying information for each person being transported. Depending on TSA's required interface/data elements, this could include things such as:
Full legal name
Date of birth
Gender
Other TSA-required identifying information
For medical transport, I would make this work with the patient and any accompanying passenger/escort. Crew could potentially be handled separately depending on the operator's TSA program.
The important part: clearance status
Dispatch Pro could display a simple status on the request:
TSA Vetting
⚪ Not Required
🟡 Required – Information Missing
🔵 Submitted / Pending
🟢 Cleared
🔴 Not Cleared / Review Required
⚠️ Error – Unable to Verify
That status should be visible from the main dispatch screen so the dispatcher doesn't have to open several tabs to figure out whether the flight can proceed.
I would also consider an optional customer setting that prevents the request from progressing to a configurable status such as Departed until all required individuals have received clearance.
Integration would make this really useful
The best implementation would be an integration rather than someone manually checking a list.
Conceptually:
Dispatch Pro → TSA-approved vetting process/provider → Result → Dispatch Pro
Dispatch enters the patient/passenger information once. DSP submits what's required, receives the response, and records the clearance status.
I would not suggest storing an actual TSA No-Fly List inside Dispatch Pro. Federal law describes the government performing the comparison against the relevant watch lists, which makes an integration/verification workflow a much cleaner model.
It also avoids exposing sensitive watch-list information unnecessarily.
Audit trail
This could be especially valuable for compliance. DSP could automatically record:
TSA Vetting Submitted — 14:32 Passenger Cleared — 14:33 Verified by: B. Fosse Aircraft: N123AB
That information could become part of the request history and potentially be available for reporting/auditing.
Problem this feature would fix: Air medical and other aircraft operators utilizing aircraft over 12,500 pounds may be subject to TSA security and passenger-vetting requirements. Dispatch centers need a reliable way to identify when vetting is required, collect the necessary passenger information, track clearance, and ensure required vetting is completed before the aircraft departs.
The Twelve-Five Standard Security Program applies to certain scheduled or charter operations using aircraft with a maximum certificated takeoff weight greater than 12,500 pounds. Federal law also provides a process for individuals associated with certain charter operations to be compared against federal watch/no-fly lists.
Proposed Dispatch Pro functionality: Allow aircraft to be configured as requiring TSA passenger vetting. When one of these aircraft is assigned to a request, Dispatch Pro would automatically flag the request as TSA Vetting Required.
Dispatch Pro would collect the required identifying information for the patient and any applicable passengers/escorts and, where technically available, submit that information through an approved TSA vetting integration or third-party provider.
The request would display a clear vetting status such as Information Missing, Pending, Cleared, Not Cleared/Review Required, or Error.
Customers could optionally configure Dispatch Pro to prevent a request from advancing to a specified operational status until all required individuals have been successfully cleared.
All submissions and results would be recorded in the request history, including date/time, person vetted, result/status, aircraft, and user/system action.
Benefit: This would bring TSA compliance into the normal Dispatch Pro workflow instead of requiring communication specialists to maintain a separate process outside the CAD. It would reduce the risk of a required vetting step being missed, provide dispatchers with immediate visibility of clearance status, and create an auditable record of the process.
Created CAD-6766 on this idea. If you have any other questions, please reply here.
This actually fits Dispatch Pro well as a workflow/compliance feature, rather than Dispatch Pro itself maintaining a TSA “No-Fly List.”
The regulatory basis is real: TSA's Twelve-Five requirements apply to certain scheduled/charter operations using aircraft with a maximum certificated takeoff weight over 12,500 lbs, and federal law provides for passenger information to be compared against federal watch/no-fly lists.
For a Jira feature request, I would frame it as TSA Passenger Vetting / No-Fly Clearance, because ideally Dispatch Pro sends the required information to the appropriate vetting process and records the result rather than storing a copy of a government watch list.
How I picture it working in Dispatch Pro
When a customer has the feature enabled, Dispatch Pro could determine whether TSA vetting is required based on the aircraft assigned to the request.
For example:
Aircraft configuration
TSA Vetting Required: Yes/No
Aircraft MTOW
Possibly a customer-configurable rule for which aircraft/mission types require vetting
Once an applicable aircraft is assigned, Dispatch Pro could automatically flag the request:
⚠ TSA VETTING REQUIRED
The dispatcher would then need the required identifying information for each person being transported. Depending on TSA's required interface/data elements, this could include things such as:
Full legal name
Date of birth
Gender
Other TSA-required identifying information
For medical transport, I would make this work with the patient and any accompanying passenger/escort. Crew could potentially be handled separately depending on the operator's TSA program.
The important part: clearance status
Dispatch Pro could display a simple status on the request:
TSA Vetting
⚪ Not Required
🟡 Required – Information Missing
🔵 Submitted / Pending
🟢 Cleared
🔴 Not Cleared / Review Required
⚠️ Error – Unable to Verify
That status should be visible from the main dispatch screen so the dispatcher doesn't have to open several tabs to figure out whether the flight can proceed.
I would also consider an optional customer setting that prevents the request from progressing to a configurable status such as Departed until all required individuals have received clearance.
Integration would make this really useful
The best implementation would be an integration rather than someone manually checking a list.
Conceptually:
Dispatch Pro → TSA-approved vetting process/provider → Result → Dispatch Pro
Dispatch enters the patient/passenger information once. DSP submits what's required, receives the response, and records the clearance status.
I would not suggest storing an actual TSA No-Fly List inside Dispatch Pro. Federal law describes the government performing the comparison against the relevant watch lists, which makes an integration/verification workflow a much cleaner model.
It also avoids exposing sensitive watch-list information unnecessarily.
Audit trail
This could be especially valuable for compliance. DSP could automatically record:
That information could become part of the request history and potentially be available for reporting/auditing.
Jira Feature Request
I would write the core idea something like this:
Title: TSA Passenger Vetting / No-Fly Clearance Workflow
Problem this feature would fix:
Air medical and other aircraft operators utilizing aircraft over 12,500 pounds may be subject to TSA security and passenger-vetting requirements. Dispatch centers need a reliable way to identify when vetting is required, collect the necessary passenger information, track clearance, and ensure required vetting is completed before the aircraft departs.
The Twelve-Five Standard Security Program applies to certain scheduled or charter operations using aircraft with a maximum certificated takeoff weight greater than 12,500 pounds. Federal law also provides a process for individuals associated with certain charter operations to be compared against federal watch/no-fly lists.
Proposed Dispatch Pro functionality:
Allow aircraft to be configured as requiring TSA passenger vetting. When one of these aircraft is assigned to a request, Dispatch Pro would automatically flag the request as TSA Vetting Required.
Dispatch Pro would collect the required identifying information for the patient and any applicable passengers/escorts and, where technically available, submit that information through an approved TSA vetting integration or third-party provider.
The request would display a clear vetting status such as Information Missing, Pending, Cleared, Not Cleared/Review Required, or Error.
Customers could optionally configure Dispatch Pro to prevent a request from advancing to a specified operational status until all required individuals have been successfully cleared.
All submissions and results would be recorded in the request history, including date/time, person vetted, result/status, aircraft, and user/system action.
Benefit:
This would bring TSA compliance into the normal Dispatch Pro workflow instead of requiring communication specialists to maintain a separate process outside the CAD. It would reduce the risk of a required vetting step being missed, provide dispatchers with immediate visibility of clearance status, and create an auditable record of the process.
Hello. I do not understand what you are requesting. Will you please provide more details?
Susan