The Navy has a choice: Get better or become less relevant



The Navy has been through a lot over the past several months.

Ships have stayed at sea longer than planned. Sailors have missed more time with their families. Aircraft have flown hard. Weapons have been fired in numbers we have not seen in decades. Maintenance has been pushed to the right because the mission came first.

We cannot keep shrinking the number of ships while expanding the number of missions and pretend the math will somehow work.

Now the bills are going to start coming due.

Ships will return needing repairs. Aircraft will need maintenance. Magazines will need to be refilled. Sailors will need time at home. Families that have carried an enormous burden will want some normalcy back. All of that is understandable. But what happens next will tell us a lot about the future of the United States Navy.

We can spend the next few years talking about how hard the Iran fight was, how tired the force is, and how much everything costs. We can lower expectations, reduce deployments, accept fewer ships at sea, and convince ourselves that this is simply the new reality.

Or we can decide to get better.

That may sound overly simple, but it isn’t. This is the choice facing this generation of Navy leaders, Pentagon officials, members of Congress, and the defense industrial base. Iran did not create the Navy’s problems. It exposed them.

Listen to sailors and learn the right lesson

The extended deployment of the USS Abraham Lincoln has become the most visible example of the strain on the force. Sailors and families have expressed frustration about deployment length, uncertainty, limited port calls, and conditions aboard the ship.

When we ask young Americans to spend month after month away from their spouses and children, they have earned the right to tell us when things are not working. Navy leaders should pay attention to quality of life, communications, food, sleep, medical care, and the information families receive back home.

But we should be careful about the conclusion we draw from their frustration. The lesson cannot simply be that deployments should never run long again. Wars don’t care about deployment schedules.

America’s national security commitments don’t disappear because a carrier strike group has been gone for eight or nine months.

Sometimes the mission requires more.

The real lesson is that America needs enough Navy that asking more of our sailors during a crisis does not become the only option available. That means more ships, more aircraft, more weapons, more logistics capacity, and more people.

It also means accepting something we sometimes became uncomfortable saying during the long years of peacetime operations: Serving in the military is supposed to be hard.

We should take care of sailors and their families. We should fix unnecessary problems and hold leaders accountable for poor decisions. But we also need a Navy that expects its people to be tough enough to fight and win a war.

RELATED: China is building power. America is still debating it.

Yuan Hongyan/VCG/Getty Images

The maintenance bill is coming

The bigger problem may be what happens when these ships finally come home.

Engines accumulate hours. Aircraft fly more sorties. Radars and combat systems operate continuously. Parts wear out. Repairs that might normally happen during a deployment get delayed because the ship is needed on station.

Eventually all of that work has to be done. And the Navy was already struggling with maintenance before the war. Public shipyards are overloaded. Private repair yards are stretched. Submarine maintenance has been a problem for years. Surface ships routinely spend longer in maintenance than planned.

Now we are going to add ships returning from combat operations. We should not act surprised when the backlog grows. The question is whether we do something about it.

That means putting real money into ship repair capacity. It means expanding public and private yards. It means training more welders, electricians, pipe fitters, and other skilled workers. It means using predictive maintenance and better data, so we know what is going to fail before it fails.

And it means getting serious about spare parts.

None of this is glamorous. There are no ribbon cuttings for having the right pump sitting on a warehouse shelf. But wars are often won by the side that can keep equipment operating.

Refill the magazines

Iran also reminded us that modern warfare burns through weapons quickly.

Missiles that take years to develop and months or years to produce can disappear from a ship’s magazine in minutes.

That should scare us, not because the Navy performed poorly — it performed extremely well — but because Iran is not China.

Imagine the weapons requirements of a sustained fight across thousands of miles of the Pacific against an adversary with a large navy, advanced aircraft, submarines, ballistic missiles, cruise missiles, and enormous industrial capacity.

The math gets uncomfortable quickly.

We should treat every weapon fired during the Iran conflict as a data point.

How quickly can we replace it?

If the answer is measured in years, we have a problem.

This is where the Pentagon and Congress need to stop treating munitions like boutique acquisition programs. We need production lines that can surge. We need long-term contracts that give manufacturers confidence to invest. We need second sources for critical components.

And we need deeper magazines.

You cannot surge missile production after the shooting starts.

Don’t become the Royal Navy

There is a historical warning here.

The British Royal Navy did not wake up one morning and suddenly stop being the world’s dominant navy.

