Independent travel intelligence. Sources cited on every guide. LatestAmtrak Ends CN Delay Disruption With 8-Year PactBoston Logan Airport Debuts Amelia AI Guide for AccessJetBlue Blue Fare Cost Allegedly Covered No Free Seat ChoiceMetro-North Grand Central Delays Disrupt September 16 Commute

Marine One Radio Calls Failed as DCA Jet Took Off

ShareEmailWhatsAppLinkedInXFacebook
Marine One helicopter flying above the White House lawn

Marine One tried twice to warn Ronald Reagan Washington National Airport before an August 4 departure, but one radio call never reached the tower and the other was unreadable. An Envoy Air jet was cleared for takeoff without the expected three-minute warning, according to a new federal preliminary report.

The event ended without injuries and both aircraft completed their flights. It still matters to DCA travelers because investigators found a specific communication blind spot, the FAA moved the affected radios, and the broader investigation remains open.

At a Glance
  • What happened: Marine One and Envoy Air flight 3742 lost required separation about two miles north of Reagan National on August 4.
  • What failed: The tower did not receive one predeparture call and could not understand a second call from Marine One.
  • Closest preliminary estimate: About 0.82 nautical mile laterally and 700 feet vertically.
  • Immediate fix: The FAA moved the helicopter-frequency radios from a nearby neighborhood to the top of the DCA control tower.
  • Traveler action: Do not assume a newsworthy aviation investigation means DCA is closed. Check the flight directly and allow normal disruption flexibility.

What the NTSB preliminary report says

The National Transportation Safety Board preliminary report identifies the aircraft as Marine One, a Sikorsky VH-3D using the identifier VM1, and Envoy Air flight 3742, an Embraer E-170 scheduled from Reagan National to Pensacola.

The aircraft were involved in a loss of separation at about 2:34 p.m. Eastern time. Marine One had departed the Ellipse south of the White House while the Envoy jet was departing DCA runway 1 and beginning its climb.

No passengers or crewmembers were injured. Marine One completed its local flight, and the Envoy flight continued to Pensacola.

The NTSB repeatedly labels its information preliminary and subject to change. Its investigation is ongoing, so the report does not assign final probable cause.

The radio warning that controllers never received

An agreement covering presidential helicopter operations requires the flight crew to contact the DCA tower on the helicopter frequency three minutes before departure. Once that call is received, DCA is expected to stop departures.

Certified tower recordings showed that Marine One’s first attempt was not received at all. The second was broken and unreadable. The controller had not received the warning and cleared the Envoy jet for takeoff.

Marine One also tried to relay the warning through the helicopter facility at Joint Base Anacostia-Bolling. That effort was unsuccessful. The helicopter established understandable communication after climbing to an altitude with better line of sight.

At that point, the Envoy jet was becoming airborne. The tower gave Marine One current traffic information, and the helicopter crew reported the jet in sight.

How close the aircraft came

The FAA’s preliminary estimate placed the aircraft about 0.82 nautical mile apart laterally and 700 feet apart vertically. The NTSB says it is still reviewing surveillance sources to confirm the closest proximity.

The Envoy crew reported a Traffic Collision Avoidance System traffic advisory shortly after takeoff. The alert did not become a resolution advisory that commanded a maneuver, and neither pilot visually located the helicopter.

The preliminary report says the displayed vertical separation was about 600 feet as the target passed behind the jet’s right wing symbol. That cockpit recollection and the FAA’s estimated 700-foot closest vertical spacing are different measurements and should not be merged into one number.

Associated Press reporting adds that the helicopter paused after its crew saw the airline traffic and that another arriving airplane was sent around once controllers recognized the presidential departure.

Why the temporary Ellipse operation mattered

Marine One was temporarily operating from the Ellipse while construction continued at the White House. After the event, FAA technicians studied radio coverage and found inadequate line of sight between the existing transmitter and receiver location and the Ellipse.

The technicians moved the radios from a nearby residential neighborhood to the top of the Reagan National control tower. Tests with two Marine Helicopter Squadron One aircraft at the Ellipse and in the area then found no deficiencies, according to the preliminary report.

That is an important operational response, but it is not a final finding that one antenna location explains every part of the event. The NTSB is still reviewing the separation calculation, communications and procedures.

Officials discussed spotty communications before August 4

DCA tower and Marine Helicopter Squadron One personnel met on July 30, five days before the event. Controllers raised concern that they had not been receiving some required three-minute calls, and the helicopter unit described communications as spotty.

