Tag: plane crash

Officials Say Aircraft Material of “Unknown Origin” Was Found at Recent Site of Mysterious Crash Near Area 51

Officials have revealed an odd turn of events involving ongoing investigations into a mysterious crash in the Nevada desert last month, which occurred near the classified U.S. Air Force facility Area 51.

On September 23, 2025, a non-fatal crash involving an aircraft was reported northeast of Las Vegas near the famous high-security facility, prompting the Federal Aviation Administration (FAA) to issue a temporary flight restriction (TFR) covering a five-nautical-mile area east of the secretive base.

The TFR advised that the restriction was in place for reasons involving “national security,” and the site of the crash was subsequently cleared by U.S. Air Force officials.

“There were no fatalities, injuries or property damage,” read a statement provided by 432d Air Expeditionary Wing Public Affairs in response to inquiries made by The Debrief on September 30, 2025.

“The incident is under investigation,” the statement read, adding that no additional details were available about the situation at that time.

That all changed last weekend, when the 432d Wing issued a new release providing the first official update on the situation in several days, which included a series of puzzling new developments.

“During a follow-on site survey on October 3rd, investigators discovered signs of tampering at the mishap location,” the October 4 release stated, “including the presence of an inert training bomb body and an aircraft panel of unknown origin that were placed on the site post-incident.”

The Debrief reached out to 432d Air Expeditionary Wing Public Affairs again on October 10, seeking any additional details that could be provided about the situation, but had received no response to our query as of the time of publication.

The aircraft involved in the initial September 23 incident has not been officially identified, although it is believed to have been an unmanned aerial vehicle (UAV), according to Dreamland Resort, a website that has chronicled news and discussions related to Area 51 and U.S. government black projects for decades.

Joerg Arnu, the site’s founder and webmaster, traveled to the area where the crash occurred shortly after officials had cleared the site, documenting his visit in a video that appeared on his YouTube page on September 29.

In an article about the incident posted on his website on October 10, Arnu wrote that while the official statements provided by the U.S. Air Force attribute the aircraft crash to a unit operating from Creech AFB, security radio communications reportedly overheard shortly after the incident may have potentially linked it to a hangar at Area 51.

Keep reading

FBI Investigates Tampering of Area 51 Crash Site

The FBI is investigating the site of a military plane crash outside Area 51 that was tampered with after cleanup. According to a press release from nearby Creech Air Force Base, workers cleared the scene of a non-fatal training accident by September 27, yet on October 3 they found someone at the site had placed an inert bomb, as well as an “aircraft panel of unknown origin.” The explosive device appeared to be for training purposes only.

The spot under investigation sits just 12 miles east of Area 51, a facility known for its ironclad security and rumored involvement in UFO recovery. The Federal Aviation Administration set a tightly monitored five-day flight restriction over the region following the initial crash, making the appearance of random debris all the more mysterious.

Keep reading

NTSB chair blasts FAA over deadly DC crash: ‘Are you kidding me? 67 people are dead’

The head of the National Transportation Safety Board (NTSB) criticized the Federal Aviation Administration for not “taking ownership” in the deadly Black Hawk helicopter collision with a passenger jet near Washington Reagan National Airport in January.

During a hearing on Wednesday that is set to continue this week, NTSB Chair Jennifer Homendy alleged that some FAA tower employees knew there “was a problem” with U.S. Army helicopters flying in close proximity to passenger aircraft near the airport.

Sixty-seven people died on Jan. 29 after a regional American Airlines jet collided with an Army Black Hawk helicopter over Washington, D.C., officials said, the nation’s first major commercial airline crash since 2009.

The Army helicopter was on a training flight at the time of the collision.

“Every sign was there, that there was a safety risk and the tower was telling you that,” Homendy said of the air traffic controllers working at Reagan National Airport (DCA) at the time.