The decline happened slowly.

Britain still had excellent ships. It still had talented sailors. It still had proud traditions. What it gradually lost was mass. The commitments remained large while the fleet became smaller. That should sound familiar.

America expects its Navy to deter China, operate in Europe, protect shipping in the Middle East, defend the homeland, reassure allies, and respond whenever something goes wrong anywhere in the world.

We cannot keep shrinking the number of ships while expanding the number of missions and pretend the math will somehow work. Eventually something gives. Iran gave us a warning. We should take it.

RELATED: How to renew American scientific research

BSIP/UIG/Getty Images

Get better

There will be a temptation after this conflict to focus almost entirely on recovery. The Navy absolutely needs to recover. But recovery cannot become retreat. This needs to be a period of brutal institutional learning.

What broke? What ran out? What took too long to repair? Which supply chains failed?

Capture those lessons and move out — don’t spend five years studying them.

Some fixes will require money. Others will require leadership. Many will require getting rid of processes and assumptions that made sense during peacetime but make no sense after experiencing sustained combat.

This should change how the Navy trains, buys weapons, maintains ships, designs the fleet, and supports families.

Most importantly, it should change the Navy’s mindset.

The service should come out of this tougher than it went in.

The choice

Every generation gets a few moments when the direction of an institution can change.

This is one of them.

Iran showed what sustained combat does to a Navy. A war with a peer competitor would ask far more. So we have a choice — slump our shoulders and talk about how difficult this is and how far behind we feel.

Or we can stop talking, learn from the last couple of years, and get better.

Fix the ships. Refill the magazines. Expand the yards.

Take care of Navy families. Demand better leadership. And expect toughness from the force.

The United States Navy is still the most capable navy in the world. The question is whether we intend to keep it that way.

Iran should not be remembered as the fight that wore down the U.S. Navy. It should be remembered as the fight that woke it up.

This article was originally published by RealClearDefense and made available via RealClearWire.

'I messed up': LaGuardia Airport shut down after deadly collision



Two are dead and scores more are injured after a plane collided with a fire truck at New York's LaGuardia Airport.

When touching down on Runway 4 at approximately 11:40 p.m. on Sunday, an Air Canada Express CRJ-900 plane operated by regional partner Jazz Aviation struck a Port Authority Airport Rescue and Firefighting vehicle that was responding to a separate incident, said the airport.

'That wasn't good to watch.'

Jazz Aviation confirmed that flight 8646 was en route to LaGuardia from Montreal and carrying 72 passengers and four crew members.

Kathryn Garcia, executive director of the Port Authority of New York and New Jersey, said during a press conference early Monday morning that "initial numbers indicate that 41 passengers and crew were transported to the hospital as well as the [Airport Rescue] officers. At this time, we understand that 32 have been released, but there are also serious injuries."

Garcia confirmed that the pilot and first officer of the Air Canada flight were killed in the collision. The sergeant and the officer who were inside the truck are in stable condition with no life-threatening injuries.

Air Canada said in a statement, "We are deeply saddened by the loss of two Jazz employees, and our deepest condolences go out to the entire Jazz community and their families."

RELATED: One crash, one derailment — and Congress still can’t follow the data

Selcuk Acar/Anadolu via Getty Images

Jack Cabot, a passenger on the ill-fated flight, said, "We went down for a regular landing. We came in pretty hard. We immediately hit something, and it was just chaos in there. About five seconds later, we had come to a stop, but in that short period, I mean, everybody was hunkered down and everybody was screaming pretty quickly," reported Canadian state media.

"We didn't have any directions because the pilot's cabin had been kind of destroyed, so somebody said, 'Let's get the emergency exit and get the door and let's all jump out,' and that's exactly what we did," added Cabot.

In audio capturing LaGuardia tower communication in the moments leading up to the collision, a ground controller can be heard instructing the truck, "Just stop there. ... Stop, stop, stop, Truck One, stop, stop, stop! Stop, Truck One! Stop!"

The two-man vehicle was headed to a United flight that had reported an issue with an odor, according to Garcia.

"Jazz 646, I see you collide with a vehicle, just hold position," continues the controller. "I know you can't move. Vehicles are responding to you now."

By that point, the cockpit was shorn off, with its occupants almost certainly dead.

An individual in the recording states, "That wasn't good to watch."

