Understand the move from AFSP to FTSP and organize eligibility records, provider responsibilities and training-event checks.
Published by Aloft360, an aircraft management software provider. Editorial standards and corrections
A new student’s TSA record should be checked before the school treats enrollment as complete. The useful questions are specific: does the planned training fall within the program, what eligibility evidence is required, and has the provider completed its own steps?
Older articles often describe the Alien Flight Student Program, or AFSP. TSA now calls it the Flight Training Security Program (FTSP). Its 2024 final rule changed the assessment framework, so an old category-based checklist is not a dependable starting point.
TSA’s FTSP portal explains the transition from event-based assessments to time-based assessments that can cover up to five years. That does not mean every candidate receives five unrestricted years of eligibility. Use the determination and conditions in TSA’s system, including any earlier limit.
Read the current provider guidance alongside 49 CFR Part 1552. A candidate’s assessment is only one part of the provider’s responsibilities. The program also addresses provider registration, security coordination, security awareness training, notifications and records.
An account, payment or lesson booking is not evidence that the student may begin covered training. Assign a responsible person to verify identity and the applicable citizenship or eligibility documentation before the first covered event.
U.S. citizens and U.S. nationals follow the applicable citizenship-verification process. Other candidates, including lawful permanent residents where covered, need the applicable FTSP eligibility process. Do not use residency, a familiar address or an FAA pilot certificate as a substitute for that review.
The scope of “flight training” matters. Avoid a blanket rule that every ground lesson, introductory flight or recurrent activity is treated the same. Consult the current program definitions and TSA guidance for the actual training proposed.
A practical school checklist can identify the following without placing identity documents in a general scheduling calendar:
| Item | What the reviewer should establish |
|---|---|
| Student identity | The records refer to the same person enrolling |
| Training scope | Which FTSP requirements apply to the proposed activity |
| Eligibility evidence | The current determination or verification basis |
| Relevant dates | Issue date, actual expiration and any earlier condition |
| Provider actions | Required notifications and other steps are complete |
| Review record | Who checked the information, when and what needs follow-up |
Store sensitive documents with appropriate access controls. Follow the current retention requirements for each record category; do not assume that a single “five years after training” rule describes every record.
A returning student may have a changed status, a different training objective or a new provider. Review the current record and required provider actions before resuming covered training. A past approval screenshot is not enough to resolve a new question.
Choose a reminder interval that gives staff time to contact the student and complete the review. When something is missing, make the next action explicit: who will obtain it, which training is affected and who can clear the hold. Teach front-desk staff where to find that decision.
Aloft360 has fields for citizenship, a TSA reference, status and dates. Some screens retain the older AFSP label. These are school-maintained records; Aloft360 does not submit an application to TSA or independently determine eligibility.
Read the TSA tracking help for the available fields. Verify required actions in the TSA portal and use the app to keep the school’s follow-up organized. An “Approved” badge reflects the saved entry, not a live determination from TSA.
For a broader student-file review, see Part 61 recordkeeping. Keep FAA training records and TSA eligibility checks distinct so staff know which requirement each record supports.