“Yet you know what FAA did, after the accident occurred, you transferred out the air traffic manager, two assistant general managers,” Homendy continued. “You transferred people out instead of taking ownership over the fact that everybody in FAA tower was saying there was a problem.”

According to Homendy, who cited FAA surveillance data, there were over 15,000 close proximity events between helicopters and commercial aircraft at DCA between October 2021 and December 2024.

Keep reading

The Anniversary They Want You to Forget: TWA Flight 800 and the Deep State’s Deadliest Lie

On July 17, 1996, 230 men, women, and children boarded TWA Flight 800 for Paris. Twelve minutes later, their lives were incinerated in midair. And for nearly three decades, the American government has done everything short of setting the ocean on fire to bury the truth.

Last week marked the 28th anniversary of that explosion. You didn’t hear much about it from CNN, or MSNBC, or even the White House. 

Of course you didn’t. 

The people who peddled Russiagate, the Hunter laptop hoax, and the now-laughable myth of President Joe Biden’s cognitive abilities are the same types of bureaucrats who sterilized the truth in 1996 to protect their golden boy: President Bill Clinton.

Because make no mistake: What happened to TWA 800 wasn’t just a tragedy. It was a cover-up soaked in blood.

The Missile Theory They Mock Until You Read the Evidence

The official story goes something like this: A fuel-air explosion inside the center-wing tank was caused by an electrical short. The problem? That has never happened before or since in the history of commercial aviation. 

And more than 200 eyewitnesses, many of them military-trained, reported a streak of light arcing up from the horizon, then a fireball.

You don’t have to believe some Reddit thread. Just read Jack Cashill. In his exhaustive investigation, “TWA 800: The Crash, the Cover-Up, and the Conspiracy,” Cashill compiles the following:

  • FBI 302 reports of eyewitnesses that were altered or disappeared.
  • Radar data showed unidentified objects rapidly approaching the plane.
  • Explosive residue on passenger seats and debris, which the FBI later claimed came from contamination, after initially labeling it “consistent with missile fuel.”
  • Whistleblowers, such as Navy Commander William Donaldson and TWA Captain Terry Stacey, were stonewalled or reassigned for raising concerns.

This wasn’t a malfunction. It was a missile strike, almost certainly fired accidentally by the U.S. Navy during a live-fire exercise, and then intentionally buried to avoid scandal in an election year.

The FBI’s War Against the Truth

While families grieved and the country mourned, the FBI moved fast, not to solve the case, but to seize control of the narrative. Within hours, they had muscled the NTSB out of the lead, quarantined key wreckage, and steered the media toward mechanical failure.

When physicist Tom Stalcup and several NTSB investigators tried to reopen the case in 2013 with new radar analysis and 3D modeling, their petition was denied. 

The response? 

There’s “no compelling evidence.” Of course not, because you people shredded it.

Keep reading

Boeing Deal With DOJ Proves That ‘Justice’ Is a Slippery Concept

Some seven years after Lion Air flight 610 crashed into the Java Sea in Indonesia shortly after take off, Boeing has made a deal with the U.S. Department of Justice (DOJ) that will mean that the aircraft manufacturer will not face criminal prosecution for the crash that killed 189 people.

In court documents filed last Friday, Boeing agreed to a settlement of investment and compensation totaling $1.1 billion, some $445 million of which is to be paid to the families of the victims of both the Lion Air crash and the Ethiopian Airlines crash that occurred just five months later.

Both planes were 737 Max aircraft manufactured by Boeing, and had been fitted with a new flight maneuvering system known as MCAS. The rationale was that the MCAS system would make flying safer by detecting if planes were about to stall and forcing the nose of the aircraft down. However, Boeing had not informed either pilots or airlines about the new system, nor its potentially deadly faults.

In both crashes, sensors mounted on the exterior of the aircraft malfunctioned, incorrectly identifying a stall and forcing the planes towards the ground, as pilots desperately tried to override the MCAS system that they had not been trained to operate.