The controller who told the truck to stop responds, "Yeah, I know, I was here. I tried to reach out to 'em and stop 'em. We were dealing with an emergency earlier, and I messed up."

Garcia noted that where port authority rescue vehicles operating on the tarmac are concerned, "the procedure always is in deference to the control tower any time anyone is moving on any of our runways or taxiways," and "they have to get clearance from the tower to move on our runways and our taxiways."

The National Transportation Safety Board is investigating the collision.

LaGuardia, which warned travelers days earlier of "longer than usual wait times" at security checkpoints "due to staffing impacts from the federal funding lapse," announced that the airport will remain closed until at least 2 p.m. on Monday — the first day of U.S. Immigration and Customs Enforcement agents' expected nationwide deployment to help with security lines at airports.

The New York Police Department announced Monday morning that all streets and highway exits into the airport have been closed until further notice.

According to Federal Aviation Administration data, LaGuardia was the 19th busiest American airport in 2024.

Like Blaze News? Bypass the censors, sign up for our newsletters, and get stories like this direct to your inbox. Sign up here!

FACT CHECK: No, Video Doesn’t Show Cargo Plane On Aircraft Carrier

A post shared on X claims to show a Boeing C-17 Globemaster taking off from an aircraft carrier. The Boeing C-17 Globemaster Amazing Takeoff From Shortest Runway. 🔥🔥🔥🔥🔥🔥🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 pic.twitter.com/UtIoTVtPRR — Trump Girl (@TrumpGirlLove) February 19, 2025 Verdict: False The video is computer-generated imagery. U.S. aircraft carriers do not have ramps. Fact Check: Social media users […]

US Navy apparently shot down own plane over Red Sea



The U.S. Navy apparently shot down one of its own two-seat F/A-18F Super Hornets over the Red Sea on Sunday around 3 a.m. local time. Although one of the pilots was injured, U.S. Central Command indicated that both were safely rescued.

CENTCOM did not provide an indication of the American F/A-18's mission prior to being shot down; however, U.S. forces in the area have recently been conducting airstrikes against Iran-backed Houthi militants and their facilities in Yemen as well as taking out ISIS targets in Syria.

Over the weekend, U.S. Air Force and U.S. Navy assets reportedly shot down multiple Houthi drones and an anti-ship cruise missile and also conducted strikes against a missile storage facility and a command-and-control facility in Sana'a, Yemen. Days earlier, CENTCOM whacked ISIS leader Abu Yusif aka Mahmud via a precision airstrike in the Dayr az Zawr province.

A Navy official told U.S Naval Institute News that the downed F-18 was assigned to Carrier Air Wing One and embarked aboard the Nimitz-class aircraft carrier USS Harry S. Truman, which entered the CENTCOM area of responsibility on Dec. 14.

'Another indicator of how pathetic a state of readiness our military is in.'

USNI indicated that the crew are most likely with the Red Rippers of Strike Fighter Squadron 11 from Naval Air Station Oceana, Virginia.

The strike group, part of Operation Prosperity Guardian, is presently focused on razing Houthi military installations and protecting merchant traffic and American vessels in the southern Red Sea, Bab al-Mandeb, and Gulf of Aden from attack.

CENTCOM said in a statement that the Ticonderoga-class guided-missile cruiser USS Gettysburg, commanded by Alaska native Captain Justin Hodges, "mistakenly fired on and hit the F/A-18" fighter craft that was flying off the USS Harry S. Truman, confirming that "this incident was not the result of hostile fire."

The Associated Press suggested that earlier Houthi drone and missile attacks may have been responsible for the confusion that led to the alleged friendly fire.

Yahya Saree, a spokesman for the Houhi militants, claimed without evidence that Houthis shot down the F/A-18.

Retired Army Col. Douglas Macgregor noted, "Yes, we shot down our own plane. If this doesn't put a cap on the worst Presidency of modern history, I'm not sure what does."

"This is another indicator of how pathetic a state of readiness our military is in, especially our U.S. Navy," tweeted retired U.S. Army Lt. Gen. Michael Flynn.

According to a 2024 Government Accountability Office report, "47 of the 49 aircraft we reviewed did not meet DOD's mission capable goals." A previous GAO report noted that between 2011 and 2021, the Navy and Marine Corps F/A-18 jets under review almost always failed to meet their mission capable goal.

The Heritage Foundation concluded in its 2024 index of military strength that "as currently postured, the U.S. military is at significant risk of not being able to defend America's vital national interests."

