Codify — Article

House resolution commemorates 10th anniversary of TORQE 62 crash

A non‑binding House resolution recognizes the anniversary, offers condolences, and affirms gratitude for the crew and those who served with them—primarily symbolic, not regulatory.

The Brief

H. Res. 765 is a commemorative House resolution marking the tenth anniversary of the TORQE 62 C–130J crash at Jalalabad Airfield and formally recognizing the crew and civilians who died.

The text frames the event as a moment for remembrance and expresses the House’s condolences and gratitude without creating legal rights or new benefits.

For professionals tracking military affairs, veterans policy, or memorialization, the resolution matters because it records an official congressional expression of remembrance, names the units and operation associated with the flight, and signals institutional recognition that can shape how DoD units and veteran organizations plan observances and archival records. It does not appropriate funds or change eligibility for benefits.

At a Glance

What It Does

The resolution memorializes the tenth anniversary of the TORQE 62 crash, acknowledges the loss of service members and civilian contractors, and contains three 'Resolved' clauses that commemorate, extend condolences, and express gratitude. It is a non‑binding expression of the House and does not direct executive action or create statutory entitlements.

Who It Affects

Directly affected parties are the families and next of kin of the fallen, the Air Force units named in the text, and civilian contractor communities who served in theater. Indirectly affected are veteran service organizations, military historians, and DoD offices that maintain casualty records and plan commemorative events.

Why It Matters

Symbolic congressional recognition helps shape public memory, legitimizes unit‑level commemorations, and can catalyze administrative or ceremonial follow‑up by military units and veteran groups. Because it names units and the operation, it also becomes a discrete congressional entry in the historical record of U.S. military operations in Afghanistan.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

H. Res. 765 opens with a series of 'Whereas' clauses establishing the factual context: it identifies the aircraft (a C–130J Super Hercules, call‑sign TORQE 62), the location (departure from Jalalabad Airfield), and the date of the accident (October 2, 2015).

The preamble states that service members and civilian contractors died while supporting Operation Freedom’s Sentinel and frames their deaths as a reminder of the risks faced by uniformed personnel and civilians who serve alongside them.

The text then lists the crew by name and age, naming six United States Air Force members and five civilian contractors. It specifically mentions the 774th Expeditionary Airlift Squadron and the 455th Air Expeditionary Wing and notes ongoing unit practices—remembrance ceremonies, battlefield crosses, and commemorative roll calls—that honor the TORQE 62 legacy.The operative portion is three short 'Resolved' clauses: the House (1) commemorates the lives and service of the crew, (2) extends condolences to their families and loved ones, and (3) expresses gratitude for their courage and for all who served in Operation Freedom’s Sentinel.

The resolution contains no command to an executive agency, no funding provision, and no change to federal benefits or legal status for survivors; it is an expression of sentiment rather than a directive. The bill text shows it was submitted to the House and referred to the Committee on Armed Services, a standard procedural step for this type of measure.

The Five Things You Need to Know

1

The bill is purely commemorative and non‑binding: it contains no appropriation, regulatory change, or entitlement for survivors.

2

The resolution names 11 individuals who died in the crash—six Air Force members and five civilian contractors—and lists their names and ages in the preamble.

3

It identifies the aircraft call‑sign (TORQE 62), the platform (C–130J Super Hercules), the date (October 2, 2015), and the location (departure from Jalalabad Airfield).

4

The text explicitly names the 774th Expeditionary Airlift Squadron and the 455th Air Expeditionary Wing and references Operation Freedom’s Sentinel as the mission context.

5

The measure was introduced as H. Res. 765 and referred to the House Committee on Armed Services; as a House resolution, it expresses the chamber’s view rather than creating executive obligations.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Whereas clauses (Preamble)

Sets factual record for the crash and service context

This section compiles factual statements: aircraft type and call‑sign, date and location, mission context (Operation Freedom’s Sentinel), and the broader point that both uniformed personnel and civilian contractors were serving in support roles. Practically, the preamble is the resolution’s evidentiary backbone: it establishes the circumstances that the House is memorializing and supplies names and unit identifiers that make the commemoration specific rather than generic.

