The TSA Commuting Fairness Act directs the TSA Administrator to produce a feasibility study on treating the time employees spend traveling between their regular duty locations and airport parking lots or bus and transit stops as on‑duty hours. The study must evaluate operational, technological, and cost considerations that would follow if that travel time were reclassified.
This is a narrow, implementation‑focused bill: it does not change pay rules directly but forces TSA to analyze whether such a change is workable and what it would cost — including whether those hours should count as basic pay for retirement. For compliance officers and payroll managers, the study’s findings could trigger significant changes to timekeeping, payroll systems, collective‑bargaining discussions, and retirement accounting if the agency moves forward on any reclassification.
At a Glance
What It Does
The bill requires the TSA Administrator to deliver a written feasibility study within 270 days examining whether to treat travel time between regular duty locations and airport parking lots and bus/transit stops as on‑duty hours. The report must be submitted to the House Committee on Homeland Security and the Senate Committees on Commerce, Science, and Transportation and on Homeland Security and Governmental Affairs.
Who It Affects
Directly affects TSA employees who work at airport locations — most immediately frontline screening officers and other on‑site staff who commute to airport parking or public transit. It also implicates TSA human resources and payroll units, agency budget offices, and employee representatives/collective‑bargaining units.
Why It Matters
Reclassifying commute‑adjacent travel as on‑duty would change timekeeping and could increase payable hours, overtime exposure, and retirement crediting, producing both recurring personnel costs and one‑time IT and administrative expenses. The study’s findings will shape whether the agency pursues policy or collective‑bargaining changes that affect operations nationwide.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Act does one thing: it orders a feasibility study and sets a short delivery clock. The study’s immediate task is technical — measure how long TSA employees take to travel between their assigned work locations and the airport parking lots or nearby bus and transit stops, and judge whether it is feasible to call that travel 'on‑duty.' The bill separates the narrow travel segment it wants analyzed from employees’ broader commuting time, and it requires the Administrator to think through both benefits and costs.
The bill specifies several methodological focal points that will shape how the study is done. It requires disaggregation by airport type (small, medium, large hub as defined in federal aviation law), asks for an accounting of average commuting time exclusive of the targeted travel segment, and instructs the Administrator to consider digital methods — for example, mobile phones and location data — to capture arrival and departure events at parking or transit locations.
Those directions push the study toward empirical, location‑based measurement rather than purely survey‑based estimates.Beyond measurement, the statute forces the study to bridge technical and legal issues. The Administrator must estimate the fiscal effect of treating the travel time as on‑duty, explicitly including whether those hours would be creditable as basic pay for retirement purposes.
That raises payroll and benefit accounting questions (how to retroactively credit retirement, how to fund higher annuity liabilities) as well as labor relations issues (any change to on‑duty rules will intersect with collective bargaining for represented employees). The study therefore needs input from payroll, budget, benefits, and labor relations offices.Finally, the bill gives the Administrator discretion to include 'other considerations' — a catchall that invites analysis of privacy and civil‑liberties risks from location tracking, potential differences in rural versus urban airports, impacts on overtime calculations and FLSA applicability, and one‑time implementation costs for timekeeping systems.
The study is the vehicle for TSA to map the operational, legal, and fiscal terrain that would accompany any policy shift on what counts as on‑duty travel.
The Five Things You Need to Know
The bill sets a 270‑day deadline for the Administrator to deliver the feasibility study to three congressional committees.
The study must break out travel‑time estimates by airport classification (small, medium, and large hub) using the definitions in 49 U.S.C. §40102.
The Administrator must estimate costs of treating the targeted travel time as on‑duty, explicitly including consideration of whether those hours would be creditable as basic pay for retirement purposes.
The statute requires the study to evaluate the feasibility of using mobile phones, location data, or other means to record employee arrival to and departure from the relevant parking lots and transit stops.
The bill distinguishes the targeted parking/transit travel segment from employees’ broader commuting time and requires the study to quantify average commuting time exclusive of that segment.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Names the statute the 'TSA Commuting Fairness Act.' This is a conventional heading provision that carries no operational effect beyond identifying the measure.
Feasibility study requirement and delivery
Directs the TSA Administrator to submit a feasibility study within 270 days to the House Committee on Homeland Security and the Senate Committees on Commerce, Science, and Transportation and on Homeland Security and Governmental Affairs. Practically, the provision creates a hard deadline and identifies the congressional audiences; the short timeline will pressure the agency to rely on existing data sources and rapid data‑collection methods rather than prolonged field studies.
Travel‑time and benefit/cost baseline analyses
Requires the administrator to quantify travel time between duty locations and airport parking/transit stops across small, medium, and large hub airports; to measure average commuting time exclusive of that travel; and to analyze potential benefits to employees and the agency of reclassifying the time as on‑duty. For implementation teams, this means defining measurement windows, setting representative samples across hub sizes, and laying out benefit metrics (e.g., reduced lateness, retention) alongside cost drivers.
Technology, cost, and discretionary considerations
Directs the Administrator to examine technological options for recording arrivals and departures (mobile phones, location data, or other means), to estimate costs including possible retirement pay crediting, and to include other considerations the Administrator deems appropriate. These clauses force the study to grapple with data‑collection design, payroll and retirement accounting (how an added on‑duty hour would flow through basic pay), and ancillary issues such as privacy, collective bargaining, and IT changes that would be required to operationalize any policy change.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Frontline TSA screening officers and on‑site staff — if the agency later reclassifies the travel time, these employees could see more of their pre/post shift time recognized as on‑duty, potentially increasing payable hours, overtime eligibility, and retirement credit.
- Long‑service and future retirees — counting additional hours as basic pay would increase annuity calculations for affected employees, improving retirement benefits if the change is implemented and appropriately funded.
- Public transit users near airports and mobility planners — a policy that recognizes travel to transit stops could encourage greater use of transit and structured parking solutions if employer practice aligns incentives with public transportation.
- TSA HR, payroll, and workforce planning units — the study forces these offices to inventory current practices and identify system upgrades, which may improve timekeeping accuracy even if no policy change follows.
Who Bears the Cost
- TSA as an agency — if the recommendation leads to reclassification, TSA would face higher recurring payroll costs (wages, overtime), increased retirement liabilities, and one‑time IT and administrative expenses to change timekeeping and reporting systems.
- Federal taxpayers — any increase in retirement or pay obligations would require appropriation adjustments and could raise long‑term liability for the Treasury if retirement crediting is expanded without commensurate funding.
- Payroll and IT contractors and internal staff — implementing granular location‑based timekeeping or changing payroll rules would impose technical work and procurement costs on teams that maintain TSA’s HR systems.
- Employee privacy and legal support functions — using location data to authenticate arrival/departure raises privacy, records‑management, and legal review obligations that will demand resources and policy work, including potential bargaining with employee representatives.
Key Issues
The Core Tension
The central tension is between fairness and cost: recognizing more employee travel time as on‑duty addresses equity, punctuality, and retirement credit concerns for a workforce that often commutes to constrained airport sites, but doing so raises immediate fiscal, administrative, and privacy costs that the agency and taxpayers must shoulder — and those costs will fall unevenly across airports and employee groups.
The bill creates more analytical obligations than it resolves. First, reclassifying travel as on‑duty interacts with multiple legal regimes: federal pay statutes, retirement system rules, and potentially the Fair Labor Standards Act (FLSA) principles about compensable time.
The study must translate travel‑time measurements into payroll and retirement accounting methods, which can be technically complex and politically sensitive if benefits increase without identified funding. That raises the question of whether Congress or the agency would provide appropriations to cover any new recurring costs — a matter outside the bill’s scope but central to the practical feasibility of any policy shift.
Second, the bill points the Administrator toward technological solutions (mobile phones, location data) to capture arrival and departure, but that choice creates privacy, data‑security, and record‑retention challenges. Implementation would require policy decisions about consent, data minimization, retention windows, protections against misuse, and alignment with existing federal workforce privacy rules.
The study will have to weigh the accuracy and administrative burden of electronic tracking against less invasive methods (surveys, manual swipes), and it must do so quickly under the 270‑day clock.
Finally, the bill’s focus on parking lots and bus/transit stops raises borderline definitional issues: what counts as the relevant parking area (employee vs public lots), how to treat shared rides or drop‑offs, and how to handle multi‑leg commutes. The statute separates the targeted segment from 'average commuting time,' but practical line‑drawing will be contentious and likely require negotiation with employee representatives.
Those implementation ambiguities mean the study is necessary but unlikely to produce a single obvious policy path; instead, it will outline tradeoffs and options for future rulemaking or bargaining.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.