The two groups discussed using another aircraft or facility to relay a call when direct contact failed. Evidence reviewed by investigators shows the crew attempted that alternative on August 4, but the relay did not reach the tower.

The existence of that meeting makes the preliminary report more consequential than an unexplained momentary radio dropout. It shows the parties recognized a communication symptom before investigators identified the line-of-sight limitation.

What this means for Reagan National passengers

The report does not announce a DCA shutdown, schedule reduction or new passenger restriction. A traveler should not cancel a flight solely because this investigation is in the news.

DCA has little slack when runways, restricted airspace or security operations temporarily interrupt traffic. Even a short operational pause can create gate and connection pressure, so same-day passengers should monitor the airline app and airport status rather than relying on a static itinerary.

Travelers with a tight connection should know the backup options before departure. Identify the next flight, keep essential medication in the cabin bag and avoid checking anything needed during an unplanned overnight stay.

Deep Arrival’s coverage of Reagan National’s summer travel planning guidance explains the airport’s parking and pickup recommendations. Those ground-side tips remain useful, but they do not predict an air-traffic restriction.

How to interpret preliminary aviation reports

A preliminary report documents facts available early in an investigation. It can identify aircraft, communications, weather, operating rules and immediate technical work without reaching a final probable-cause conclusion.

That distinction protects readers from two errors. The first is minimizing a serious loss of separation because no one was injured. The second is treating an early technical finding as a final judgment about fault.

The strongest current traveler takeaway is narrower: required communication did not reach the tower, simultaneous departures followed, the FAA moved the radio equipment, and the NTSB continues to investigate.

Why a technical fix does not close the safety question

Moving the receiver addresses the line-of-sight problem investigators found during postincident testing. It does not by itself answer why the helicopter departed after direct and relay calls failed, how the fallback procedure should work, or whether another independent communication path is needed.

A resilient system expects one component to fail without leaving every participant with a different picture of the airspace. That can involve equipment coverage, clear stop rules, confirmation that a critical message was received and a backup that is tested in the same location where it may be used.

The July 30 meeting shows that people were already trying to solve a practical problem. The investigation can now evaluate whether the agreed workaround was specific enough, whether each party understood it the same way and what should happen when both the normal call and the relay fail.

For passengers, the important distinction is between system learning and immediate panic. A serious event deserves transparent follow-through even when the airport continues operating. Travelers can respect the investigation, monitor their actual flight and avoid converting an early safety report into a claim that every DCA departure is unsafe.

What to watch next

Watch the NTSB investigation page for docket material, updated separation calculations and a final report. The final report can refine or replace preliminary conclusions.

Watch the FAA for any lasting procedural or equipment changes beyond the relocated radios. A successful post-move test is encouraging, but future policy can address redundancy as well as reception.

Finally, watch the live DCA operation on the travel day. The investigation is a safety story; an airline cancellation, delay or gate change remains a separate customer decision that should be confirmed through the carrier.

Decision Matrix
If you are… Best next step
Flying DCA today Keep the trip unless the airline changes it, and monitor the flight plus airport status.
Making a short connection Save the next viable flight and keep essential items in the cabin bag.
Reading the 0.82-mile figure Treat it as a preliminary FAA estimate that the NTSB is still confirming.
Assessing the radio fix Note that the FAA moved the radios and tests passed, while the investigation remains open.
Comparing fault claims Wait for final findings rather than assigning blame from a preliminary report.
Planning Impact

The new report is important aviation-safety news, but it is not a reason to assume Reagan National is closed. Travelers should preserve normal flight flexibility while investigators determine how the missed calls, temporary departure location and procedures interacted.

Frequently Asked

Was anyone injured in the Marine One event?

No injuries were reported, and both aircraft completed their flights.

How close did Marine One and the Envoy jet come?

The FAA’s preliminary estimate is about 0.82 nautical mile laterally and 700 feet vertically. The NTSB is still confirming the closest proximity.

Why did the tower not stop the jet?

The tower did not receive an understandable three-minute departure warning from Marine One, so the controller cleared the jet without knowing the helicopter was about to depart.

What did the FAA change afterward?

It moved the affected helicopter-frequency radios to the top of the DCA control tower, where subsequent tests reported no deficiencies.

Is the NTSB report final?

No. It is preliminary, subject to change and part of an ongoing investigation.

Table of Contents

The weekly brief

One calm email. The week's plan.

Park hours, crowd outlook, fare moves, and what changed, plus first word as we open new destinations. No noise, just the planning signal.

Free. Unsubscribe anytime. We never sell your address.