Vanderklok v. TSA

A passenger leaves an airport checkpoint with a broken wrist, a false-arrest allegation, or a claim that screening was discriminatory. The immediate question is not whether the checkpoint was public or private in the political sense. It is more basic: who can be sued, in which court, under which immunity rule, and with what contract sitting behind the person who touched the bag, gave the order, or called law enforcement.

Under the current TSA model, that map is already uneven. In the Third Circuit, Pellegrino and Vanderklok point passengers toward a hard sovereign-immunity problem: Transportation Security Officers have been treated as administrative screeners rather than law-enforcement officers for purposes of the Federal Tort Claims Act’s law-enforcement proviso, limiting assault, battery, false arrest, and similar claims against the United States in that jurisdiction.[1][2] In the Fourth Circuit and Eighth Circuit, the rule is different; those courts have treated TSOs as law-enforcement officers for FTCA purposes, allowing the waiver to reach claims that the Third Circuit would block.[3][4]

That is the existing fracture. It is not national law in any clean sense. The available rulings here are from the Third, Fourth, and Eighth Circuits, and the Supreme Court has not resolved the disagreement. For a passenger, geography can decide whether the first serious fight is about the facts at the checkpoint or about whether Congress permitted the case to exist at all.

The old uncertainty is federal and circuit-dependent

The FTCA does not simply say that a person injured by a federal employee may recover. It waives sovereign immunity only on specified terms, and those terms matter most when the claim sounds like intentional misconduct. The law-enforcement proviso is the narrow gate for claims such as assault, battery, false imprisonment, false arrest, abuse of process, and malicious prosecution when committed by qualifying investigative or law-enforcement officers.

The Third Circuit’s approach makes the statutory category do the work. Vanderklok emphasized the Aviation and Transportation Security Act’s distinction between screening employees and law-enforcement officers, and Pellegrino left passengers in that circuit without the same FTCA opening available elsewhere.[1][2] The Fourth and Eighth Circuits read the officer question differently, producing the split that now defines federal TSO liability for intentional tort claims.[3][4]

For readers who want the broader sovereign-immunity architecture, the FTCA problem here resembles the threshold disputes covered in internal discussions of how the FTCA shapes liability for Yellowstone tourist incidents: courts often decide whether the government can be sued before they ever reach the injured person’s version of events.

That is a poor baseline for clarity, but it is still a known kind of uncertainty. Lawyers can identify the circuit, check the FTCA cases, file an administrative claim when required, and anticipate a federal sovereign-immunity defense. TSA privatization changes that sequence.

Private screeners do not simply step into TSO liability

The statutory hinge is 28 U.S.C. § 2671. The FTCA definition of federal employee includes officers and employees of federal agencies, but it excludes “any contractor with the United States.” That exclusion is the point too often lost when privatization is described as a staffing model rather than a remedial redesign.[5]

If a passenger’s alleged injury is caused by a federal TSO, the claim begins in the FTCA world, however fragmented that world may be. If the same conduct is committed by an employee of a private screening contractor operating under the Screening Partnership Program or a Gold+ arrangement, ordinary FTCA coverage does not presumptively travel with the badge. The defendant is no longer simply the United States acting through a federal employee; the defendant may be the contractor, the individual employee, or another entity depending on the pleaded theory and the applicable state law.

That shift changes more than the caption. It changes the plaintiff’s first investigation. Counsel has to determine whether the screener was a federal TSO, a contractor employee, a worker retained through a right-of-first-refusal transition term, an airport police officer, or someone else in the chain. Each answer can alter the forum strategy, limitations analysis, immunity argument, indemnity inquiry, and insurance search.

For passengers, this is not a technical substitution. A false-arrest claim that once rose or fell on whether a TSO qualified under the FTCA law-enforcement proviso may become a state tort case against a contractor. A physical-injury claim may turn on premises concepts, negligent training, negligent supervision, battery, or vicarious liability. A discriminatory-screening claim may require a different mix of federal civil-rights theories, state public-accommodation law, and contract-related discovery. None of that is necessarily worse in every case. It is less charted.

State tort law would carry more of the load

Once the alleged wrongdoer is a contractor employee rather than a federal employee, state law becomes harder to avoid. The basic claims may look familiar—negligence, assault, battery, false imprisonment, negligent hiring, negligent retention, negligent training—but the elements, immunities, damages rules, notice requirements, and employer-liability doctrines can vary by state.

That matters because airport screening is national in function but local in litigation consequences. A passenger injured at one airport may be steered toward one state’s tort doctrines; a passenger injured after materially similar conduct elsewhere may face a different damages cap, different emotional-distress rule, different employee-scope analysis, or different standard for punitive damages. The forum-shopping incentive does not disappear. It changes shape.

A contractor defendant will also have incentives that the United States does not share in the same form. It may remove to federal court if a federal-question or federal-officer-removal theory is available. It may argue that TSA directives controlled the challenged conduct. It may point to airport authority obligations, local police intervention, or passenger behavior as intervening causes. It may also tender the defense to an insurer or seek indemnity under a contract the injured passenger has not seen.

