Showing posts with label NTSB. Show all posts
Showing posts with label NTSB. Show all posts

Sunday, September 6, 2026

UPDATE: Amazon Cargo Plane mishap at Miami airport results in 5 deaths and 5 serious injuries


We now know that at least five people were killed, and five others were seriously injured, at Miami International Airport on Sunday after an Amazon cargo plane overran the runway, struck multiple vehicles and caught fire while landing.

The Miami-Dade Sheriff’s Office (MDSO) and Miami-Dade Fire Rescue (MDFR) confirmed that there were at least 10 victims involved in the crash, which happened when Prime Air flight 7598 overran Miami International Airport’s diagonal runway [number 30] at about 2 p.m. local time.

An Amazon spokesperson expressed condolences following the devastating crash at Miami International Airport that left five people dead.

"We're heartbroken to learn that five people lost their lives in today’s incident at Miami International Airport. Our deepest sympathies go out to the families, loved ones, and all those affected by this devastating loss," the company said.

The tragedy unfolded Sunday afternoon after an Amazon Prime Air Boeing 767 operated by 21 Air crashed while attempting to land at the airport.

Fire Chief Raied Jadallah said three people were transported to a trauma center in critical condition, while two others were taken to a local hospital.

Miami-Dade County Mayor Daniella Levine Cava said rescue crews wasted no time responding to the crash.

The rescue team "was there within seconds of the crash," Cava said.

Firefighters were also dealing with a dangerous fuel leak from the aircraft.


"We do still have an active fuel leak that's occurring off of the aircraft that is being mitigated," Jadallah said.

Fire officials told Fox News Digital that the fire originated in the aircraft's engine. HazMat crews were able to safely shut down the engine while firefighters worked to contain the fuel leak.

"Firefighters encountered a complex engine compartment fire and used foam from specialized airport firefighting units to extinguish the flames," officials said.

The crash also involved vehicles on the roadway, leaving several victims trapped inside their cars. According to Miami-Dade Fire Rescue, one victim required "extrication" by specialized technical rescue personnel.

Crews simultaneously launched search-and-rescue operations for the pilots and co-pilots, who officials said were trapped inside the cockpit. Emergency personnel also worked to locate and evaluate patients scattered throughout the crash site.

The scale of the emergency response was massive. More than 60 fire units and approximately 200 personnel rushed to the scene after the aircraft crashed and came to a stop beyond the airport operations boundary.

"Units arrived to find an airplane that had caught on fire as a result of this crash, with heavy flames and smoke showing. Firefighters are working on extinguishing the fire and assessing patients," the Miami-Dade Fire Rescue said in a post on X.

MDFR has since shifted into a supporting role, with units remaining at the scene to assist other agencies investigating and responding to the disaster.


Amazon confirmed that the aircraft experienced an "incident" while attempting to land, though the company did not immediately provide details about what caused the crash.

"We can confirm that an Amazon Air plane operated by 21 Air experienced an incident while attempting to land at Miami International Airport today," Amazon said.

"This is a fast-moving situation and we're still gathering details. We're working closely with local authorities and officials to understand exactly what happened. Right now, our absolute priority is the safety, well-being, and care of everyone involved. We're doing everything we can to support those affected."

Boeing also weighed in, confirming that the aircraft has been flying for decades.

The aerospace giant told Fox News that the Boeing 767 was originally delivered as a passenger aircraft in 1994 before later being converted into a freighter.

"Boeing extends our deepest condolences to the families and loved ones of those who lost their lives in the accident in Miami. Our hearts go out to those injured and affected by this tragedy. Boeing is supporting the investigation led by the U.S National Transportation Safety Board," the company said.

The Federal Aviation Administration said 21 Air Flight 7598, a Boeing 767-300, had departed Luis Muñoz Marín International Airport in San Juan, Puerto Rico.

County CAD records indicate that the emergency call came in at approximately 1:55 p.m.

Cava said local officials were closely monitoring the situation as emergency crews continued their work.

"Right now, our focus is on everyone involved and making sure our first responders have what they need. We will provide updates as we learn more," she said in a post on X.

The crash immediately disrupted operations at one of the nation's busiest airports.


Department of Transportation Secretary Sean Duffy said authorities had issued a full ground stop while first responders assessed the wreckage and dealt with the emergency.

"We’ve issued a full ground stop at Miami International while first responders assess the scene after an Amazon cargo plane overran the runway. If you’re traveling through the area, please expect significant delays and potential cancellations," he said in a post on X.

Airport officials later announced that one runway had reopened, but warned that they were "still experiencing impacts from this incident."

Passengers scheduled to fly out of Miami on Sunday were urged to check directly with their airlines for the latest flight information before heading to the airport.

For now, investigators face the grim task of determining exactly what went wrong during the landing and how an aircraft carrying cargo ended up crashing beyond the airport's operations boundary and striking vehicles on the ground.

The investigation will ultimately have to provide answers, but for the families of those who died, no explanation can undo the loss suffered Sunday in Miami.

The National Transportation Safety Board is sending Jennifer Homendy. She is the Chairwoman of the NTSB and reports say she'll be leading the team investigating the crash. The NTSB has an office in Miami so the investigation should start very soon.

