What are the opening hours?

Monday 9am - 5pm Tuesday 9am - 5pm Wednesday 9am - 5pm Thursday 9am - 5pm Friday 9am - 5pm

https://www.rawlslawgroup.com/, https://www.rawlslawgroup.com/medical-malpractice, https://www.rawlslawgroup.com/nursing

Vet4Vet Lawyers, 211 Rocketts Way Ste 100, Richmond, VA (2026)

08/28/2026

Today in United States Military History-August 28

A Flag Over a Sandbar: How Midway Atoll Became American Territory

Long before it became the site of one of the most consequential naval battles in American history, Midway Atoll was little more than a remote, uninhabited speck in the vast North Pacific. On August 28, 1867, that changed, when an American naval officer raised the U.S. flag over the atoll, marking the first territorial acquisition by the United States beyond its own shores.

A Remote and Unremarkable Outpost:

Midway Atoll, then known as the Brooks Islands, consists of a small ring of coral and two tiny islets sitting roughly halfway between North America and Asia — a geographic fact that would later give the atoll its enduring name. In the mid-19th century, the islands held little obvious strategic or economic value. They were uninhabited, difficult to reach, and surrounded by treacherous reefs.

Yet as American commercial and naval interests expanded across the Pacific in the years following the Civil War, even remote and seemingly unremarkable islands took on new significance as potential coaling stations, communication points, and strategic outposts.

Raising the Flag:

On August 28, 1867, Captain William Reynolds of the screw sloop Lackawanna formally claimed the islands for the United States, raising the American flag over them. Reynolds understood the historic weight of the moment. He would later write of the experience with evident pride, reflecting on his role in helping expand American territory beyond the continental United States for the first time in the nation's history.

The formal annexation of the islands followed several months later, on December 28, 1867, cementing what had begun as a modest, largely symbolic act of flag-raising into an official expansion of American territory.

A Quiet Beginning to an Outsized Legacy:

For decades after its annexation, Midway remained a largely quiet, remote outpost, valued chiefly for its potential as a coaling station and, later, as a stop along early transpacific communication and aviation routes. Few at the time could have imagined the role the atoll would eventually play in American military history.

Destiny at Midway:

That would change dramatically in June 1942, when Midway Atoll became the site of one of the most decisive naval battles of World War II. The Battle of Midway, fought less than a year after the attack on Pearl Harbor, saw American forces deal a crushing and unexpected defeat to the Imperial Japanese Navy, sinking four Japanese aircraft carriers and fundamentally shifting the balance of naval power in the Pacific. Historians widely regard the battle as a turning point of the entire Pacific War.

From Obscurity to Historic Significance:

The story of Midway Atoll's acquisition in 1867 stands as a reminder of how seemingly minor territorial claims can take on outsized historical importance decades later. What began as a modest flag-raising ceremony on a remote Pacific outpost would, three-quarters of a century later, become the setting for one of the most consequential naval battles in American history — a legacy that continues to define the atoll's place in the nation's military memory today.

08/27/2026

Today in United States Military History-August 27

Watching the Skies: The Beginning of Operation Southern Watch

In the aftermath of the Gulf War, the United States and its coalition partners faced an ongoing challenge: how to protect vulnerable civilian populations in Iraq from further attacks by Saddam Hussein's regime, even after the formal fighting had ended. The answer came in the form of Operation Southern Watch, a sustained, years-long air campaign designed to enforce a no-fly zone over southern Iraq.

The Aftermath of War:

The 1991 Gulf War had driven Iraqi forces out of Kuwait, but it left Saddam Hussein's regime in power in Baghdad. In the war's aftermath, Hussein's government launched brutal crackdowns against Shiite Muslim populations in southern Iraq, who had risen up against the regime in the war's chaotic final days. Iraqi military aircraft, including helicopters, were used to attack these populations, drawing international condemnation and raising fears of further large-scale violence against Iraqi civilians.

Establishing a No-Fly Zone:

In response, the United States, alongside coalition partners including the United Kingdom and France, established a no-fly zone over southern Iraq, prohibiting Iraqi aircraft from operating below the 32nd parallel. The goal was to prevent the Iraqi government from using its air power to attack civilian populations in the region, offering a degree of protection without requiring a full-scale ground invasion or renewed occupation.