This is where the practical burden shifts onto the claim file. The plaintiff needs documents before knowing whom to sue confidently. The airport risk manager needs to know whether a passenger injury will trigger contractor insurance, airport coverage, federal indemnity, or a dispute among all three. The procurement reviewer needs to know whether a lower bid price is being subsidized by an unexamined allocation of tort risk.

Boyle is a question, not an answer

The most important unresolved defense is the government-contractor defense associated with Boyle v. United Technologies Corp. Boyle recognized a federal common-law defense in the military-procurement context when the government approved reasonably precise specifications, the equipment conformed to those specifications, and the supplier warned the government about dangers known to the supplier but not to the government.[6]

Private airport screening is not a military helicopter-design case. A contractor operating a checkpoint may argue that federally mandated screening procedures left no room for state tort law to impose a different duty. A plaintiff may answer that the claim is not an attack on TSA policy at all, but on excessive force, misidentification, discriminatory treatment, poor supervision, or careless execution. Those are different propositions, and courts have not yet supplied an appellate answer for private SPP screeners.

That absence should be treated as an absence. No appellate court in the reviewed materials has decided whether Boyle extends to private SPP screeners performing TSA-mandated screening under federal contract. Treating Boyle as a guaranteed shield would overstate the law. Treating it as irrelevant would understate the litigation risk. It is a live defense candidate whose strength will likely depend on the precise claim, the federal directives at issue, the contractor’s discretion, and the record developed in discovery.

The distinction is not academic. If Boyle or a related federal-preemption theory applies broadly, a passenger may find that state tort law supplies the cause of action but federal contractor doctrine narrows the duty. If it applies narrowly, contractors remain exposed to ordinary state-law standards for conduct that cannot be attributed to precise federal commands. Until courts test the issue in the screening context, any confident procurement claim about liability clarity is premature.

The contract may decide who pays, but the public may not see it

The July 2026 Gold+ request-for-proposal and transition materials reviewed for this analysis include right-of-first-refusal hiring terms, but they do not publicly explain how passenger tort-liability exposure changes when screening is performed by contractor employees rather than federal TSOs.[7] That omission is not a drafting quibble. In a privatized checkpoint, indemnity and insurance provisions may determine whether the contractor, the airport, an insurer, or the federal government ultimately absorbs defense costs and judgments.

A public-facing privatization pitch can say “private screening” while leaving the legally decisive material in attachments, incorporated clauses, coverage schedules, or bid documents. The passenger does not know whether the contractor must indemnify the government. The airport may not know, from the public materials alone, whether its own policies are primary, excess, excluded, or implicated through additional-insured language. Plaintiff’s counsel may need early discovery simply to understand the financial architecture behind the person at the checkpoint.

That opacity creates a different kind of uncertainty from the FTCA split. The FTCA problem is public law: visible, citable, and geographically bounded. Contractual allocation is private or semi-private risk engineering. It may be rational. It may even be well priced. But if the terms are not disclosed, the affected passenger and the airport board evaluating privatization are asked to trust a liability structure they cannot inspect.

Cost data explains the pressure, not the remedy

There is a reason airports look at privatized screening. GAO-16-19 reported, using 2015 data, that private-screening contractor costs were on average 11 percent below TSA’s estimated costs, with airport-level differences ranging from 2 percent to 19 percent below TSA estimates.[8] GAO also cautioned that TSA’s estimates excluded Federal Employees Retirement System pension costs, a caveat that matters when the comparison is used as a savings claim rather than as a rough procurement signal.[8]

Those figures should not be carried into 2026 as if nothing changed. Later TSO pay increases and budget changes are reasons not to treat the 2015 comparison as current proof of savings. The data is still useful for explaining the attraction of SPP or Gold+ enrollment: if an airport believes it can obtain comparable screening at lower apparent cost or with more local control, privatization becomes administratively tempting.

But tort exposure is one of the costs that can disappear from the headline and reappear in the dispute. A bid can be lower because labor is organized differently, because pension assumptions differ, because staffing is managed differently, because insurance is priced differently, or because legal risk is shifted rather than reduced. The GAO numbers do not answer which of those is doing the work at any specific airport.

Labor transition is a liability issue when status controls the claim

The labor materials matter here only because employee status is legally consequential. DHS terminated a collective-bargaining agreement affecting 47,000 TSOs, and AFGE litigation produced a preliminary injunction in that dispute.[9] Separately, the Gold+ transition materials reviewed in July 2026 include right-of-first-refusal hiring terms.[7] Those facts sit in the same liability file because a worker’s path from federal employment into contractor employment can change the remedial regime attached to that worker’s conduct.

