Breaking News · Immigration · U.S.–Iran Conflict · Federal Courts · Asylum Confidentiality · Civil Rights · Due Process · DINA Analysis
WASHINGTON — November 6, 2026: Court records unsealed Thursday show that the Trump administration pursued plans to remove Iranian nationals through a third country while the United States was at war with Iran, prompting a federal judge to require advance notice before any removal could proceed.
At an October 15 hearing, a Justice Department lawyer told U.S. District Judge Ana Reyes that the government's answer had changed from having no planned removals to having plans for removals. The lawyer said the United States would facilitate travel to an unidentified third country and Iran would facilitate onward travel. The transcript did not establish a specific departure date or identify the people who might be removed.
Reyes ordered the government to provide at least five days' written notice before placing a person on transportation bound for removal and 24 hours' notice after any plan is finalized. She warned that violations could trigger contempt proceedings.
What the transcript establishes
The lawsuit, Iranian American Legal Defense Fund v. Rubio, No. 1:26-cv-02375, is pending in the U.S. District Court for the District of Columbia. It challenges alleged disclosures of confidential information about Iranian asylum seekers and the government's removal practices.
The October 15 hearing record shows that federal officials had communicated with Iran's Interests Section in Washington about travel documents and possible avenues for removal. A Justice Department attorney said detainees would first be taken to another country and Iranian authorities would arrange onward travel. The government told the court that no specific removal date had been fixed at that time.
On October 20, Reyes denied the plaintiff's preliminary-injunction request and an emergency discovery motion, while ordering the government to submit meeting notes for private judicial review. That denial was not a final judgment that every challenged practice was lawful. The case remains pending, and the court's notice directives continue to matter because they give lawyers and the court time to examine any finalized plan.
What remains allegation, not established fact
The Iranian American Legal Defense Fund alleges that immigration agencies shared protected information about asylum seekers with Iranian representatives. The organization also told the Associated Press that at least 12 detainees had recently been notified of possible removals, some allegedly as soon as Sunday, November 8, through Pakistan. It said one detainee attempted suicide and two were transferred to a Texas facility frequently used before removals.
DINA has not independently confirmed those detainee-specific claims. No public court filing reviewed for this report establishes a passenger list, a Sunday departure time or a completed removal plan. DHS has disputed the allegation that it shared asylum-application records with Iran. The State Department told the Associated Press that it generally does not comment on pending litigation or private diplomatic communications.
The confidentiality rule at issue
Current federal regulation 8 C.F.R. § 208.6 protects information contained in or pertaining to asylum, withholding-of-removal and Convention Against Torture applications, as well as credible-fear and reasonable-fear records, subject to listed exceptions. The rule also protects records showing that a specific person sought such protection.
Whether any disclosure in this case violated that regulation depends on exactly what information was transmitted, who received it, whether written consent existed and whether a regulatory exception applied. The public record reviewed by DINA does not resolve those questions. The judge's October 20 order for in-camera review of meeting notes reflects that the underlying evidence still requires judicial examination.
Why it matters
Returning a person to a government they say may persecute or torture them can carry irreversible consequences. The risk is heightened when the destination country is in an active war with the United States and U.S. officials themselves describe severe instability and repression.
The case also reaches beyond any one flight. Asylum confidentiality exists in part so applicants can explain alleged persecution without alerting the government they fear. If protected information was disclosed improperly, it could endanger individuals and undermine confidence in the asylum system. If officials used only information lawfully available for consular travel documents, the government should be able to demonstrate that through a complete, appropriately redacted record.
DINA analysis
The administration's assertion that it is enforcing final orders answers only one part of the accountability test. Lawful removal authority must still be exercised consistently with confidentiality rules, the Convention Against Torture framework, statutory withholding protections, court orders and basic due process.
The notice order is therefore more than a scheduling requirement. It is the practical safeguard that allows the court to determine whether an individual has received the review the law requires before transportation begins. The public should not assume that the court's denial of preliminary relief validated the broader alleged program; nor should it assume that diplomatic contact with Iran proves unlawful information sharing. Both conclusions require evidence the public record does not yet supply.
Strongest accountability angle
The central accountability question is the chain of custody for detainee information: which agency selected each person, what records were given to Iranian representatives, who authorized each disclosure, what legal exception was invoked, and what individualized risk assessment preceded removal planning.
A second question is operational transparency. If officials have finalized a November 8 flight or any other removal movement, the court's notice requirements should produce a dated filing or other verifiable record. Aggregate information can be released without exposing private asylum claims or identifying vulnerable detainees.
Urgent follow-up and public records
- Obtain the complete October 15 transcript, the court's written notice directives and every docket entry filed after the transcript was unsealed.
- Request aggregate counts of Iranian nationals considered for removal, notified, transported or removed, broken down by final-order status, fear-review status and destination, without names or private asylum details.
- Request DHS, ICE, State Department and Justice Department communications with Iran's Interests Section and any third country about travel documents, routing, flights and diplomatic assurances.
- Request the legal memorandum or compliance review addressing 8 C.F.R. § 208.6 for each category of information shared.
- Request individualized country-conditions, non-refoulement and Convention Against Torture review protocols used for contemplated returns to Iran during the war.
- Request redacted versions of the meeting notes submitted for in-camera review, if and when the court permits disclosure.
- Track any notice of a finalized plan, including a possible November 8 flight, and verify that the five-day and 24-hour requirements were satisfied.
- Request medical and mental-health safeguards for detainees who receive removal notices, including suicide-prevention protocols and continuity-of-care plans.
Primary and corroborating sources
- Iranian American Legal Defense Fund — case-document index, including the October 15 evidentiary-hearing transcript
- CourtListener/RECAP — public docket for Iranian American Legal Defense Fund v. Rubio
- Civil Rights Litigation Clearinghouse — docket chronology and October 20 orders
- Electronic Code of Federal Regulations — 8 C.F.R. § 208.6, disclosure to third parties
- Plaintiff's exhibit — ICE emails concerning Iranian removals
- Associated Press — unsealed transcript, government responses and detainee allegations
- ABC News — October 15 hearing transcript and removal-route account