Tag Archive for: transportation

‘Accident Waiting To Happen’: Feds Ignored D.C. Death Trap For Years Despite Dozens Of Near Misses With Planes, Choppers

Washington’s Reagan National Airport has suffered countless near misses between aircrafts over the last few decades, many reported by pilots themselves, an issue the FAA has done little to solve, according to a Daily Caller review of public documents.

Just a few moments away from touching down at Washington Reagan National Airport (DCA) on Jan. 29, an American Airlines passenger jet collided with a military helicopter. There were no survivors. The most fatal crash in several decades has caused aviation experts and administration officials alike to parse through public information and determine how something so catastrophic happened. Was the helicopter too high? Did the airplane take the wrong approach? Did Air Traffic Control (ATC) give proper alerts?

Days after the crash, the FAA temporarily banned all mixed helicopter and fixed-wing flying aircrafts from flying over the Potomac River near the airport. New FAA guidance now allows some emergency helicopters to pass near the D.C. airport and requires civilian planes to hold when they are in the area.

But those changes only happened now, despite the fact that for years prior to the crash, helicopters and airplanes have been passing within feet of each other at DCA, causing pilots to make evasive maneuvers to avoid catastrophe. Pilots have been angrily reporting these incidents to an anonymous, public database, but little was done to address the issue until the tragedy last month.

“THIS HELI CONFLICT … AT DCA IS AN ONGOING PROB. HERE IS AN ACCIDENT WAITING TO HAPPEN,” a pilot furiously asserted after a January 2016 near miss.

The issue has become so frequent that pilots reported feeling that complaining about the incidents was useless and unlikely to spur any action. As such, they started treating the near misses as practically inevitable at the Washington, D.C. airport.

“Complacency is a killer,” one commercial pilot, who requested anonymity to speak freely about the reported incidents and the DCA crash, told the Caller.

The Daily Caller reviewed public reports pilots and air traffic control have filed through the Aviation Safety Reporting System (ASRS) between 1988 to 2025 while working at DCA. The reports address all sorts of aviation issues and are supposed to help the FAA “disseminate information to the proper authorities who can investigate and determine if action is warranted.”

The Caller looked specifically at self-reported airborne conflicts and near misses between aircrafts near Washington Reagan National Airport and found there had been 220 such incidents from 1988 to 2025. Of those, 30 have been between helicopters and airplanes, marking an almost annual occurrence.

By comparison, nearby Dulles National Airport has had 181 self-reported airborne conflicts and near misses between aircrafts in the same time period. Just five have been between helicopters and airplanes.

“Anyone can [self] report it for any reason, but usually it’s because pilots get afraid and they said, ‘Holy shit that was too close.’ Traffic was issued too late, or I didn’t see that issue report,’” Michael Pearson, a former air traffic controller and ATC training instructor, told the Caller of the ASRS reports.

The commercial pilot added, “Usually you are pretty pissed if you are willing to write the report and submit as an ASR. It’s not an ‘Oh, that was interesting’ moment. It’s a ‘Hey, this is a problem’ moment.”

The near miss reports cite numerous issues that pilots and ATC have faced over the last several decades at DCA. Some airplane pilots wrote that they never received any alert from the ATC of a helicopter flying just feet below the plane as it landed.

“Helicopter traffic was heading up the Potomac while we were on the river … visual approach did not alert us to the oncoming traffic,” a pilot wrote in January 2022.

Others were notified of the close aircraft only after it had passed by.

“After there was action taken to make a correction from the close call, we were then informed by DCA tower of close traffic,” a pilot recounted in July 2015, “although at that point it would have been too late.”

In other instances, pilots and ATC reported that helicopters flying near the DCA runways had climbed far higher than they were supposed to, putting them dangerously close — sometimes just 200 feet — from the airplane.

Even a helicopter potentially tasked with transporting the vice president has reportedly experienced a near miss in the last decade. In May 2017, a helicopter and airplane pilot reported an “an unsafe situation involving VIP movements.” It is not confirmed if the vice president — at the time, Mike Pence – was in the helicopter at the time, but the report notes that the craft was en route to the Naval Observatory.

