What Counsel Must Verify About ICE Airport Arrests in 2026
- Authority
- U.S. Immigration and Customs Enforcement (ICE)
- Rule type
- regulation
- Jurisdiction scope
- US federal
- Effective date
- Jul 27, 2026
- Source text
- Read primary rule text ↗
Verify passenger data sharing risk, status, and documents before noncitizen client air travel.
Scope note, last verified August 3, 2026, UTC: this is a U.S.-only Regulation & Ethics record for lawyers and legal teams. It is not legal advice for any individual traveler. The practical question is no longer whether immigration arrests can occur in airports. The question is what counsel must verify now that Secure Flight passenger data is being used as an immigration-enforcement input.
The source hierarchy matters. The first document is the TSA-ICE Memorandum of Agreement signed in May 2025, produced to American Oversight on July 23, 2026, and released publicly on July 28, 2026. The agreement cites the 2008 Secure Flight Final Rule as the legal basis for TSA’s passenger-data role and provides for ICE retention of shared passenger data.[1]

The record starts with the passenger-data handoff
The operational chain is simple enough to describe and serious enough not to flatten. TSA receives passenger information through Secure Flight. Under the May 2025 MOA, TSA shares passenger data with ICE. ICE then uses that data to identify travelers it considers immigration-enforcement targets. At the airport, the traveler experiences the result as a boarding-pass problem, a stopped itinerary, a secondary encounter, or a detention call. The traveler does not see the matching logic, the retention rule, or the enforcement list that turned travel into a custody event.

