FY2024 USAspending in Virginia District 05
Virginia District 05 shows $9.6 billion in FY2024 USAspending.gov obligations for place of performance in the 5th district. The exact sum is $9,558,096,821.70 across 13,930 awards. Those dollars are award commitments, not outlays. VA-05 is a numbered House seat, not an unspecified 90 code. SpendingVault indexes the rows on the Virginia District 05 hub.
Key figures
- Virginia District 05 shows $9.6 billion in FY2024 place-of-performance obligations.
- 13,930 awards are counted for VA-05 in that FY2024 extract.
- District 05 is a numbered House seat, not a 90/98 unspecified bucket.
- Geography is place of performance, not recipient headquarters.
- Cite $9.6 billion as obligations, not outlays.
The $9.6 billion FY2024 commitment total
The $9.6 billion figure is the FY2024 obligation aggregate on awards whose place of performance is Virginia District 05. Obligation means a recorded commitment. It is not Treasury cash already paid, and it is not Virginia’s state budget. The matching record count is 13,930.
First year and last year are both 2024. Federal fiscal years begin on October 1. Later USAspending.gov corrections can revise $9,558,096,821.70 and the 13,930-award count. Until then, cite both as the FY2024 VA-05 place-of-performance stock.
Thirteen thousand nine hundred thirty award actions
13,930 is the FY2024 record count for VA-05 place of performance. Modifications and assistance actions can each add a row. The packet does not publish unique recipients or an agency mix. Do not treat 13,930 as 13,930 Virginia companies.
Do not divide $9.6 billion by 13,930 awards. That quotient is not in the packet. Keep the dollar total and the row count as separate facts and use the Virginia District 05 hub to inspect lines. A mid-size file can mix large and small actions; the packet does not identify which.
Performance geography, not a 5th-district HQ map
Even for a numbered Virginia seat, the district field is still place of performance, not recipient headquarters. A contractor based in another Virginia district or another state can appear on VA-05 if the performance location is coded to the 5th. A 5th-district headquarters can post dollars to another district when performance is coded there.
Virginia’s unspecified 90/98 rows, if present, stay on their own pages. Recipient-location maps are a different cut from this $9.6 billion file. HQ lists of “5th district contractors” will not match 13,930 performance-coded awards.
VA-05 versus leftover codes 90 and 98
Virginia District 05 is a mapped House district. District 90 and district 98 are USAspending unspecified and non-voting bins. VA-05 is the numbered 5th, not a leftover. Unspecified Virginia performance, if any, would live on a 90 page rather than inside this table.
The Virginia state hub is the statewide obligation view. VA-05 is the 5th-district place-of-performance page. They are related but not interchangeable. This packet does not quote a statewide Virginia total and does not rank the 5th against other districts.
Obligations versus outlays
The $9.6 billion total is the obligation series. Outlays measure disbursements and can lag. SpendingVault does not recast VA-05 as cash paid. If another Virginia headline disagrees, check series, fiscal year, and whether geography is performance or HQ.
The precise FY2024 statement is that agencies obligated $9.6 billion on 13,930 awards with VA-05 place of performance. Multi-year vehicles can obligate here and invoice later. Federal FY2024 starts October 1.
How to quote Virginia’s 5th without mixing codes
A complete VA-05 citation names numbered District 05, FY2024, USAspending.gov, place of performance, obligations, $9.6 billion, and 13,930 awards. Calling the code unspecified would confuse it with district 90.
The Virginia District 05 hub is the table. The Virginia state page is the statewide roll-up. The all-districts index lists other Virginia seats in the same format. Outlay tables, headquarters maps, and calendar-year charts are other products. Do not drop $9,558,096,821.70 onto those grids unless they already use place of performance, federal FY2024, and obligations.
Virginia District 05 can be briefed as $9.6 billion in FY2024 obligations on 13,930 awards with numbered code VA-05. Treat 13,930 as an action stock, not unique vendors. Keep other Virginia numbered districts and any District 90 leftover on other rows. What this packet supplies is VA-05 place-of-performance commitments from USAspending.gov, not outlays, not a headquarters extract, and not a multi-year series. A headquarters in the 5th without a VA-05 tag does not enter this file. Work coded to VA-05 from a vendor based elsewhere does enter $9.6 billion.
Questions
- How much federal spending is in Virginia District 05?
- USAspending.gov shows $9.6 billion in FY2024 obligations with place of performance in Virginia District 05. The exact sum is $9,558,096,821.70. That is not an outlay total and not Virginia’s state budget. The extract counts 13,930 awards for VA-05 in FY2024. The packet year range is FY2024 only.
- Is Virginia District 05 an unspecified 90 bucket?
- No. District 05 is a numbered voting House seat. Codes 90 and 98 are USAspending unspecified or non-voting buckets. The $9.6 billion total uses the VA-05 place-of-performance code. 13,930 awards share that same numbered tag.
- Are Virginia 5th-district dollars based on contractor headquarters?
- No. The district is place of performance. Recipients based outside the 5th can still appear on VA-05 if the performance location is coded to the 5th. A 5th-district headquarters can also map dollars to another district when performance is coded there.
- Is $9.6 billion in VA-05 already paid out?
- No. $9.6 billion is an obligation sum from FY2024 award records. Outlays are a different series. SpendingVault does not convert the Virginia 5th-district obligation total into Treasury outlays. Cite the figure with the obligation label, the FY2024 window, and VA-05 place of performance.
Congressional district is USAspending place-of-performance, not the recipient HQ. District 90/98 are USAspending unspecified/non-voting buckets.