From February 24th, 2026 through March 2nd, 2026, the calendar carries echoes of campaigns, crises, experiments, and hard lessons that have shaped United States arms and strategy. In this edition of “This Week in U.S. Military History” from Dispatch: U.S. Military History Magazine, we move from muddy frontier forts to steel warships, from early Pacific battles to nuclear test islands, from the skies over North Vietnam to the deserts of Kuwait and the high valleys of Afghanistan. Across these stories, American soldiers, sailors, airmen, and Marines confront uncertainty, adapt under pressure, and pay close attention to how each decision may ripple years into the future. Some episodes are celebrated victories, others are sobering setbacks or tragic accidents, but all of them pushed the United States military to change, refine, and reconsider the way it fights. Together they show how much history can be packed into one late-winter week on the calendar.
Capture of Fort Sackville at Vincennes
In the dead of winter during the Revolutionary War, Virginia officer George Rogers Clark led a small force of frontiersmen and French militia through flooded Illinois country to strike the British post at Vincennes, in what is now Indiana. After a grueling march through icy water and mud, his men surrounded Fort Sackville and convinced the British commander, Lieutenant Governor Henry Hamilton, that he faced a much larger American force. Through a mix of aggressive skirmishing, well-placed marksmen, and psychological pressure, Clark secured the fort’s surrender on February 25th, 1779. The victory helped break British control over the old Northwest, bolstered American claims to territory beyond the Appalachians, and added weight to the young republic’s diplomatic position when peace terms were eventually discussed. For the United States Army that would follow, Vincennes stands as an early example of how small, determined forces on the frontier could achieve outsized strategic gains.
Open the Wiki entryUSS Princeton gun disaster
On a winter day on the Potomac River in 1844, the brand-new steam warship USS Princeton hosted Washington dignitaries for a demonstration cruise. The pride of the ship was a massive naval gun nicknamed “Peacemaker,” intended to showcase the Navy’s technical skill and the promise of long-range, heavy artillery at sea. When the gun was fired during the outing, it catastrophically exploded, killing several prominent officials, including the Secretary of State and the Secretary of the Navy, and injuring others while President John Tyler narrowly escaped harm. The disaster shocked the capital and underscored the dangers of cutting-edge weapons when design, testing, and safety procedures lag behind ambitious ideas. In the years that followed, the Navy placed greater emphasis on careful gunnery trials, metallurgical study, and more rigorous procedures before new weapons reached the fleet, a sobering reminder that technological progress in war carries real human risk.
Open the Wiki entryAnti-aircraft barrage over Los Angeles
In the dark hours of February 25th, 1942, only weeks after Pearl Harbor and just days after a Japanese submarine shelled an oil facility near Santa Barbara, air raid sirens wailed across the Los Angeles area. Searchlights probed the sky, and anti-aircraft batteries opened fire on what many believed were incoming Japanese bombers. For hours, crews unleashed thousands of rounds, filling the night with noise, smoke, and confusion, yet no confirmed enemy aircraft were found. Property damage and several civilian deaths came not from bombs but from falling shell fragments and accident. The event, later nicknamed the “Battle of Los Angeles,” exposed how fear, incomplete radar information, and poor communication could turn the home front into a battlefield of nerves. It pushed planners to refine air warning systems, radar interpretation, and civilian defense procedures along the West Coast as a nervous nation braced for possible attacks.
Open the Wiki entryBattle of the Java Sea begins
Just two days after the Los Angeles scare, a very real crisis unfolded far across the Pacific. On February 27th, 1942, a mixed Allied naval force under Dutch command, including the United States heavy cruiser Houston, engaged a Japanese invasion convoy in the waters of the Java Sea. Outgunned, short on air cover, and struggling with differences in doctrine and communications across Dutch, British, Australian, and American ships, the Allied force was gradually overwhelmed by Japanese torpedoes and gunnery. Several cruisers and destroyers were sunk or damaged, and Houston and her companions were forced into further desperate actions as Java’s fall loomed. The defeat cleared the way for Japanese landings on Java and exposed how unprepared the Allied navies were for Japan’s combination of long-range torpedoes, air power, and aggressive tactics. For the United States Navy, the battle’s losses added urgency to the drive to rebuild and learn quickly in the early months of the Pacific War.
Open the Wiki entryBattle of the Bismarck Sea begins
One year later to the week, the balance of power in the air over the Southwest Pacific had begun to shift. On March 2nd, 1943, United States Army Air Forces and Royal Australian Air Force units spotted a Japanese convoy attempting to move troops and supplies to the key base at Lae in New Guinea. Over the next two days, Allied medium bombers and attack aircraft used new low-level “skip bombing” techniques, roaring in just above the waves and tossing bombs that bounced into ships’ hulls. The result was a disaster for the convoy, with most transports and several escorting warships sunk, thousands of soldiers lost, and Japanese reinforcement plans badly disrupted. The battle demonstrated how air power, when combined with good intelligence and innovative tactics, could effectively replace traditional surface fleet actions against shipping. For the United States, it was a clear sign that control of the air could strangle enemy logistics long before land fighting reached the front lines.
Open the Wiki entryCastle Bravo nuclear test
In the early Cold War, the United States sought more powerful nuclear weapons to stay ahead in the arms race. On March 1st, 1954, at Bikini Atoll in the Pacific, the United States conducted the Castle Bravo test, the first dry-fuel thermonuclear device in its series. The blast was far more powerful than designers anticipated, yielding many megatons of explosive force and producing a massive fireball and mushroom cloud. Radioactive fallout spread much farther than expected, contaminating downwind islands, exposing some United States personnel, and sickening the crew of a Japanese fishing boat that strayed into the affected area. The incident triggered public concern and diplomatic strain, highlighting that nuclear tests were not just distant scientific experiments but events with real human and environmental consequences. Inside the United States defense establishment, Castle Bravo forced more careful study of fallout, blast effects, and the political implications of testing weapons whose destructive reach was difficult to fully predict.
Open the Wiki entryOperation Rolling Thunder begins in Vietnam
As the Vietnam conflict deepened, American leaders turned to the air campaign as a tool of pressure and signal. On March 2nd, 1965, the United States began Operation Rolling Thunder, a sustained bombing effort against North Vietnam that was intended to deter aggression, reduce support to Viet Cong forces in the South, and reassure allies of American resolve. Fighters and bombers from United States bases and carriers struck lines of communication, supply routes, and selected targets, but the campaign was tightly controlled, with many restrictions on where and how pilots could attack. Over time, North Vietnamese defenses adapted, building dense anti-aircraft networks and improving tactics, while political limits in Washington kept the bombing from fully matching early expectations. For the United States Air Force and Navy, Rolling Thunder became a long, costly test of air power’s limits when political objectives and military means were misaligned. The lessons about targeting, escalation, and the intersection of strategy and policy would be studied for decades afterward.
Open the Wiki entryGround offensive in Operation Desert Storm begins
After more than a month of intensive air strikes during Operation Desert Storm, coalition leaders launched the long-awaited ground campaign on February 24th, 1991, to liberate Kuwait and break the Iraqi army. United States Marine units attacked directly into Kuwait alongside Arab partners, driving against entrenched Iraqi formations and minefields that had been weakened by bombardment. To the west, United States Army heavy corps executed a wide “left hook,” sweeping into Iraq to cut off retreat and threaten key supply lines and Republican Guard units. The combined effect was rapid: Iraqi forces began to collapse, surrender in large numbers, or attempt chaotic withdrawals under air attack. The ground war would famously last only about one hundred hours before a cease-fire, but the opening day set the tone, demonstrating how air and ground operations could be tightly integrated for a quick decision. For the United States military, Desert Storm’s ground phase reinforced faith in training, coalition warfare, and new technologies, even as later debates questioned what was left unresolved.
Open the Wiki entryOperation Anaconda begins in Afghanistan
Just over a decade after Desert Storm, United States forces found themselves fighting a very different kind of war in Afghanistan. On March 2nd, 2002, Operation Anaconda began in the Shah-i-Kot Valley and surrounding high ground, as United States and allied troops attempted to encircle and destroy concentrations of al-Qaeda and Taliban fighters. The plan called for Afghan and coalition units to block escape routes while airlifted infantry swept through rugged terrain at high altitude. In practice, resistance was stronger than expected, communications were sometimes strained, and several units found themselves in intense close combat and reliant on rapid air support, including dramatic rescues and firefights on snow-covered ridgelines. Though the operation ultimately disrupted enemy networks and killed or captured many fighters, it also exposed shortcomings in coordination, intelligence, and preparation for high-altitude warfare. For the United States military, Anaconda became an early case study in the challenges of joint operations, special operations, and conventional forces working together in complex, unforgiving terrain against a determined irregular foe.
Open the Wiki entryAcross the Week
Across these days from February 24th, 2026 through March 2nd, 2026, the calendar draws together frontier campaigns, industrial-age technology, world war at sea, nuclear brinkmanship, air campaigns over Southeast Asia, armored blitzes in the desert, and mountain firefights in Central Asia. The common threads are adaptation and consequence: each event forced American leaders and service members to revise assumptions about geography, technology, and the enemy’s will. A winter slog through flooded prairies, a shattered naval gun, a panicked home-front sky, and distant battles over islands and valleys all contributed in their own way to the doctrines and habits that shape today’s forces. As readers of Dispatch: U.S. Military History Magazine reflect on this week in history, the stories invite us to see the present United States military not as a fixed object, but as the product of generations of trial, error, courage, and hard-earned insight.