Skip to content
View in the app

A better way to browse. Learn more.

ASEAN NOW

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Trump Aboard During Marine One Traffic Incident

Featured Replies

Federal aviation officials and the National Transportation Safety Board (NTSB) are investigating an air traffic incident involving the Marine One presidential helicopter this week, which occurred while President Donald Trump was on board, authorities said on Wednesday.

The incident took place at about 2.30pm Eastern Time on Tuesday as Marine One departed from the Ellipse near the White House, with the president travelling to Joint Base Andrews in Maryland as part of the first leg of a trip to the West Coast, the Federal Aviation Administration (FAA) said.

Departure Near Reagan National Airport

As Marine One lifted off, commercial traffic at nearby Ronald Reagan Washington National Airport (DCA) was not stopped as required by safety procedures, officials said.

Standard protocol calls for air traffic controllers to suspend all other aircraft operations three minutes before Marine One is scheduled to depart. According to officials, that coordination did not happen at the time of take-off.

An air traffic communications recording provided to ATC.com indicated that Marine One issued a notice about three minutes before departure. However, a controller did not hear the message because another transmission was being made on the same frequency.

FAA Says Separation Lapse Was Brief

The FAA said that initial review suggested the event involved a brief disruption in separation between Marine One and an American Airlines regional service aircraft taking off from DCA.

Under FAA regulations, commercial aircraft must maintain at least 1.5 miles of horizontal separation and 500 feet of vertical separation from a helicopter operating in the vicinity of DCA. The FAA said the American Airlines regional flight did not come dangerously close to Marine One at any point.

In its statement, the FAA said the aircraft continued to diverge after the loss of required spacing. It added that during the period in question, the controller remained in contact with both the commercial pilot and the Marine One pilot.

White House Says President Was Not At Risk

The White House said on Wednesday that the president was never at risk. “At no point was the President in harm’s way,” it said in a statement.

The Wall Street Journal first reported the incident late on Tuesday.

Review Under Way, Corrective Actions Planned

The FAA said it was continuing its examination of the incident and would introduce any suitable corrective measures based on its findings.

Join the discussion? Create account. orange.png


image.png

6 August 2026


View full article

Bit of an overreaction.

The lapse wasn’t about Marine One being in mortal danger, it highlighted that commercial traffic was left exposed.

If the controller missed the call, that means the American Airlines flight was the one carrying the risk. FAA admits spacing was briefly off but never “dangerously close.”

White House spin that the President was never at risk misses the point: the system breakdown put paying passengers in the mix.

  • Popular Post

Marine One pilot should have received a confirmation from the tower to assure the tower heard his transmission. That's why there is always a readback between air traffic and tower.

24 minutes ago, dannyol said:

Marine One pilot should have received a confirmation from the tower to assure the tower heard his transmission. That's why there is always a readback between air traffic and tower.

Yes, correct.

In controlled airspace, a pre-filed flight plan or "as-briefed" schedule does not grant an active movement clearance. Positive readback between pilot and controller is required before wheels leave the ground.

On 8/6/2026 at 12:26 PM, webfact said:

An air traffic communications recording provided to ATC.com indicated that Marine One issued a notice about three minutes before departure. However, a controller did not hear the message because another transmission was being made on the same frequency.

What a screw up - if Marine One didn’t get the read back confirmation from the ATCO then Marine One should never have taken off. What a horrible piece of arrogance by Marine One to assume the message was heard. Seems yet another abject safety failure showing that the FAA’s safety culture is broken.

On 8/6/2026 at 12:48 PM, Jim Waldron said:

Bit of an overreaction.

The lapse wasn’t about Marine One being in mortal danger, it highlighted that commercial traffic was left exposed.

If the controller missed the call, that means the American Airlines flight was the one carrying the risk. FAA admits spacing was briefly off but never “dangerously close.”

White House spin that the President was never at risk misses the point: the system breakdown put paying passengers in the mix.

I blame the pilot of Marine One whose 3 minute "warning call" was blocked (happens all the time on busy frequencies - especially by pushy pilots who do not listen out before transmitting) , AND who ,clearly, did NOT receive an acknowledgement to his call from the controller (who also would have, most likely, known of the blocked call and requested that the "other" aircraft "say again"

And these are meant to be highly experienced and disciplined pilots and controllers.

Pathetic!

On 8/6/2026 at 5:26 AM, webfact said:

“At no point was the President in harm’s way

What a shame!

One day when the Mossad finds he's of no use anymore, this festering wad of afterbirth will have an accident and he will be directly in harms way

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.