Like Blaze News? Bypass the censors, sign up for our newsletters, and get stories like this direct to your inbox. Sign up here!

'Wow': Biden-Harris DOD bungles Veterans Day commemoration with mind-boggling error



Keen observers noticed something amiss about a Biden-Harris Department of Defense social media post Monday commemorating Veterans Day.

In a now-deleted post on Instagram and X, the F-35 Lightning II Joint Program Office — whose very existence centers on the F-35 fighter jet — shared an image of an aircraft with the caption, "Today, and every day, we thank all Veterans and those currently serving for their service and sacrifice."

The trouble with the F-35 JPO's post was not the wording but rather the image. Not only was the aircraft pictured not American, it belongs to an adversarial, communist nation that some living veterans commemorated on Monday fought against in Korea.

Military.com noted that instead of the F-35's single Pratt & Whitney F135 turbofan engine, the vehicle depicted in the post had twin engines. On closer examination, it appears as though the F-35 JPO actually posted an image of communist China's J-35 stealth fighter aircraft, the People's Liberation Army Air Force's F-35 knockoff.

'You can't make this stuff up.'

The backlash was immediate.

Sen. Eric Schmitt (R-Mo.) wrote, "WTAF?"

"Biden Administration: showcasing Chinese military equipment on Veterans Day," wrote Sen. Mike Lee (R-Utah).

One commentator on Instagram noted, "'Mom I want an F-35 from the JPO!' 'no son, we have F-35s at home!' *the F-36s at home*"

"Embarrassing," wrote another user. "Please take this down. We don't want a Chinese J-35 supported by our F-35 JPO office."

Conservative filmmaker Robby Starbuck tweeted, "You can't make this stuff up. Wow."

Former Salomon Brothers and Citigroup investment banker John LeFevre wrote, "China stole the IP for the F-35 and then mocked us by naming theirs the J-35. Today, the Biden administration celebrated Veteran's Day by posting a picture of the Chinese knockoff."

The F-35 JPO, which touts itself as the "DoD's focal point for defining next gen strike aircraft weapons systems," deleted the post, then shared images and video of real F-35 jets.

Blaze News has reached out to the F-35 JPO for comment.

While embarrassing, the F-35 JPO's blunder was not the first time the Biden-Harris DOD evidenced difficulty discerning friend from foe.

Stars and Stripes reported that the U.S. Pacific Fleet tweeted then deleted a Fourth of July message last year depicting a service member saluting silhouettes of a Russian Kashin-class destroyer and Russian Sukhoi-27 fighter jets.

The Naval Criminal Investigative Service similarly mistook an adversary's ship for its own, celebrating the U.S. Navy's 246th birthday in 2021 with an image of a Russian Kirov-class battle cruiser.

Like Blaze News? Bypass the censors, sign up for our newsletters, and get stories like this direct to your inbox. Sign up here!

Drones Are Swarming U.S. Military Bases, And Our Incompetent Bureaucracy Won’t Do Anything About It

When drones swarmed our military bases, the only thing bureaucrats 'shot down' were proposals about how to deal with the problem.

United Airlines Boeing aircraft found to be missing external panel



An external panel was found to be missing on an aircraft after it arrived in Medford, Oregon, according to United Airlines.

"This afternoon, United flight 433 landed safely at its scheduled destination at Rogue Valley International/Medford Airport. After the aircraft was parked at the gate, it was discovered to be missing an external panel. We'll conduct a thorough examination of the plane and perform all the needed repairs before it returns to service. We'll also conduct an investigation to better understand how this damage occurred," the airline noted in a statement, according to nbcbayarea.com.

The outlet reported that United noted that there had been 139 passengers and six crewmembers aboard the aircraft.

The flight had traveled to Medford, Oregon, from San Francisco, California, according to FlightAware.

The aircraft is a Boeing 737-824, according to airport director Amber Judd, Rogue Valley Times reported.

The outlet reported that based on the plane's N-number, the airplane had been delivered to Continental Airlines December 22, 1998. The aircraft has been operated by United since November 30, 2011, according to the outlet.

Earlier this year, "a left mid-cabin door plug blew out of Alaska Airlines Flight 1282 on January 5 while in flight," according to the FAA. That incident also involved a Boeing aircraft.

Like Blaze News? Bypass the censors, sign up for our newsletters, and get stories like this direct to your inbox. Sign up here!