Follow America's fastest-growing news aggregator, Spreely News, and stay informed. You can find all of our articles plus information from your favorite Conservative voices. 

The helicopter carrying President Trump nearly crossed paths with a passenger airliner over Washington after confused radio calls and crowded airspace created a dangerous moment, prompting an FAA review and renewed questions about how the capital’s skies are managed.

This incident happened as Marine One departed the White House for Joint Base Andrews, and it exposed flaws in communication and traffic handling near Ronald Reagan National Airport. Officials say separation briefly dropped short of safe standards, though the FAA’s preliminary review calls it a “momentary loss of separation.” From a Republican angle, this raises concerns about operational discipline and the need to hold aviation authorities accountable for preventing needless risks to the president and civilians.

Marine One crews repeatedly warned tower controllers that they were about to lift off, yet radio traffic became muddled and the helicopter moved into a conflict path with an Envoy Air passenger jet. Controllers apparently did not hear the calls in time, and the controller warned Marine One a minute after their takeoff that there was “traffic.” That sequence points to a breakdown in basic air traffic management at a time when redundancy and clarity should be ironclad.

A military helicopter carrying President Trump came within less than a mile of a passenger jet above Washington on Tuesday after garbled communications between his crew and air traffic controllers in Ronald Reagan National Airport’s tower delayed the controllers from clearing nearby air traffic, according to two people familiar with federal officials’ initial assessment.

The incident occurred shortly after 2:30 p.m. as Mr. Trump was flying to Joint Base Andrews from the White House on the initial leg of a planned trip to Los Angeles.

At peak times, the Washington terminal area is congested, and that pressure magnifies the consequences of any miscommunication. Aviation safety relies on predictable, fail-safe procedures, and when those procedures are strained, you get near-misses that would be unacceptable under any competent management. Republicans should demand clear answers and corrective action so political risk does not translate into a public safety crisis.

Officials described the proximity in concrete terms: the helicopter came within 0.8 miles laterally and 700 feet vertically of the passenger jet at closest approach. The FAA defines a loss of safe separation in cases like this as breaching either 1.5 miles laterally or 500 feet vertically, though parameters can vary by airspace and aircraft type. Those numbers matter, because they help determine how close we edge to catastrophe.

The communications appeared not to have been heard by the controller, and the helicopter advanced. That put it in the flight path of an Envoy Air passenger jet, a haunting situation after a tragic collision between a military helicopter and a passenger jet in the Washington airspace last year.

Cassandra Nolan, a spokeswoman for the Federal Aviation Administration, said “based on our preliminary safety review,” there had been a “momentary loss of separation,” that the president was “never in danger,” and that a “review” is ongoing. Those reassurances are not enough on their own. The public and lawmakers need specifics: what exactly went wrong, how controllers missed the calls, and what fixes will be implemented to prevent recurrence.

At their closest proximity, Marine One came within 0.8 miles of lateral distance and 700 feet of vertical distance from the passenger jet, according to the two people with knowledge of the Federal Aviation Administration’s preliminary findings.

A loss of safe separation — the distance between two aircraft that is needed to reduce the likelihood of a collision — is defined by the F.A.A. in a case like this as breaching either 1.5 miles in lateral distance or 500 feet in vertical distance. But the parameters can vary depending on the airspace and the types of aircraft.

This episode should trigger a mandatory, transparent after-action investigation with timelines for corrective steps and accountability where needed. Congress must press the FAA and Department of Defense partners to explain coordination failures and to set binding standards for presidential movements in crowded airspace. Vague promises of “reviews” won’t cut it when lives and the security of the commander in chief are at stake.

Operational fixes could include improved radio redundancy, stricter sequencing rules for helicopters near passenger routes, and a reexamination of how military and civilian traffic are integrated around major airports. Training standards and controller staffing levels deserve scrutiny as well, because even small lapses can have oversized consequences in the terminal area. Republicans should push for practical reforms that strengthen safety without politicizing the agencies responsible for keeping our skies secure.

Add comment

Your email address will not be published. Required fields are marked *