One air traffic controller for the Potomac Consolidated TRACON wrote that they were holding airplanes in the sky during a presidential movement, but the controllers at DCA nonetheless launched two departures at the presidential aircraft “less than a mile and no altitude, converging.” The report suggests that towers need to coordinate better during VIP movements.

“How is it we on approach are not allowed to run arrivals yet they have the authority to release airplanes right at presidential aircraft?” the controller at Potomac Consolidated TRACON vents in his report.

DCA’s airport is one of the most difficult landings for pilots in the country. With congested airspace, short runways, frequent restricted airspace and landings right along the water, the reports showed that pilots found themselves having a difficult time juggling an already-tight landing zone with possible helicopter presence near the runways. Pilots were especially frustrated with the fact that helicopters are allowed to pass below airplanes, near runways, as commercial airplanes are descending to land.

“I cannot imagine what business is so pressing that these helicopters are allowed to cross the path of airliners carrying hundreds of people! I do not understand why they are not crossed IN-BETWEEN arrivals,” a pilot angrily wrote in 2013 after his aircraft came within just 200 feet of a helicopter. The pilot added that ATC only called out the traffic one time — and that the helicopter was several hundred feet above where he should’ve been. Upon landing and making a call up to the tower, the pilot wrote that it took some “prodding” to even get an explanation from ATC on why his aircraft nearly grazed the helicopter.

“The FAA allows these aircrafts to operate in this environment and we have no choice, but to accept it and deal with it,” the pilot added.

Of the self-reported incidents the Caller reviewed, many pilots described coming within a few hundred feet of helicopters while descending into the Washington airport. Some near misses took place while planes were trying to land on Runway 33, the runway that the crashed American Airlines craft was set to land on. The Washington Post reported that Runway 33’s landing route takes jets within 15 feet of the top of the Route 4 helicopter corridor.

“The width of the Potomac [helicopters] are allowed to … pass [below airplanes]. But it’s kind of insane. Honestly, they should not, they shouldn’t have those routes that close to descending airplanes,” Pearson told the Caller.

A report from March 2015 details an airplane and a helicopter coming just a few hundred feet apart as the aircraft lined up to land on Runway 33. The pilot notes in his report that while starting to land, they spotted a helicopter that was close in altitude and climbing. The report explains that the pilot made a decision to abort the landing ahead of getting an alert that the other aircraft was too close to the plane.

After landing on a different runway, the pilot spoke to the tower about the near miss, learning that the helicopter had climbed far beyond where it was supposed to be.

“The tower supervisor I spoke with told me a few things that explained what may have happened. Number one, he said that the helicopters operating in that area should NEVER be above 200 feet. According to him, the helicopter was at 800 feet, clearly not where he was supposed to be,” the pilot writes, noting that he had his airplane climbed to 2,000 feet to avoid a crash.

“[The tower supervisor] also explained that ATC may have taken their eyes off the helicopter for a second because they would never expect those helicopters to do something that egregious. That seems plausible given the fact that I’ve never seen a helicopter in that area at that altitude. He suggested that it was most probably a deviation on the part of the Pilot of the helicopter, and a loss of aircraft separation that was also the fault of the helicopter pilot,” the report states.

Another 2015 report details a severe incident where the ATC failed to communicate another aircraft’s activity in the airplane’s path during its landing — just 400 feet from the ground.

“This occurred about 400 feet off the ground to the point where the pilot monitoring had to take the controls to make a correction in order to prevent it from becoming a midair collision,” the captain of the landing aircraft wrote.

“After there was action taken to make a correction from the close call, we were then informed by DCA tower of close traffic, although at that point it would have been too late,” the pilot added.

In May of 2013, another self report details another near miss while attempting to land on Runway 33. In this incident, the airplane pilot writes that, despite ATC asking the helicopter if it had the aircraft in sight and to maintain visual separation, the chopper made a turn that looked to be directly in the path of the airplane.

The turn caused the captain of the airplane to make a “hard turn” to avoid the helicopter.