Enforcing that no-fly zone became the mission of Operation Southern Watch, which began flying missions on August 27, 1992.

Carrier Power Takes the Lead:

The first aircraft to take up station as part of Operation Southern Watch flew from the aircraft carrier Independence, underscoring the central role naval aviation played in enforcing the no-fly zone from the earliest days of the operation. Carrier-based aircraft, along with land-based coalition planes, would go on to patrol the skies over southern Iraq continuously for more than a decade, monitoring Iraqi military activity and responding to violations of the no-fly zone as they occurred.

A Long-Running Commitment:

Operation Southern Watch would continue for more than ten years, becoming one of the longest sustained air operations in modern American military history. Over the course of the mission, coalition aircraft regularly encountered and responded to Iraqi air defense systems that tracked or targeted patrolling aircraft, leading to periodic airstrikes against Iraqi military installations throughout the 1990s.

Setting the Stage for Future Conflict:

Operation Southern Watch remained in effect until the 2003 invasion of Iraq, at which point the no-fly zone was rendered moot by the broader military campaign that toppled Saddam Hussein's government entirely. In hindsight, the operation is often viewed as an important bridge between the first Gulf War and the second, reflecting a period of sustained but limited American military engagement in Iraq during the 1990s.

The beginning of Operation Southern Watch in 1992 illustrates a defining feature of the post-Cold War era: the use of sustained, precision air power to enforce international mandates and protect vulnerable populations, without committing to a full-scale ground war.

08/26/2026

What Happens When You Contact Rawls Law Group for Your VA Medical Malpractice Claim?

Navigating your VA medical malpractice claim can be overwhelming, and trying to determine your options after negligence occurs can feel confusing. Unlike standard civil medical malpractice claims, actions against federal facilities are governed by strict federal laws—specifically, the Federal Tort Claims Act (FTCA). Finding lawyers that handle VA medical malpractice claims can be difficult. There are not many law firms that handle VA medical malpractice claims, making the process feel like you’re looking for a needle in a haystack. Lucky for you, Rawls Law Group can help you with your VA medical malpractice claim!

Here is a step-by-step breakdown of what initially happens after you contact Rawls Law Group for assistance with your VA medical malpractice claim.

Initial Intake and Confidential Consultation:
When you first submit your case details online or call, your case information is shared with our in-house intake team. If our team requires additional information, we will contact you to discuss your medical care timeline, injuries, and the facilities involved.

At this stage, it is important to list the medical facilities that were involved in your medical care since your stated injury. Additionally, if you have already submitted an SF95 claim, it is important that you have a copy of your claim ready for review.
Typically, the intake process can take between 3 and 5 business days. Rather than rushing the process, at Rawls Law Group we like to be thorough when reviewing proposed claims. When veterans and their families contact us, they are dealing with life-changing events; we like to ensure each case is properly reviewed before a decision is made.

In the event we cannot assist you with your claim, we will contact you via email.

Medical Record Request and Evaluation:
In the event we want to investigate your medical malpractice claim further, we will contact you via email and mail asking you to provide relevant medical records. We will outline which medical records we need and what timeframe we need them to cover. Please ensure that when you request/obtain medical records from medical facilities, you request medical records covering the timeframe we requested. *If the facility permits, it will be cheaper and easier to obtain digital/electronic copies of your medical records. Once you receive the medical records from all requested facilities, you may submit the medical records to Rawls Law Group either electronically or via mail. Once all originally outlined medical records are submitted, we will put your case in queue for review. Typically, the review process takes between 2 and 4 weeks.

After a review is completed and all attorneys at the firm have commented on the matter, we will contact you, informing you whether or not we have decided to take the case. If we decide not to take your case, we will return all medical records you had submitted for the review process.