The Lion Air and Ethiopian Airlines crashes killed 346 people in total, and led to a series of “deals” with Boeing under which it paid various fines and compensation to victims’ families, including a $2.5 billion settlement in 2021.

However, after it was found that Boeing had misled the Federal Aviation Association (FAA) about the safety of its aircraft, possible criminal charges were discussed, with Boeing entering a plea deal in which it would plead guilty to federal fraud charges in 2024 – although the deal was subsequently rejected.

Now, the new deal has been announced that will allow Boeing to essentially pay its way out of any criminal sanctions, prompting the question of whether justice has been served.

What constitutes “justice” is highly subjective, depending on who is defining the term.

Keep reading

After Blaming Trump, Pete Buttigieg Implicated in Washington National Air Traffic Control Scandal

As Pete Buttigieg attempts to stand up a 2028 presidential campaign by growing a patchy beard, he might want to consider that his record could be a major liability. 

On Wednesday, it was revealed that a key hotline between the Pentagon and the air traffic control at Washington National Airport has been inoperative since 2022. But what would have been a mundane failure turned deadly in January when a military helicopter collided with a regional airliner, killing 67 people. That phone line would have typically been used by the Department of Defense to report when its aircraft were in the vicinity and what their intentions were.

A hotline connecting air traffic controllers at Reagan National Airport and their counterparts at the Pentagon has been “inoperable” since March 2022, a Federal Aviation Administration official confirmed Wednesday, further evidence of poor safety coordination between federal agencies responsible for the airspace where a midair collision in January killed 67 people.

The line is maintained by the Defense Department, and the aviation agency was not aware of the outage during the three years it was down, Franklin McIntosh, the FAA’s deputy head of air traffic control, testified at a Senate hearing Wednesday. Aviation officials discovered the hotline wasn’t working after May 1, when controllers at National ordered two passenger jets to abandon landings because an Army helicopter was circling nearby at the Pentagon.

Hotlines between adjoining air traffic control sectors and airport towers are common across the national airspace to help with coordination, and the line to the Pentagon would have served the same purpose. Who was in charge in 2022 when it went offline and then spent the next three years not being repaired? That would be Pete Buttigieg, whose most notable action as transportation secretary was taking a long “paternity leave” without letting the public know he was leaving his job as a cabinet official for several months.

Now, we know why Buttigieg rushed to blame the Trump administration after the January crash. 

Keep reading

Russia rejects ‘biased’ UN ruling on 2014 downing of Malaysian airliner

The Kremlin on May 13 rejected as biased a ruling by the UN aviation council that Russia was responsible for the downing of a Malaysian airliner over Ukraine in 2017 that killed all 298 passengers and crew.

“Our position is well known. You know that Russia was not a country that took part in the investigation of this incident, so we do not accept any biased conclusions,” Kremlin spokesman Dmitry Peskov said.

Malaysian Airlines Flight MH17 departed from Amsterdam for Kuala Lumpur on July 17, 2014, and was shot down over eastern Ukraine as fighting raged between pro-Russian separatists and Ukrainian forces.

The victims included 196 Dutch citizens and 38 Australian citizens or residents.

In November 2022, Dutch judges convicted two Russian men and a Ukrainian man in absentia of murder for their role in the attack. Moscow called the ruling “scandalous” and said it would not extradite its citizens.

Keep reading

The New York Times “investigates” the DC jet crash – and buries the truth it finds

The New York Times cannot stop mangling the truth to serve its political goals.

On Sunday, the paper exhaustively examined the collision between an Army Black Hawk and an American Airlines jet that killed 67 people over the Potomac in January.

The massive 4,000-word article claimed the crash had many causes, including an overworked air traffic controller. “Missteps, Equipment Problems and a Common but Risky Practice Led to a Fatal Crash,” the Times proclaimed.

Except that’s not really what happened. Or what the Times found.

