Intelligence. Accountability. Analysis.
Est. 2022 · Washington, D.C.
The Congressional Times
We follow the data, not the narrative
◆ Live Intelligence
Loading...
Analysis Loading today's analysis...
Federal Policy

U.S. Air Force Officer Recounts Evasion After Being Shot Down Over Iran

U.S. Air Force Officer Recounts Evasion After Being Shot Down Over Iran

The account surfaces publicly as Congress continues oversight hearings on U.S. Military engagements in the Middle East, raising questions about rules of engagement and rescue protocols.

Gab-E Intelligence Platform · September 14, 2026

A U.S. Air Force officer identified by the call sign Dude 44 Bravo has publicly described surviving days alone in Iran's desert after being shot down, evading capture by Iranian forces while awaiting rescue by U.S. Military units, according to a report published September 14, 2026, by 60 Minutes via RealClearPolitics.

The officer, referred to throughout the broadcast by his tactical call sign rather than his legal name, described being badly wounded at the time of the incident. The account states that both Iranian forces and U.S. Military search-and-rescue units were actively searching for him during the evasion period.

The 60 Minutes report does not specify the date of the incident, the aircraft type involved, or the specific military operation during which the shoot-down occurred. Those details, if not already in the public record, would be contained in Air Force accident investigation reports filed under Air Force Instruction 91-204, or in congressional notifications required under the War Powers Resolution, 50 U.S.C. Section 1541.

Under the War Powers Resolution, the executive branch is required to notify Congress within 48 hours when U.S. Armed forces are introduced into hostilities or situations where hostilities are imminent. Whether such a notification was filed in connection with this incident is not confirmed in the available source material. Congressional notifications under that statute are submitted to the Speaker of the House and the President pro tempore of the Senate and become part of the congressional record.

The Senate Armed Services Committee and the House Armed Services Committee both hold jurisdiction over military operations and personnel recovery protocols. Neither committee has issued a public statement, hearing notice, or press release referencing this specific incident as of the publication date of this article. Committee hearing schedules are publicly available through congress.gov.

Personnel recovery operations, including combat search and rescue, are governed by Joint Publication 3-50, the Defense Department's doctrine for recovering isolated personnel. That doctrine covers evasion, resistance, and escape procedures, as well as coordination between theater commands and rescue assets. Whether any after-action review of this specific recovery has been completed and whether it has been provided to relevant congressional oversight committees is not known from the available source material.

The cost and resource expenditure associated with a combat search-and-rescue operation of the type described would appear in Defense Department budget justification documents submitted to the appropriations committees, though individual recovery missions are not typically itemized at that level of detail. Unit-level expenditure records, if they exist in releasable form, would be accessible through a Freedom of Information Act request to the relevant Air Force command.

The officer's identity has not been released in the public source material reviewed for this article. Air Force personnel records are not public documents. The officer's rank, wing assignment, and the theater command responsible for the operation are not specified in the 60 Minutes report as summarized by RealClearPolitics.

The incident description, involving a downed American military aircraft and an evasion period inside Iranian territory, represents a significant operational event if confirmed through official channels. The State Department and the Defense Department had not issued public statements on the matter as of September 14, 2026, based on a review of both agencies' public press release archives.

What remains unknown includes the date of the incident, the type of aircraft, the specific operation involved, whether a War Powers Resolution notification was filed, whether any diplomatic communication with Iran occurred in connection with the event, and whether an official Air Force accident investigation report has been completed. Those details would be contained in Air Force accident investigation records, War Powers Resolution notifications in the congressional record, and any State Department cables or communications released under FOIA.

Today's Analysis
Loading...
Latest Intelligence
Congressional Intelligence
Loading...
Financial Intelligence
Loading...
Geopolitical Intelligence
Loading...
Follow the MoneyGab-E Political Intelligence Investigation
Loading...
Opinion & Analysis
Loading...
Archive
Loading...
About
Our Mission

We Follow the Data, Not the Narrative

The Congressional Times exists because public records are public — and the analysis built from them should not be exclusive to those who can afford $60,000-a-year intelligence subscriptions.

Every story published in The Congressional Times is sourced to a verifiable public record: a court filing, a Senate lobbying disclosure, an FEC contribution record, a USASpending contract, or a verified news report. We state our sources inline. We show our math. When we are wrong, we say so publicly.

We do not editorialize in news coverage. We do not use loaded language. Both political parties are held to identical standards.

The Follow the Money investigations are the heart of this publication. Each begins with Gab-E Political Intelligence running against 10+ million government records before a single word of editorial is written.

Powered by Gab-E, an elite global intelligence platform built to democratize political and financial intelligence.

Editorial Policy
Editorial Standards & Corrections Policy

How We Source, Verify, and Correct Our Work

Every factual claim in a Congressional Times story is checked against a primary source: a government filing, a court record, a direct quote, before publication. When a claim can't be verified or doesn't hold up as originally reported, we drop it or reframe it. We do not publish disputed claims as settled fact.

When we get it wrong: we correct the story directly, note the correction and date at the bottom of the piece, and update the record. We do not quietly edit and move on.

Bylines: stories with a named byline are written and fact-checked by that person. Stories without a byline are sourced from Gab-E Political Intelligence, our automated research platform, and are labeled as such.

Ownership: The Congressional Times is published by Gab-E Holdings LLC. Gab-E, our intelligence platform, powers our sourcing and research pipeline.

Corrections or concerns: support@gab-e.com