Listing of deceased (Preamble line items)

Identifies the individuals and personalizes the loss

The bill enumerates the six Airmen and five civilian contractors by name and age. Including individual names converts an abstract memorial into a record that family members, units, and archives can cite. That specificity also matters for unit histories and for organizations that track casualty lists or maintain registers of those killed in theater.

Resolved clause 1

Formal commemoration of lives and service

The first operative clause declares that the House commemorates the lives, courage, and service of the deceased. This is a formal expression intended to validate remembrance activities and provide an official congressional acknowledgement of sacrifice. It carries symbolic weight for ceremonial planning but imposes no operational duties on the Department of Defense or other federal agencies.

2 more sections
Resolved clause 2

Extension of condolences

The second clause extends condolences to families, loved ones, and friends. While purely symbolic, this language functions as public recognition of bereavement that families can reference; it does not, however, alter survivor benefits or create new administrative processes for benefits claims.

Resolved clause 3 and procedural note

Expression of gratitude and committee referral

The final clause expresses gratitude for the crew’s service and for those who served in the named operation, reinforcing the resolution’s commemorative purpose. The bill text also records the standard procedural step of referral to the Committee on Armed Services, which is how the House typically considers military‑related resolutions.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Veterans across all five countries.

Explore Veterans in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Families and next of kin of the deceased — they receive a recorded expression of congressional recognition that can be cited in memorials and archived records, which some families value as formal acknowledgement.
  • 774th Expeditionary Airlift Squadron and 455th Air Expeditionary Wing personnel — unit morale and institutional memory benefit from formal congressional recognition that spotlights unit history and sacrifice.
  • Civilian contractor community and employers — naming contractors alongside uniformed members publicly acknowledges contractor risk and service in theater, which can affect how private employers and industry associations memorialize lost colleagues.
  • Veteran service organizations and unit associations — the resolution provides an official congressional reference that VSO events, roll calls, and memorial projects can rely on for legitimacy and publicity.
  • Military historians, archivists, and DoD casualty‑record offices — the detailed preamble (names, units, date, and location) supplies a clear, citable congressional record entry for archival purposes.

Who Bears the Cost

  • House Committee on Armed Services and committee staff — they expend time reviewing and processing the resolution, albeit a routine and typically low‑burden task.
  • Families and survivors — while they benefit symbolically, public commemoration can reopen grief and require engagement (requests for records, participation in ceremonies) that carries emotional cost.
  • Department of Defense administrative offices — the resolution may prompt informal inquiries or requests for unit participation in commemorative events, creating minor unfunded administrative or ceremonial burdens.
  • Taxpayers (negligible) — any incidental costs arise only if units or DoD choose to fund additional ceremonies; the resolution itself authorizes nothing and contains no appropriation.

Key Issues

The Core Tension

The central dilemma is between symbolic recognition and substantive support: the resolution provides an official, specific remembrance that validates sacrifice and shapes public memory, but it stops short of creating tangible assistance or policy changes for survivors—leaving families and units with public affirmation but no new legal or financial remedies.

The most concrete operational feature of H. Res. 765 is its specificity: names, units, platform, and mission are spelled out.

That specificity makes the resolution a useful archival document but also raises questions about selectivity — Congress memorializes many incidents but not all; choosing which events to memorialize in this way shapes institutional memory without an explicit standard. Practically, the bill creates expectations of recognition without providing resources: units or families that see the resolution as validation may reasonably ask for further acknowledgment or support, but the text contains no mechanism to deliver that support.

Another tension concerns the parallel treatment of civilian contractors and uniformed personnel. The resolution names both groups together, which has symbolic inclusivity, but it does not address the different statutory regimes that govern benefits, death gratuities, and access to military‑provided survivor services.

Readers should note that congressional recognition does not equate to changes in eligibility or benefits, and the resolution does not direct DoD to alter administrative practices. Finally, while the measure is routine in form, its referral to Armed Services places it in a committee context where memorial language can sometimes be amended or used as a vehicle for broader policy statements; the current text, however, stays narrowly ceremonial.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.