When you reach out to an experienced firm like Rawls Law Group—a veteran-founded firm specializing in nationwide VA and military healthcare claims—you gain knowledgeable guidance, strategic advocacy, and a clearer path through the complex VA medical malpractice claim process. If you or a loved one has been injured by a VA healthcare provider, contact our office today for a free consultation (https://www.rawlslawgroup.com/contact-us/).

08/26/2026

Today in United States Military History-August 26

A Ship, A Rebellion, and a Fight for Freedom: The Capture of the Amistad

Few maritime incidents in American history carry the moral and legal weight of the Amistad affair. What began as a slave-trading voyage across the Atlantic ended, after a dramatic rebellion at sea, with a U.S. Revenue Cutter Service vessel discovering a ship whose fate would become entangled in one of the most consequential legal battles over slavery in American history.

A Voyage That Went Terribly Wrong:

The Amistad was a Spanish schooner engaged in transporting a group of enslaved Africans, who had been illegally captured and sold into bo***ge in violation of international treaties banning the transatlantic slave trade. While en route along the coast of Cuba, the captives aboard the Amistad rose up in rebellion, seizing control of the ship and killing several crew members in the process.

Rather than sailing back to Africa as the rebels intended, the ship's surviving Spanish navigators secretly steered the vessel northward, hoping to reach a port where Spanish authorities could regain control. For nearly two months, the Amistad drifted and sailed erratically around the waters of the North Atlantic, its unusual and unpredictable course eventually drawing the attention of American authorities.

Discovery Off Long Island:

On August 26, 1839, the revenue cutter Washington, part of what would later become the U.S. Coast Guard, discovered the Amistad anchored near Montauk Point, New York. The ship's crew took the vessel into custody, bringing to an end its months-long, unintended voyage along the American coastline.

A Legal Battle That Captivated the Nation:

What followed was far more consequential than the ship's capture itself. The fate of the Africans aboard the Amistad became the subject of an intense legal battle that worked its way through the American court system, ultimately reaching the U.S. Supreme Court. At issue was a fundamental question: were the men and women aboard the Amistad legally enslaved property, subject to return to their Spanish claimants, or had they been illegally captured and therefore entitled to their freedom?

The case drew national attention and became a rallying point for the American abolitionist movement, which saw in it a powerful opportunity to argue against the legitimacy and morality of the slave trade before the nation's highest court.

A Landmark Ruling:

In 1841, the Supreme Court ruled in favor of the Africans, finding that they had been illegally enslaved and were therefore free individuals rather than property subject to return. The ruling represented a significant, if narrow, legal victory for the abolitionist cause, affirming that individuals who had been unlawfully captured and enslaved could not be treated as legitimate property under American law.

A Small Cutter, A Lasting Legacy:

While the U.S. Revenue Cutter Service's role in the Amistad affair was limited to the ship's initial discovery and seizure, that action set in motion one of the most significant legal cases in the history of the American antislavery movement. The Amistad case remains a powerful symbol of the fight for freedom and justice, a reminder of how a single maritime encounter off the coast of New York helped shape the broader national reckoning with slavery in the decades before the Civil War.

08/25/2026

Today in United States Military History-August 25

Into a Powder Keg: Marines Land in Beirut

In the summer of 1982, Lebanon's capital was in chaos, torn apart by years of civil war and now caught in the crossfire of an Israeli military campaign against Palestinian forces entrenched within the city. Into this volatile situation stepped a contingent of U.S. Marines, tasked with a delicate and dangerous peacekeeping mission that would, over the following year, prove far more perilous than anyone initially anticipated.

A City in Crisis:

By 1982, Lebanon had been engulfed in civil war for years, its government weakened and its capital divided among rival militias and factions. The situation grew even more volatile when Israeli forces launched a major military campaign into Lebanon, encircling Beirut in an effort to root out Palestine Liberation Organization fighters who had used the city as a base of operations. The resulting siege devastated the city and created an urgent humanitarian crisis, with thousands of Palestinian fighters and civilians trapped amid the fighting.

A Multinational Response:

To help defuse the crisis and facilitate a peaceful resolution, the United States joined France and Italy in assembling a Multinational Force intended to oversee the evacuation of Palestinian fighters from Beirut and help stabilize the situation on the ground.

On August 25, 1982, U.S. Sixth Fleet amphibious ships landed 800 Marines from the 32nd Marine Amphibious Unit in Beirut. Their mission was narrowly defined and time-limited: serve as part of the peacekeeping force for a period of roughly two weeks, providing security and support as thousands of Palestinian fighters and their families were evacuated from the city.

Overseeing a Massive Evacuation:

During their time ashore, the Marines played a direct role in one of the more remarkable humanitarian operations of the era, helping facilitate the evacuation of approximately 12,000 Palestinians from Lebanon. These evacuees departed aboard merchant vessels that were escorted to safety by Sixth Fleet warships, allowing the withdrawal to proceed despite the extraordinarily tense and dangerous conditions surrounding the besieged city.

By the second week of September, having completed their assigned role in the evacuation, the Marines withdrew from Beirut, their initial mission accomplished without major incident.

A Deceptively Brief Calm:

The August 1982 deployment would prove to be only the opening chapter of a much longer and, ultimately, far more tragic American involvement in Lebanon. Within weeks of the Marines' withdrawal, renewed violence and instability in Beirut prompted the United States to send Marines back into the city as part of a reconstituted multinational peacekeeping force — a deployment that would tragically culminate, in October 1983, in the bombing of the Marine barracks in Beirut, one of the deadliest single-day losses in Marine Corps history.

A Complicated Legacy:

The initial August 1982 landing is often overshadowed by the tragedy that followed a year later, but it stands on its own as a notable example of American military forces being used for a focused humanitarian and peacekeeping purpose amid one of the Middle East's most complex and dangerous conflicts. It reflects both the potential and the peril of using military forces for peacekeeping missions in deeply unstable environments — a lesson that would be reinforced, at great cost, in the months that followed.

08/24/2026

Today in United States Military History-August 24

Fire and Sacrifice: The Burning of the Washington Navy Yard

In one of the most humbling episodes of American military history, British forces marched into the young nation's capital and set it ablaze. But before the British ever reached the Washington Navy Yard, American forces had already made the painful decision to destroy it themselves, rather than let its ships and resources fall into enemy hands.

A Capital Under Threat:

By August 1814, the War of 1812 had turned dangerously against the United States. A British invasion force had landed in the Chesapeake Bay region and was advancing rapidly toward Washington, D.C., with little standing in its way. American defenses proved unable to stop the British advance, and it quickly became clear that the capital itself was about to fall into enemy hands.

Amid the chaos, American forces fought a desperate defense at the Battle of Bladensburg in nearby Maryland. Naval personnel who had previously served with the Chesapeake Bay Flotilla, under the command of Captain Joshua Barney, joined the fight against the advancing British regulars, providing some of the most determined resistance the British encountered that day. Despite their efforts, the battle ended in defeat, and the road to Washington lay open.

A Difficult Decision:

With British troops closing in and the fall of the city all but certain, American commanders faced an agonizing choice regarding the Washington Navy Yard, one of the young nation's most important naval facilities. Rather than allow its ships, supplies, and infrastructure to be captured intact and potentially used against the United States, the Secretary of the Navy ordered the yard destroyed.

Captain Thomas Tingey, commanding the yard, carried out this order on August 24, setting fire to the facility himself. The blaze consumed several frigates under construction or awaiting completion, including the Boston, General Greene, and New York, along with two additional vessels, Argus and Columbia, that were still being built.

The British Arrive:

The following day, British troops entered Washington and continued the destruction, setting fire to numerous government buildings, including the White House and the Capitol. They also burned what remained of the Navy Department's facilities. It was, by any measure, one of the darkest moments in the capital's history — a foreign army occupying and burning the seat of American government.

Saving What Mattered Most:

Amid the devastation, one crucial success stood out. Official Navy papers, books, and records had been moved to safety before the British arrival, preserving the institutional memory and administrative continuity of the Navy despite the physical destruction of its facilities. This foresight ensured that, even as buildings and ships were lost, the Navy's essential records and knowledge survived intact.

Rebuilding From the Ashes:

The burning of the Washington Navy Yard, though a painful and symbolically devastating moment, did not mark the end of American naval power. The yard was rebuilt in the years that followed, and the broader war ultimately ended without significant territorial loss for the United States. The events of August 1814 remain a powerful reminder of the vulnerability the young nation faced in its early decades — and of the resilience required to rebuild in the aftermath of such a stinging blow.

08/21/2026

Today in United States Military History-August 21

Breaking the Barrier: The F8U Crusader's Record-Setting Flight

In the mid-1950s, the race to push aircraft performance to new extremes was one of the defining contests of the early Cold War, as military aviation rapidly advanced from propeller-driven planes to sleek, powerful jets capable of astonishing speeds. On August 21, 1956, that race reached a milestone when a Navy fighter became the first operationally equipped aircraft to fly faster than 1,000 miles per hour.

A New Generation of Naval Fighters:

The F8U Crusader, developed for the U.S. Navy, represented a major leap forward in carrier-based fighter design. Sleek, powerful, and built for speed, the aircraft was intended to give Navy pilots a fighter capable of competing with — and outperforming — the fastest aircraft being developed by rival nations during an era of rapidly escalating aviation technology.

Unlike many earlier speed records, which were often set by specially modified, stripped-down research aircraft, the Crusader's achievement carried particular significance because it was accomplished in an aircraft outfitted for genuine operational, combat-ready service.

The Record-Setting Flight:

At the Naval Ordnance Test Station in China Lake, California — a facility long associated with cutting-edge aviation and weapons testing — Commander Robert W. Windsor took the Crusader through a carefully measured 15-kilometer course. When the results were tallied, Windsor had set a new national speed record of 1,015.428 miles per hour, becoming the first pilot to exceed 1,000 miles per hour in an aircraft that was fully equipped for operational military use, rather than a purpose-built speed demonstrator stripped of standard equipment.

Why It Mattered:

Breaking the 1,000-mile-per-hour barrier in an operational aircraft carried real strategic weight. It demonstrated that the Navy's newest fighter wasn't simply a technological curiosity or a one-off speed machine, but a genuinely combat-capable aircraft that could be deployed on carriers and flown by operational squadrons while still delivering world-class performance. In the tense atmosphere of the Cold War, such achievements served as visible proof of American aerospace and military capability.

A Storied Career for the Crusader:

The F8U Crusader — later redesignated the F-8 under a unified military aircraft naming system — went on to have a long and distinguished career with the Navy and Marine Corps, seeing extensive combat service during the Vietnam War. Pilots often praised the aircraft for its speed and maneuverability, and it earned a reputation as one of the last true "gunfighter" jets of its era, at a time when many fighters were shifting primarily toward missile-based combat.

A Milestone in Naval Aviation:

The Crusader's record-setting flight in 1956 stands as a landmark moment in the history of naval aviation, marking a new frontier in fighter aircraft performance and underscoring the rapid pace of technological advancement that characterized military aviation throughout the 1950s. It remains a notable point of pride in the long history of American carrier-based fighter development.

08/20/2026

Today in United States Military History-August 20

Answering Terror: The 1998 Retaliatory Cruise Missile Strikes

Twelve days after simultaneous truck bombings devastated two U.S. embassies in East Africa, the United States struck back — launching a coordinated wave of cruise missiles at targets thousands of miles apart, in one of the earliest major American military responses to al-Qaeda terrorism.

Twin Attacks, Hundreds of Lives Lost:

On August 7, 1998, terrorists linked to al-Qaeda detonated massive truck bombs outside the U.S. embassies in Nairobi, Kenya, and Dar es Salaam, Tanzania, within minutes of each other. The coordinated attacks killed hundreds of people, the overwhelming majority of them Kenyan and Tanzanian civilians, and wounded thousands more. The bombings marked one of the deadliest terrorist attacks against American interests to that point, and they placed the growing threat of al-Qaeda squarely in the spotlight of U.S. national security concerns.

A Swift Military Response:

Within less than two weeks, American intelligence had identified targets believed to be connected to the attacks and to the broader al-Qaeda terrorist network led by Osama bin Laden. On August 20, U.S. Navy surface ships and submarines launched a total of 75 Tomahawk cruise missiles at two very different targets on two different continents.

One set of missiles struck a suspected chemical weapons production facility in Sudan, which American officials believed was linked to bin Laden's network. The other wave targeted a series of terrorist training camps in Afghanistan, where al-Qaeda operatives were believed to be training for future attacks.

Bin Laden in the Crosshairs:

The strikes were explicitly aimed, at least in part, at bin Laden himself, reflecting growing American recognition that he represented a significant and direct threat to U.S. interests. Though the strikes caused damage to the targeted facilities, bin Laden was not present at the camps struck in Afghanistan, and he survived the attack to continue leading al-Qaeda for years afterward.

Controversy and Consequence:

The strikes, launched under President Bill Clinton, drew mixed reactions both domestically and internationally. Questions were raised about the intelligence used to justify the Sudan strike in particular, with some analysts and Sudanese officials disputing that the targeted facility was actually involved in chemical weapons production. The strikes also became entangled in domestic political controversy, given the timing amid ongoing scrutiny of the Clinton administration.

A Preview of a Longer Struggle:

In hindsight, the August 1998 strikes are often viewed as an early, if ultimately insufficient, American response to a terrorist threat that would grow dramatically over the following years. Al-Qaeda continued to plan and carry out attacks against American targets in the years that followed, culminating in the September 11, 2001, attacks that would draw the United States into a decades-long global war on terror.

The 1998 strikes stand as an important, if often overlooked, chapter in that longer story — a moment when the United States first attempted to directly confront, through military force, a terrorist network that would soon become the defining security challenge of a generation.

08/19/2026

Today in United States Military History-August 19

A Line in the Water: The Gulf of Sidra Incident

In the summer of 1981, a routine U.S. Navy training exercise in international waters turned into a brief but consequential clash with Libyan forces — a confrontation that tested American resolve against one of the era's most defiant and unpredictable adversaries, Libyan leader Moammar Qaddafi.

Qaddafi's "Line of Death":

Libya, under Qaddafi's leadership, had long claimed sovereignty over the entire Gulf of Sidra, an assertion far beyond what international law recognized as Libyan territorial waters. Qaddafi went so far as to declare a so-called "line of death" across the gulf, warning that any foreign military forces crossing it would be met with force.

The United States, along with much of the international community, rejected this claim, viewing the gulf as international waters open to lawful navigation and military exercises. To underscore that position, the U.S. Navy conducted routine training operations in the area, including flight operations from the aircraft carrier USS Nimitz.

Fighters in the Sky:

On August 19, as American F-14 Tomcat fighters from Fighter Squadron 41 operated in the contested airspace, two Libyan Su-22 fighter jets approached and engaged them. In the brief encounter that followed, the Libyan aircraft fired on the American fighters — an aggressive move that left the U.S. pilots little choice but to respond in self-defense.

The American F-14s made quick work of the engagement, shooting down both Libyan Su-22s in a matter of moments. Both American pilots returned safely to the carrier, having demonstrated the clear technological and tactical superiority of U.S. naval aviation in the encounter.

A Message Sent:

The incident carried significance well beyond the brief dogfight itself. It served as a clear signal that the United States would not be deterred from operating in international waters and airspace, regardless of unilateral claims made by regional powers. For the Reagan administration, still relatively new to office, the successful engagement reinforced a broader posture of firmness toward Qaddafi's Libya, which the United States viewed as a significant sponsor of international terrorism throughout the 1980s.

A Preview of Future Tensions:

The Gulf of Sidra incident would not be the last clash between American and Libyan forces during this turbulent period. Tensions between the two nations continued to simmer throughout the decade, eventually culminating in further naval confrontations in the Gulf of Sidra and, in 1986, American airstrikes against targets in Libya following terrorist attacks linked to Qaddafi's government.

A Small Battle with Lasting Symbolism:

Though brief, the 1981 Gulf of Sidra incident remains a notable episode in the history of American naval aviation and Cold War-era foreign policy. It stands as an early example of the kind of high-stakes, split-second encounters that would come to define much of the tense standoff between the United States and rogue regimes during the final decades of the twentieth century.

Vet4Vet Lawyers

08/28/2026

08/27/2026

08/26/2026

08/26/2026

08/25/2026

08/24/2026

08/21/2026

08/20/2026

08/19/2026

Address

Opening Hours

Telephone

Website

Alerts

Contact The Practice

Shortcuts

Share

Category

Listing takedown request

Monday	9am - 5pm
Tuesday	9am - 5pm
Wednesday	9am - 5pm
Thursday	9am - 5pm
Friday	9am - 5pm