Pearson explained to the Caller that one issue that is contributing to the near misses is that military and commercial pilots cannot hear each other because they are on different radio systems. Nearly all of the self-reported near misses reviewed by the Caller make a reference to Traffic Alert and Collision Avoidance Systems, which alert the plane and ATC if two aircrafts are on a collision course. These, Pearson told the Caller, are specifically designed to not be inhibited at low altitudes.

“Military and civilian traffic together adds a challenge. Part of our situational awareness is hearing what’s going on on the radio. When ATC transmits to the [military] guys we can hear them but can’t hear the [military] guys because they are on UHF and we are on VHF,” a commercial pilot told the Caller.

“A lot of accidents have been avoided by hearing another aircraft say something and it raising a red flag to you that you can bring to the attention of a controller,” the pilot continued to the Caller.

Several of the reports reviewed by the Caller cited the different radio frequencies as concerns for their near misses. Others said they had trouble understanding the helicopter pilots even if they were on the same frequency. Additional self reports made notes of the busy airport and the pressure to push airplanes in and out as quickly as possible as reasons for near misses.

“I understand DCA is a busy airport, I was based there for years. The military low-level helicopter traffic that routinely is in the DCA traffic area complicates matters,” a captain of a major carrier wrote in 2015. “But this is probably the most dangerous airport in the United States, strictly based on the fact the controllers are pushing, pushing, pushing, in an attempt to handle the traffic they have.”

Lack of communication between aircrafts and ATC regarding helicopters in the area of landing dates back to 1988, according to the Caller’s review of reports.

Pilots have also been expressing concern about the lack of separation between craft for decades.

“Non-standard separation over the river seems to be the norm for DCA for some reason. I have not encountered this type of [operation] at any other U.S. airport,” a pilot wrote in 2006.

The pilot details the difficult approach  at DCA and points out that his aircraft received several notifications through Traffic Alert and Collision Avoidance Systems. He opted to continue his landing, believing he had the two offending helicopters in sight, but later realized they had come within 200 feet of his plane. At the time, their Traffic Alert and Collision Avoidance Systems had also been inhibited because of low altitude.

“I have to question the wisdom of DCA [tower] letting helis fly in the [approach] path of one of the country’s highest profile airports, particularly on an [approach] as challenging as this one,” the pilot wrote.

And just two years ago, one air traffic controller flagged that control tower was short staffed, causing the individual to take on multiple roles at once. This contributed to a near miss between two military helicopters.

“I was working two positions combined of both helos/Local Control when the event happened,” the air traffic controller wrote.

A pilot summed up the general frustration with so many close calls after a 2006 incident: “Why does the tower allow such nonsense by the military in such a critical area? This is a safety issue, and needs to be fixed.”

Early reports about the Jan. 29 crash suggest several of the problems identified by pilots flying into DCA over the years contributed to the incident: a helicopter flying above altitude, limited visibility, a tight landing on Runway 33, and poor communication.

“Accidents are rarely result of a single failure but rather a series of failures that all have to line up. We refer to it as the swiss cheese model in the industry. ATC staffing, air space design, equipment limitations, night conditions. All the holes lined up that night. Plug one hole and everyone goes home to their families,” the commercial pilot explained.

As for the FAA, the agency did not have any explanation for why these reports were ignored for years, telling the Caller that its “reports are one of many data sources we use to identify system-level safety risks, which we can communicate through Safety Alerts for Operators.” It did not say whether any of the DCA reports over the decades had led to changes in DCA protocol or safety alerts to operators at the airport.

AUTHORS

Reagan Reese And Amber Duke

Contributors.

RELATED ARTICLE: ‘Bowing To Wokeness Since 2010’: Fmr Air Traffic Controller Says Short Staffing Is ‘Attributable To Obama Admin’

EDITORS NOTE: This Daily Caller column is republished with permisssion. ©All rights reserved.

New Trump Admin Policies Promote Marriage, Having Kids

In a clear contrast from the previous administration, the Trump administration is signaling that they are working to implement policies that support marriage and families and encourage couples to have children.