That distinction changes counseling. Traditional travel advice often asks whether the document is facially valid: passport, visa, advance parole, EAD, I-797 receipt, I-94, state identification. The 2026 airport program asks an additional question: what will ICE see when the client’s passenger record is compared with immigration-enforcement data before or during travel?
The earliest, cleanest risk category is still the client with a final order of removal. A data handoff that tells ICE when and where such a person is flying is operationally powerful even without any new substantive removal law. But the late-July 2026 reporting and practice alerts make the professional problem wider than final orders. Counsel must now screen visa overstayers, nonimmigrants with pending requests, adjustment applicants, asylum applicants, and travelers carrying advance parole or work authorization documents.
The enforcement figures show consequences, not a complete census
Reuters, relying on internal ICE data, reported more than 800 arrests on TSA tips and more than 31,000 traveler records shared through February 2026. Those are investigative findings from internal data, not DHS-confirmed official statistics.[2]
KCRA’s FOIA-derived analysis found airport-linked ICE arrests increasing from 108 to 568 between January 20, 2025, and March 10, 2026, with O’Hare linked 220 times. KCRA’s dataset was an incomplete snapshot, built from Deportation Data Project FOIA data and coding tied to 16 airports, landmarks, and current-duty-site fields. It is useful because it shows pattern and location; it should not be quoted as a complete national total.[3]
TRAC’s detention figures give the airport numbers a larger custody context. As of July 11, 2026, TRAC reported 65,765 people in ICE detention; about 70.6%, or 46,436 people, had no criminal conviction, and 43,138 people had been booked into detention during June 2026.[4] Those figures are not airport-arrest figures. They matter because a lawyer advising travel has to assume that an airport stop can become a real detention-placement problem, not merely a missed flight.
DHS has declined to confirm an airport-arrest uptick for operational-security reasons.[9] That refusal does not erase the MOA, the FOIA data, or the practice alerts. It does require careful wording: the public record supports a documented data-sharing and enforcement pipeline with reported arrests and detentions; it does not support claiming a complete, agency-certified national count.
Late July 2026 widened the client categories counsel must screen
AILA’s July 27, 2026 practice alert reported increased domestic-travel detentions at U.S. airports, including reports from California, Colorado, Florida, Illinois, Kansas, Michigan, New Jersey, Texas, and Virginia. AILA also noted reports involving individuals with valid work authorization or advance parole.[5]
Barnes & Thornburg’s July 29, 2026 alert described the expansion as reaching nonimmigrants with pending immigration requests, including people in periods of authorized stay with pending applications. The alert also described the July 14, 2026 detention in Nashville of a Southwest Airlines flight attendant as an example of the expanded risk category.[6]
That is the point where the client pool becomes much broader. A client with a pending adjustment application may have a receipt notice. A DACA or TPS-related traveler may have an EAD. An adjustment applicant may have advance parole. Those documents may be essential to the client’s lawful-position argument, but the practice reports show they should not be treated as proof that airport travel is operationally safe.[5][6]
The hardest call is the client who is neither plainly removable tomorrow nor plainly insulated from enforcement attention. That includes a person with an old overstay, a pending adjustment filing after a status gap, an asylum filing with disputed entry facts, a prior removal order the client barely remembers, or a travel document that is valid on its face but does not answer every removability question. The airport program makes those unresolved facts travel-critical.
Separate the legal hooks from the documents
The MOA is not an arrest statute. It is a data-sharing arrangement that helps put a traveler in front of immigration authorities. Counsel still has to identify the enforcement pathway ICE would likely use if the client is stopped.
For arrests, 8 U.S.C. § 1357(a) supplies the familiar immigration-officer authority, including warrantless arrest authority when statutory conditions are met. INA § 235(b)(1) is different: it governs expedited removal for certain applicants for admission and other covered noncitizens. It does not turn every admitted overstay, adjustment applicant, or asylum applicant into the same legal category, which is why the client’s entry, admission, parole, and physical-presence facts matter before the flight.
| Client posture | What counsel should identify before travel | Why it matters at the airport |
|---|---|---|
| Final order of removal | Order date, reopening history, stays, supervision, check-in history, pending motions or petitions | This remains the cleanest airport-enforcement category because passenger data can reveal the client’s itinerary and location. |
| Admitted nonimmigrant with possible overstay | I-94 history, extension or change-of-status filings, bridge issues, unauthorized employment allegations, departure triggers | The question is not only document validity; it is whether ICE may treat the person as presently removable despite pending filings. |
| Adjustment applicant or asylum applicant | Manner of entry, current parole or status theory, pending application receipts, EAD, advance parole, prior orders, bars or reinstatement issues | Pending applications can matter greatly, but the late-July alerts warn against assuming they prevent airport detention. |
| International arrival or return on advance parole | Inspection posture, parole document, prior unlawful presence, prior orders, inadmissibility risks, secondary-inspection plan | International arrival raises inspection and admissibility questions that differ from domestic airport travel. |
| Person potentially exposed to expedited removal | Entry date evidence, physical-presence evidence, prior encounters, credible-fear posture, circuit and litigation developments | Expedited-removal authority and its limits are a separate analysis, and current litigation remains a boundary condition counsel must check. |
For expedited removal, counsel should not rely on shorthand. The Make the Road New York v. Mullin litigation is part of the current boundary around expanded expedited-removal practice, and lawyers should read the D.C. Circuit source directly before making a precise claim about the current rule in a client file.[7]
Domestic travel and international arrival also have to be kept apart. A domestic itinerary may still trigger an ICE encounter because of Secure Flight data sharing, but it is not the same legal posture as presenting at a port of entry after international travel. A traveler returning on advance parole may have a stronger document packet than a domestic traveler with no parole document, yet the inspection setting can make the return more legally complex.
The pre-travel verification file