The historical warning is also practical. Available labor materials identify pre-9/11 private-screener turnover exceeding 100 percent annually.[9] That figure should not be treated as proof that a modern SPP or Gold+ contractor will replicate the same turnover pattern. It does, however, explain why staffing continuity, training records, supervision, and retention terms belong in a liability review rather than in a separate labor-policy box.

If a passenger alleges that an injury flowed from inadequate training, rushed staffing, poor supervision, or failure to remove a known-problem employee, the distinction between federal workforce management and contractor workforce management becomes evidence. The right-of-first-refusal term may preserve some continuity at transition, but it does not by itself answer who is responsible for post-transition training, discipline, incident review, or defense tender.

What a passenger’s lawyer has to verify first

The first factual task after a checkpoint injury is identification. The uniform may not answer it. The boarding pass, surveillance footage, incident report, contractor roster, airport police report, and TSA complaint record may all be needed before the legal theory can be safely chosen.

• Identify the actor: federal TSO, contractor screener, airport police, local law enforcement, airline employee, or another participant.
• Identify the forum incentives: FTCA federal practice for TSOs, state tort practice for contractor conduct, and any removal path.
• Identify the immunity theory: sovereign immunity, law-enforcement proviso limits, state governmental immunity, federal preemption, or Boyle-style contractor defense.
• Identify the financial backstop: contractor insurance, airport coverage, federal indemnity, additional-insured provisions, and exclusions.
• Identify the operational record: screening directive, training file, staffing level, incident review, complaint history, and who had authority to intervene.

Civil-rights and custody analogies can be useful but should not be imported too quickly. As in other federal-contact settings, including the claim pathways discussed in three legal pathways for a Mexican tourist killed fleeing ICE and legal options after a death in ICE custody, the pleading route depends on the defendant’s legal status as much as on the severity of the harm.

What airports and procurement reviewers should not leave to later

For an airport evaluating Gold+ or SPP, the legal review should not stop at operational control and projected cost. A checkpoint is a place where low-frequency, high-friction incidents produce expensive disputes: physical contact, perceived profiling, law-enforcement referrals, missed medical conditions, damaged property, and removal from travel. Those disputes do not wait for a board to reconstruct indemnity language after the first complaint arrives.

The review should ask for the actual indemnity provisions, not a summary. It should ask whether the contractor must defend the airport, TSA, both, or neither. It should ask for insurance limits, exclusions, self-insured retentions, additional-insured language, notice requirements, and control-of-defense terms. It should ask whether intentional torts, civil-rights claims, negligent training, and employment-practices allegations are covered or carved out.

It should also ask how complaints become records. A federal checkpoint incident may generate TSA documentation, airport police records, airline records, or contractor records. If privatization changes where those records sit, how long they are retained, or who must produce them, it changes the evidence environment for both the injured passenger and the risk manager trying to evaluate a pattern.

None of these questions proves that privatized screening is unlawful or categorically worse for injured passengers. They show that the legal implications of TSA privatization are not exhausted by the familiar pros and cons of efficiency, staffing flexibility, or local control. The liability system has its own architecture, and it must be priced, disclosed, and tested on its own terms.

The narrower conclusion

The current TSA regime leaves passengers with a circuit-dependent FTCA problem. In the Third Circuit, the cases identified here point against law-enforcement-proviso coverage for TSOs; in the Fourth and Eighth Circuits, the opposite rule applies.[1][2][3][4] That is fragmented and unsatisfactory, but it is at least a visible body of federal law.

SPP and Gold+ privatization would likely replace that known uncertainty with a less tested contractor-liability uncertainty. State tort law would carry more weight. Boyle would sit as an unresolved defense question. Indemnity and insurance terms could decide who ultimately pays, yet the reviewed July 2026 Gold+ materials do not publicly explain the passenger-liability transition.[7] Forum-shopping incentives would persist, only now around state-law claims, removal, contractor defenses, and contract-specific risk allocation.

Before relying on any privatization claim about cleaner legal exposure, the missing items are concrete: the governing circuit law for federal TSO claims, the contract indemnity terms, the insurance requirements, the relevant state tort rules, and whether a future court extends Boyle or a related contractor defense to private airport screeners. Without those answers, “private screening” is not a liability solution. It is a change in where the uncertainty lives.

References

1. Pellegrino v. TSA — Courthouse News Service and FEDmanager.
2. Vanderklok v. TSA — U.S. Court of Appeals for the Third Circuit.
3. Osmon v. United States — U.S. Court of Appeals for the Fourth Circuit.
4. Eighth Circuit decision on Transportation Security Officers and the FTCA law-enforcement proviso — U.S. Court of Appeals for the Eighth Circuit.
5. 28 U.S.C. § 2671 — U.S. Code.
6. Boyle v. United Technologies Corp. — Supreme Court of the United States.
7. Gold+ RFP and transition documents — July 2026.
8. GAO-16-19 — U.S. Government Accountability Office.
9. AFGE litigation materials on TSA collective bargaining and workforce data — American Federation of Government Employees.