This week, Department of Transportation (DOT) Secretary Sean Duffy issued a memo announcing that the federal agency would “prioritize projects and goals” that “direct funding to local opportunity zones” and that “mitigate the unique impacts of DOT programs, policies, and activities on families and family-specific difficulties, such as the accessibility of transportation to families with young children, and give preference to communities with marriage and birth rates higher than the national average.”

Brad Wilcox, a fellow at the Institute for Family Studies and sociology professor at the University of Virginia, called the new policy “a very big deal,” writing that it “represents a creative move by one cabinet secretary in the Trump administration to take family policy in a new administrative direction — to boost the fortunes of the family not just through new laws but also new regulations, in an age when marriage and fertility rates in America have hit record lows.”

Wilcox went on to observe that the move “is likely to reorient transportation dollars to lower-density communities where there are more single-family homes, family life is often more affordable, and family formation is higher. So, more money for highways, and less for subways and light rail. This suggests that suburbs, exurbs, towns and rural communities where families with kids are more common are more likely to benefit from this Trump administration move.”

The DOT policy will likely be just the beginning of the family-focused policies that the Trump administration will attempt to implement. On the campaign trail last year, President Trump signaled that he would pursue the “maximum” for the child tax credit, which his first administration doubled to $2,000.

Vice President J.D. Vance has also emphasized that the Trump administration will prioritize expanding the child tax credit as well as other family-friendly policies, as he described during an interview on the campaign trail last August:

“[W]hat President Trump and I want to do on family policy is make it easier for families to start in the first place. We want to bring down housing costs so that if you have a baby, there’s actually a place to raise that baby. [We] want to increase and expand the child tax credit. We want to make it easier for moms and dads to not be shocked by these surprise medical bills when they go to an out-of-network provider. We’re working on all this stuff, and I think that’s ultimately how we turn down the temperature a little bit, is to make it easier to choose life in the first place. Because when you talk to women, you talk to moms and dads, a lot of times they feel like, if you have a pregnancy, especially an unexpected pregnancy, there just aren’t options. We want to provide more options so that people are raising families in a thriving and happy way in this country.”

Wilcox believes that affordable housing should indeed be high on the new administration’s to-do list. “Legislatively, the new administration should work with leaders in the House and Senate to get some version of Utah Sen. Mike Lee’s HOUSES Act (Helping Open Underutilized Space to Ensure Shelter Act) passed, which would lead to the construction of more than 2 million homes by turning over existing federal land to development,” he argued.

In addition, he contended that “the Trump team could take regulatory actions at the Department of the Interior, HUD and the Department of Agriculture to eliminate regulations that make building homes more expensive and possibly even turn over public lands to development.”

Compared to Trump’s first administration, “there are growing signs the second Trump administration will move much more aggressively to make America more family friendly,” Wilcox remarked.

AUTHOR

Dan Hart

Dan Hart is senior editor at The Washington Stand.

RELATED ARTICLES:

Finally! Family-friendly public policy for all Americans on the way

Living in the World, Not of It: The Balance of Finding Unity While Standing Firm in Truth

Reflecting on an NFL Season of Players Boldly Sharing Their Faith

Trump Creates Federal ‘Task Force to Eradicate Anti-Christian Bias’

EDITORS NOTE: This Washington Stand column is republished with permission. All rights reserved. ©2025 Family Research Council.


The Washington Stand is Family Research Council’s outlet for news and commentary from a biblical worldview. The Washington Stand is based in Washington, D.C. and is published by FRC, whose mission is to advance faith, family, and freedom in public policy and the culture from a biblical worldview. We invite you to stand with us by partnering with FRC.

Ten Bills, Ten Solutions to save America

Russ Vought, Political Director for Heritage Action for America, notes, “During the State of the Union address, President Obama called for 2014 to be a year of action. We agree, but Americans deserve action that will take the nation in the right direction. That’s why, with no clear goals or mandate from the Washington Establishment, we hosted the first Conservative Policy Summit.

On February 10th, Heritage Action brought together leaders to highlight conservative bills that would improve the lives of hardworking Americans. 10 speakers. 10 solutions.

[youtube]http://youtu.be/26d0H5Wl43M[/youtube]