Thanks for following Brain Flushings. Please take time to check out the sponsors on this page--it's one way to support my work and you don't need to purchase anything to do so. Of course, you can Buy Me A Coffee at any amount if you want to support me directly. And finally, don't be afraid to subscribe if you enjoy the blog--it's free, and worth the cost.


Sunday, May 4, 2025

Planes forcedto 'go-arounds' after Army helicopter's 'scenic' route to Pentagon



The skies over D.C. just got a little too wild for comfort. In a move that screams “rules are for suckers,” a U.S. Army Black Hawk helicopter decided to play tourist over the Pentagon, forcing two commercial flights to pull a “not today” and circle back for safer landings. This wasn’t just a minor oops—it’s the kind of thing that makes you wonder if someone’s trying to turn Reagan National into an action movie set.

According to the National Transportation Safety Board, which is now digging into this mess alongside the FAA, a Delta Air Lines Airbus A319 (Flight 1671) and a Republic Airways Embraer E170 (Flight 5825) were told to hit the brakes—mid-air—around 2:30 p.m. EST on Thursday. Why? Because this Black Hawk was apparently taking the long way home to the Pentagon from Fort Belvoir, Virginia, looping around the south and east sides like it was sightseeing. 

The Washington Post got hold of an FAA summary that called the route “scenic.” Scenic! As if this chopper was out there snapping selfies with the Lincoln Memorial.

Now, let’s talk numbers: Flight 1671, carrying 97 passengers and five crew from Orlando, had to abort its landing first. Then, Flight 5825 came within a half mile of kissing this Black Hawk, which was cruising just 200 feet below it. Oh, and for a few heart-stopping seconds, the helicopter’s radar tracker went dark. Because nothing says “everything’s fine” like a military chopper going stealth in one of the busiest airspaces in the country.

The FAA insists the helicopter didn’t stray into newly restricted airspace—put in place after a horrific mid-air collision earlier this year between a commercial plane and another Black Hawk that killed 67 people. 

But that’s cold comfort when you’re a passenger on a plane dodging a military joyride. U.S. Army spokesperson Capt. Victoria Goldfedib told NBC News the chopper was “in accordance with published FAA flight routes and DCA Air Traffic Control,” but an anonymous Army official scoffed at the “scenic” label. Sure, buddy, it was just business as usual, not a Pentagon parade.

Enter Transportation Secretary Sean Duffy, who is, shall we say, not amused. 

Duffy called the incident “unacceptable” and laid it out plain: “Our helicopter restrictions around DCA are crystal clear. Safety must ALWAYS come first. We just lost 67 souls! No more helicopter rides for VIPs or unnecessary training in a congested DCA airspace full of civilians. Take a taxi or Uber -- besides most VIPs have black car service.” Preach, Sean! He’s vowing to have a come-to-Jesus chat with the Defense Department about “why the hell” the rules were “disregarded.” 

I’d love to be a fly on the wall for that one.

Look, I get it—military helicopters are cool, and the Pentagon’s a big deal. But this isn’t Top Gun. We’re talking about civilian planes packed with families, business travelers, and probably a few folks just trying to get home to their dogs. The skies around D.C. are congested enough without some hotshot pilot turning it into their personal playground. Duffy’s right: if you’re a VIP, call your driver. If you’re training, find a less crowded sandbox. And for the love of all that’s holy, keep your radar on. We’ve got enough drama on the ground without adding near-misses in the air.

If you enjoy my blog, feel free to toss a virtual coffee my way on Buy Me a Coffee – it’s like a high-five with caffeine! No pressure, it's your call.


Thursday, January 30, 2025

BREAKING: Latest on Reagan Int'l Airport Situation


A U.S. Army Blackhawk helicopter [Sikorsky UH-60] and an American Airlines regional jet crashed into the frigid waters of the Potomac River at around 8:48 p.m. Wednesday night. The jet was in the process of landing at Reagan International Airport.

Chief of District of Columbia Fire Department John Donnelly gave the sad news, "we don't think there are any survivors from this accident.” The fact is, being that the water in the river is around 35 degrees F. the probability that anyone remains alive is practically zero.

“We have recovered 27 people from the plane and one from the helicopter,” the Chief added.

“Despite all these efforts, we are now at a point where we are switching from a rescue operation to a recovery operation,” he also said.

"The district office of the medical examiner has lead on reuniting these bodies and these people, with their loved ones," Donnelly added, "and we will continue to work to find all the bodies and collect them. and reunite them with their loved ones."


Aviation expert Kyle Bailey told Fox News Digital that "[I]t was a perfect storm of events [that happened last night]." He compared the tragic event to being struck by lightning and noted that it was "unfair to cast blame at this early stage."

“The U.S. military runs an incredible aviation operation,” he said. “But distractions do happen, and all humans make errors."

One possible reason this tragedy may have occurred is that the military uses UHF frequencies to communicate while civilian aircraft use VHF (Very High Frequency) generally between 118 MHz and 137 MHz. There could have been a miscommunication or delay that interrupted the flow of information needed to avoid the collision. Of course, it's too soon to speculate as this is a recent event.

I sincerely hope much is learned from this tragedy as it is investigated by the NTSB and FAA. 

May the friends and families of the victims find peace in their grieving. 

Iran regime's January crackdown murdered 221 children

In late December 2025, economic grievances ignited nationwide protests in the Islamic Republic of Iran that rapidly escalated into systemic...