Yes, the controller was busy. Yes, the Black Hawk pilots wore night-vision goggles that can, ironically, complicate seeing in cities with lots of ambient light.

Those choices and problems raised the risks of an accident.

But despite all the words the Times devoted to explaining the crash, its root cause was simple. The Black Hawk was flying too high. It flew directly into the CRJ700 regional jet. The plane’s pilots and passengers had no chance.

That’s the reality. The second reality is that an inexperienced female Army pilot, Capt. Rebecca Lobach, 28, (CORRECTION: original article said 36) was at the controls of the Black Hawk when it hit the CRJ700, on a training and evaluation mission.

What the Times actually found, the news in the article, is that the Lobach’s copilot repeatedly warned her the helicopter needed to descend in the minutes before the accident. Just seconds before the crash, he suggested she tack left, a path that would likely have avoided the jet.

She didn’t respond.

In other words, the story here is that Lobach — who had never deployed overseas but had volunteered in the Biden White House and whose obituary prominently called her a certified advocate for “sexual harassment” victims — flew her helicopter into a passenger jet and killed 67 people, including herself.

Keep reading

New Details Emerge About Female Pilot Rebecca Lobach’s Shocking Negligence Before Helicopter-Plane Collision Near DC’s Reagan Airport

New details about the fatal helicopter-plane crash near DC’s Reagan Airport reveal the female pilot was repeatedly ignored warnings from her male co-pilot to turn away but she flew right into the passenger jet.

An American Airlines flight carrying approximately 64 souls collided with a Blackhawk helicopter near Washington D.C. Reagan National Airport (DCA) in late January.

All 64 passengers in the jet were killed.
The three pilots in the Blackhawk helicopter also died in the explosive crash.

A preliminary FAA report indicated that staffing at the DCA Air Traffic Control tower was “not normal” at the time of the helicopter-plane collision.

According to NBC News, at the time of the collision, one controller was overseeing both helicopter and airplane traffic.

Typically, one controller focuses on helicopter activity.

Webcam video from the Kennedy Center showed the Blackhawk helicopter flying right into the American Airlines plane.

Keep reading

Why Are There So Many Aviation Accidents?

While the latest aviation safety issues and accidents over the last few months scare some, to seasoned professionals the aviation tragedies and near misses do not come as a surprise. The only question is: Why did it take so long?

There’s a long list of safety failures in the airline industry. United Airlines B777 plunged to the Pacific during climb in 2023, and the Federal Aviation Administration (FAA), United, and the National Transportation Safety Board (NTSB) didn’t investigate it for months. A 265-pound main tire fell off a B777 taking off out of Los Angeles; it fell from over 200 feet — still spinning — into an airport parking lot. The nose tire came off a taxiing B757. Two mechanics were killed when an incorrectly pressurized tire exploded in Atlanta. Most memorable were the Endeavour regional jet that flipped in Toronto, the mid-air collision between a PSA Airlines regional plane and a military helicopter, and an Endeavour regional aircraft that struck a wing during a go-around at La Guardia airport. More such events never made the news or were easily forgotten.

Boeing’s 737-Max was a failure on so many levels. But it wasn’t Boeing’s failure, as people were led to believe. Boeing makes products. Airlines buy these aircraft for technological improvements. It’s solely the airline’s responsibility to properly train their pilots and technicians to operate and maintain the aircraft — not the manufacturer’s.

The Alaska Airlines flight 1282 door plug loss was Boeing’s fault; but Boeing didn’t own it alone. Blame for that failure was shared with the FAA, the contract fuselage producer, Spirit AeroSystems, and the NTSB. All missed the important cues. They permitted breakdowns in quality control; both internal and external quality evaluations were ignored and almost cost a plane full of people their lives. It’s impossible to analyze these multiple facts in so short a space, but Alaska flight 1282 was never recognized for what it was: a symptom.

Keep reading