Conservatives must lead through action. And we are. Heritage Action brought these leaders together on February 10th. The Conservative Policy Summit highlights the bills they have introduced, showing Americans a winning conservative reform agenda. Watch important discussion about our nation’s most pressing issues and learn about the conservative answers.

 

Privacy – Rep. Matt Salmon (R-AZ)
Social Welfare – Rep. Jim Jordan (R-OH) 
Health Care – Rep. Tom Price (R-GA) 
Health Care – Rep. Phil Roe (R-TN) 
Energy – Sen. Ted Cruz (R-TX)

Housing – Rep. Jeb Hensarling (R-TX)
Transportation – Rep. Tom Graves (R-GA)
School Choice – Sen. Tim Scott (R-SC)
Higher Education – Sen. Mike Lee (R-UT)
Religious Freedom – Rep. Raul Labrador (R-ID)

EDITORS NOTE: The featured image is courtesy of Claude Covo-Farchi. The use of this image does not in any way that suggests that Covo-Farchi endorses Heritage Action or the use of the work in this column. This file is licensed under the Creative Commons Attribution-Share Alike 2.0 Generic.

High-Speed Rail Fiasco will Break the Bank!

A national spider-web of high-speed rail is being pushed throughout America despite proof of “insolvency” and “never-ending subsidies.” Taxpayers need to know!

The fast-track towards US High-Speed-Rail was funded in the 2009 Stimulus, based on the President’s “80% High-Speed Rail 25-Year Plan,” even though the $10.1 Billion appropriate was quickly allocated, the high priority for deficit-reduction in the House of Representatives 2011 Budget, eliminated federal funds and High-Speed-Rail was derailed!

High Speed Rail Doomed: Too Expensive!

The Reason Foundation report forecasts U.S. High Speed Rail failure! European travel compared to America is apples-to-orange, because European rail transportation began pre-automobile, leading to the natural development of a full-service transportation system. This can’t be duplicated in America’s car-culture that provides cheaper and independent personalized travel. Reason.org reports the figures: Construction costs are $10 Million per mile and operational costs of $50,000 per seat, translating to $2.4 Billion for a 240-mile track that requires 6-to-9 million passengers to break even! The odds are against 25% of the country, as passenger ridership is concentrated in the highly populated New England corridor, monopolizing three-fourths of all US passengers, leaving all other projects scrambling for riders, subsidy-driven dollars and taxpayer obligations.
Treasure Coast Florida or New York’s Grand Central Terminal?

Similar to the Seven/50 Regional Planners in Florida, highly paid speculators pitch the Federal Railroad Administration and Department of Transportation goals for High-Speed-Rail to serve as a catalyst for growth, increase mobility, reduce national oil dependency, foster livable urban and rural communities, improve safety, maximize economic returns, environmental sustainability with US 33% greenhouse emissions.

On the other side of the fence! The International Energy Agency affirms that emissions in America are down to 1992 levels and California Air Resources Board recommends many more cost-effective ways to improve the air than through High-Speed-Rail! In truth, a massive train network will blast through America’s peaceful hometown communities: creating pollution, congestion, adding to higher density, enormous construction and funding costs while inflicting untold stress on overburdened economies!

Taxpayers Choose Savings: As Debt Rushes Towards $18 Trillion!

The ticket to rail success is selling tickets! On Amtrak’s Boston-Washington DC corridor, one-way tickets range from $146 – $420 per person, at $3.50 a gallon for the 438-mile trip, the $97.00 cost for car travel wins! Plus, the savings for door-to-door convenience, unlike train travel.

The Truth! There Are No High-Speed Trains in America!

In Ryan Holeywell’s 2013 article “Has High-Speed-Rail Been Derailed?” he emphasizes that High-Speed-Rail has not been achieved in America! The US Code defines high-speed as: “reasonably expected to reach sustained speeds of more than 125 miles per hour,” while Amtrak’s Acela Express, the only classified High-Speed-Rail, uses a flawed rating based on “sharing tracks with others trains.” Virtually the tracks alone create the need to average speeds, thus, preventing “sustained speeds of 125 miles per hour.” Travel speed times are easily distorted by adding, or dropping, train stops and, if the objective for HSR is to move people faster, High Speed Rail remains a fantasy!