A competent pre-flight review now needs a file note, not a hallway answer. The point is not to frighten every noncitizen out of travel. The point is to avoid telling a client that a facially valid document settles a question that the airport enforcement system may test differently.
- Confirm identity and status chronology: entries, admissions, parole events, I-94 records, exits, status expirations, and any periods the government may characterize as unlawful presence or unauthorized stay.
- Check for removal history: final orders, in absentia orders, reinstatement risk, voluntary departure, supervision orders, prior expedited-removal orders, immigration-court hearings, appeals, motions to reopen, stays, and petitions for review.
- Verify pending filings: adjustment, asylum, withholding, CAT, TPS, DACA-related filings, extension or change of status, employment-based petitions, consular steps, receipts, biometrics, RFEs, denials, appeals, and any gap between status and filing.
- Review travel documents without overvaluing them: passport, visa, advance parole, EAD, refugee travel document, I-797 notices, state identification, and employer letters. Identify exactly what each document proves and what it does not prove.
- Map the itinerary: domestic versus international, departure and arrival airports, layovers, timing, return route, and whether the client can postpone, reroute, or travel with a different document packet.
- Prepare a detention-response plan: emergency contact, counsel contact, signed representation documents where appropriate, family document access, employer notification protocol, medication and caregiving issues, and rapid access to the immigration file.
- Document the advice: what was checked, what remained uncertain, what risk category applied, what alternatives were discussed, and what the client decided after receiving the explanation.
For law firms and in-house teams, the verification burden should not sit only with the attorney who happens to answer the phone. Knowledge-management staff should maintain an airport-travel intake form that forces the right questions before the itinerary is booked. Employers with noncitizen workforces should not tell employees that business travel is cleared merely because HR has an unexpired EAD or I-797 in the personnel file.
Boundary conditions: state resistance, incomplete data, and fast-moving litigation
State and local resistance may affect what happens around enforcement cooperation, detention logistics, and information sharing, but it does not make airport travel safe by itself. NILC’s July 9, 2026 report describes a state-law patchwork of measures resisting federal mass-deportation efforts.[8] That patchwork belongs in the file when it affects local response planning, but it does not replace the federal immigration-risk analysis.
The public data is also uneven. Reuters’ numbers are internal-data findings, KCRA’s numbers are FOIA-derived and incomplete, AILA’s alert is a practice report, and Barnes & Thornburg’s alert is a client advisory. Those sources do not carry the same evidentiary weight as a statute or an agency agreement. They do, however, point in the same operational direction: passenger data is being used to identify noncitizens for airport enforcement, and the reported risk category now reaches beyond final-removal-order cases.
Pending legislation, litigation, and agency practice may change the analysis. That is why the file should show the date of advice and the sources checked. A travel clearance given in early 2025, before the MOA became public and before the late-July 2026 alerts, is not the same professional act as a clearance given today.
The professional conclusion for Q3 2026
As of Q3 2026, counsel cannot treat airport travel advice for noncitizen clients as routine logistics. The record now includes a released TSA-ICE data-sharing agreement, reported arrests tied to TSA tips, FOIA-derived airport-arrest increases, detention-capacity context, and practice alerts involving domestic travelers, work authorization, advance parole, visa overstays, and pending applications.
Before a client flies, counsel should verify the status record, removability exposure, pending filings, travel documents, itinerary, and detention-response plan. Then counsel should explain what is known, what is uncertain, and why a boarding pass can now trigger an immigration-enforcement review the client never sees.
References
- ICE-TSA Data Sharing Agreement Lawsuit FOIA, American Oversight, July 28, 2026, link
- TSA shared data with ICE, leading to arrests at US airports, records show, The Guardian, April 7, 2026, link
- ICE arrests airport data, KCRA, link
- Immigration Detention Quick Facts, TRAC, link
- Practice Alert: Reports of Increased Detention at U.S. Airports for Individuals Traveling Domestically, AILA, July 27, 2026, link
- ICE Enforcement at U.S. Airports Expands to Include Nonimmigrants with Pending Immigration Requests, Barnes & Thornburg, July 29, 2026, link
- Make the Road New York v. Mullin, No. 25-5320, U.S. Court of Appeals for the D.C. Circuit, June 2026, link
- How States Are Fighting Back Against Trump’s Mass Deportation Machine, NILC, July 9, 2026, link
- ICE airport arrests, CNN, July 28, 2026, link
Operationalizing workflow
No workflow has been explicitly linked to this obligation yet. See Workflows generally.
Illustrative cases
No illustrative case is currently tracked for this obligation. See Risk Digest for documented incidents generally.
← Back to RegulationReport a correction or tip
Spotted an outdated figure, a misstated fact, or a ruling this regulation entry should reflect? Public comments are disabled for this content given the professional cost of a misreported case outcome, penalty amount, or rule text — use the structured correction channel instead.
Report a correction or tip for this record →