TSA AFSP compliance for flight schools training non-U.S. citizens. What 49 CFR Part 1552 requires, the approval and renewal process, and what to track per student.
If your flight school trains non-U.S. citizen student pilots, federal law requires you to participate in the TSA Alien Flight Student Program. That's true whether you're Part 61 or Part 141, and regardless of the student's visa status or country of origin.
The penalties are real. Training a non-citizen before TSA approval is received carries civil penalties up to $10,000 per violation, and the TSA has pursued enforcement against schools where the breach was inadvertent. The deciding factor isn't intent. It's whether you have a system that prevents the breach from happening in the first place.
This walks through what AFSP actually requires, the approval and renewal process, and the records every school needs to maintain.
AFSP lives in 49 CFR Part 1552. It's administered by TSA and applies to flight training providers — which means you, as the school. The three requirements are simple to state and harder to enforce in practice:
The regulation splits training into two categories:
Most flight schools live in Category 2. The check is faster, but "training before approval" is exactly as illegal in Category 2 as in Category 1.
The regulation applies to any non-U.S. citizen seeking flight training. U.S. citizens and U.S. nationals are exempt. Everyone else is in scope:
The green card surprise catches a lot of schools. A student with a green card has been a U.S. resident for years, has a U.S. address, has a U.S. medical, and feels like a citizen for every other purpose. Under AFSP, they're not. Approval is required.
The student applies through TSAFlightStudent.com:
The critical detail: the school's confirmation is separate from the student's. The student showing you their copy is not sufficient. You need the school-side confirmation visible in your AFSP account before training begins.
Per non-citizen student:
Records have to be retained for five years after training completes.
Initial approval is the obvious checkpoint. Renewal is where schools quietly drift out of compliance. The student finishes their initial program, takes a break, comes back six months later for an instrument rating, and nobody catches that the original approval has expired.
A spreadsheet doesn't reliably catch this. The expiry date sits in column F and nobody looks at column F until something goes wrong. Real compliance means three things:
If you can't see all three working in your current process, you're one staff change away from a compliance incident.
Aloft360's TSA/AFSP tracking covers each of these — citizenship status, case number, approval status, approval date, and expiry are first-class fields with admin alerts ahead of expiration. The states where this is most critical (FL, AZ, OK, ND) have dedicated breakdowns in our per-state guides for context.
The regulation is unambiguous. You may not provide flight training to a non-U.S. citizen before TSA approval is received. Civil penalty: up to $10,000 per violation.
A few clarifications schools sometimes get wrong:
"We didn't realize" is not a defense. The TSA has prosecuted inadvertent cases.
Audit:
Process forward:
A few things AFSP doesn't cover but tend to matter for the same population of students:
AFSP is a federal floor. Your insurance and your state may add additional checks on top.
Verify approval before training begins. Track the approval and its expiration. Maintain records for five years. Doing those three things consistently across every non-citizen student is the entire compliance story. Doing them with a system that alerts on expiry instead of relying on someone remembering is the difference between "compliant" and "lucky so far."
For related reading: FAA Part 61 record-keeping requirements, the best flight school management software, and the Florida flight school landing page for the state with the highest concentration of AFSP students.