California Budget-Busting High-Speed-Rail Boondoggle

While the California San Francisco-Los Angeles projects another $43 Billion from the Feds, the Government Accounting Office (GAO) argues that satisfying this obligation will be more than ALL national grants combined for subway, light-rail and bus transit. “Where is the money?”

California Congressman Jeff Denham, House Subcommittee on Rails, skeptical of the California business plan, forced transparency from Governor Jerry Brown who admitted his plan is to use Cap-and-Trade Pollution Trade Funds to match $2.5 Billion state obligation. This funding is highly controversial and Kathryn Phillips, Director of The Sierra Club, has aligned with the Tea Party against High-Speed-Rail. While the deadline for matching funds looms, the entire project hangs in balance, but Governor Brown aggressively pursues HSR!

Major problems are escalating in the first High-Speed rail state, even though Californians approved a $10 billion bond issue six years ago, they are now fraught with confusion and anger! Joe Nation, a public policy professor at Stanford University, reflected the frustration to the San Jose Mercury News “this could turn into a real nightmare.” Conflicts explode over imminent domain grabs, water issues delayed 20 years behind rail, inflated ridership projections and low ticket prices creating endless subsidies.

Yes Nevada’s Senator Harry Reid, presses to reactivate his $5.5 Billion stimulus monies cancelled when the supplier was revealed as the Canadian Bombardier Company, in direct violation of the Buy-America law.

All Aboard Florida – Private Industry Hijacks Taxpayers!

As soon as Florida turned down a federal grant for HSR, Florida East Coast Industries (FECI) conveniently introduced “All Aboard Florida” – the first private high-speed railway. Since FECI owns the rail corridor, and strategic building plots in Miami and Orlando, this will be profitable venture for their bottom line, but Treasure Coast taxpayers, with already-strained budgets, are required to pony-up millions to implement AAF’s private venture and then endure the environmental-assault of 35 round-trip “sort-of-high-speed trains” as they whiz through, once peaceful, beachside communities. No profit for Treasure Coast taxpayers!

Treasure Coast Vs. Grand Central Station?

Before “All Aboard Florida,” Florida Department of Transportation and Amtrak, were discussing new Miami-Orlando passenger service with seven new stations stops! If all of these projected plans eventuate, the lifestyle of paradise along the Treasure Coast will be transformed into the hectic pace of Grand Central Station! When tourism is Florida’s shining star, and money-maker, why would efforts continue to diminish this success?
Let Failure Be the Guide for the Wise!

Randal O’Toole of the Cato Institute in his article: “Defining Success, The Case Against Rail Transit,” outlines what All Aboard Florida could have in store for their bottom line! The Miami-West Palm 1989-debacle that cost the SE Florida Regional Transportation Authority (Tri-Rail) $53 million, with a $9 million return and $1 Billion capital improvement for double tracking of 71 miles, was projected to create 30,000 new riders and, astoundingly in 2008, resulted in a meager 13,000 new riders. Pretty steep fare at $76,923 per new customer! The good news is that sensible riders chose the $14.62 car travel instead! Failure still looms with Tri-Rail’s $30 million deficit!

The heroes in this grand-picture are Governor Scott Walker of Wisconsin, Governor John Kasich of Ohio and Florida’s Governor Rick Scott – who used wise judgment to reject federal grants and put taxpayer concerns above speculation. Governor Scott saw the writing on the wall, when comparing the proposed ridership of 3 million, to the busy New York Acela’s real riders of 3.2 million, highlighting a highly unobtainable goal. Hopefully this story rings-a-bell for politicians rushing towards a doomed financial fiasco!

Taxpayer Loyalty Pays, While Breaking the Bank Does NOT Pay!

EDITORS NOTE: The featured image is courtesy of SignalPAD and is licensed under the Creative Commons Attribution-Share Alike 2.0 Generic. SignalPAD does not in any way  endorse this author or DrRichSwier.com and their use of SignalPAD’s original work.