Construction Machinery & Heavy Transportation Equipment · US Census Bureau
US Census International Trade Data - Schedule B 8429 Construction Machinery Exports
Datadory delivers US Census International Trade data for Schedule B 8429 construction machinery exports: the official monthly record of American earthmoving-equipment shipments, queryable to the 10-digit Schedule B code across heading 8429's bulldozers, graders and levelers, scrapers, excavators and shovel loaders, tamping machines and road rollers, crossed with roughly 240 partner countries and running from January 2010 to the latest press-release day. Delivered daily, weekly, or hourly as an API, files, or straight into your warehouse. Get a sample of this dataset scoped to your codes and country list.
API, files, or your warehouse. Daily, weekly, or hourly.
- geography
- United States totals plus breakdowns by partner country (~240), by US state, and by customs district/port depending on the endpoint chosen
- How far back
- January 2010 to present, extended each press-release day; the seasonally adjusted end-use series reach back to 1994
- How fine
- Monthly flows per commodity code at HS2/HS4/HS6 up to 10-digit Schedule B detail, crossed with country, state or port
What is the US Census International Trade dataset for Schedule B 8429?
It is the US government's own account of America's earthmoving-machinery trade, one tidy row at a time. The Census Bureau is the official compiler of US export and import statistics, and commodity detail runs to the 10-digit Schedule B level for exports. Heading 8429 of the Schedule B 2026 chapter 84 file covers "self-propelled bulldozers, angledozers, graders, levelers, scrapers, mechanical shovels, excavators, shovel loaders, tamping machines and roadrollers", and it breaks into queryable subheadings: 8429.11 track-laying bulldozers (split new versus used/rebuilt), 8429.19 other bulldozers, 8429.20.0000 graders and levelers, 8429.30 scrapers (divided at a 13.7 cubic-meter bucket threshold) and 8429.40 tamping machines and road rollers (vibratory versus other). Each carries its own 10-digit number and unit of quantity.
Every observation joins three axes: a commodity code, a trading partner and a month. Roughly 17,000 active 10-digit export codes exist in a typical year, crossed with around 240 partner countries, and each cell carries dollar value for the month and year-to-date, unit counts, and vessel, air and containerized value splits. The underlying records originate from Electronic Export Information filed in Customs' ACE system - real shipment declarations, not estimates - which is why analysts treat these figures as the ground truth of the trade.
What do sample rows look like?
Flat, monthly, one row per commodity code per partner - shaped to load straight into a warehouse table. Illustrative rows in the delivered column order:
year: 2026 month: 6 e_commodity: 842911 comm_desc: Track-laying bulldozers and angledozers, new
cty_name: Canada unit_qy1: NO. all_val_mo: 12345678 all_val_yr: 98765432 qty_1_mo: 450
ves_val_mo: 9000000 air_val_mo: 500000 cnt_val_mo: 7000000 last_update: 2026-08-06
year: 2026 month: 5 e_commodity: 842940 comm_desc: Tamping machines and road rollers, vibratory
cty_name: Australia unit_qy1: NO. all_val_mo: 4210550 all_val_yr: 18930400 qty_1_mo: 96
ves_val_mo: 4180300 air_val_mo: 0 cnt_val_mo: 30250 last_update: 2026-08-06
year: 2026 month: 6 e_commodity: 842952 comm_desc: Self-propelled shovel loaders, new
cty_name: Mexico unit_qy1: NO. all_val_mo: 6874300 all_val_yr: 31204880 qty_1_mo: 214
ves_val_mo: 1204000 air_val_mo: 180500 cnt_val_mo: 5489900 last_update: 2026-08-06The block already says something. Canadian buyers took $12.3 million of new track-laying dozers in June alone - $9 million of it moving by vessel - while Australian demand concentrated almost entirely in ocean freight, as you would expect for 20-tonne machines crossing the Pacific. The Mexico row shows the opposite pattern: nearly 80% of the value moved containerized, consistent with cross-border parts-and-units flows. Value divided by units gives an implied price per machine - here roughly $27,000-$44,000 average per unit across the three rows - a free sanity check on any pricing assumption. Request a sample and you get rows scoped to your own code list and country set.
What fields does the dataset include?
Sixteen documented fields define the observation: two commodity descriptions, the aggregation-controlled code itself, monthly and year-to-date dollar values, quantity with its unit code, partner identifiers, three transport-mode value splits, customs district, calendar keys and a refresh timestamp. Field definitions are verified against the publisher's own variable metadata rather than inferred from documentation prose.
The dictionary below is the verified core. Deeper columns confirmed during sample preparation fold out on request rather than being promised blind.
What does coverage look like across geography, time and granularity?
Geography - United States totals first, then three ways to cut them: by partner country (roughly 240 of them, four-character codes and names included), by US state, and by customs district or port on the port-level endpoints. That last cut matters for logistics people: it shows not just that $12 million of dozers went to Canada but through which border district they actually crossed.
Temporal - January 2010 to present on the trade endpoints, extended every month on press-release day, with each record stamped by a LAST_UPDATE date so revisions are visible instead of silent. The companion end-use series, seasonally adjusted, reach back to 1994 when your analysis needs a longer arc than fifteen years.
Granularity - monthly flows per commodity code at HS2, HS4 or HS6 aggregation up to full 10-digit Schedule B detail, crossed with country, state or port. You choose the aggregation level; the schema underneath does not move, so a dashboard built at HS6 keeps working when you drill to 10 digits.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Pick the channel your team already works in: REST-style queries for live lookups against a specific code and country, flat files sized for overnight warehouse loads, or a direct pipe into Snowflake, BigQuery or Redshift. Cadence is yours to set - and to change when your models change.
Every delivery ships with the full field dictionary, sample rows for validation, and a schema that holds steady between refreshes.
Who uses this data, and for what?
- Partner-country demand tracking - rank the markets actually buying American dozers, excavators and rollers month by month; see our market researchers use cases page.
- OEM demand sensing - monthly dollar values and unit counts are the highest-frequency official proxy for heavy-equipment order books, arriving weeks ahead of annual production surveys.
- Tariff and reshoring reporting - ground every headline in 10-digit official figures with a named government publisher behind them, the standard newsroom-data-desk move.
- Import-surge monitoring - watch the mirrored import side for exactly the 8429 subheadings where foreign machines threaten domestic share; more on our competitive intel product teams use cases page.
- Quant features and models - a fifteen-year monthly panel with verified definitions drops straight into a feature store; see our data scientists use cases.
- Logistics mix analysis - vessel, air and containerized value splits reveal how heavy iron physically reaches each market, useful to freight planners and equipment financiers alike.
Which personas get the most value?
Data scientists and ML engineers get a fifteen-year monthly panel with stable codes and verified field definitions - no scraping archaeology, no silent schema drift. Investors and quant researchers get the freshest official read on construction-machinery demand, a high-frequency complement to quarterly OEM filings. Market researchers and consultants get country-by-country demand sizing with citable provenance behind every chart. Journalists, academics and students get primary government statistics standing behind tariff and trade stories. Competitive intelligence teams get early warning on import pressure in precisely the subheadings they compete in. Developers building data products get one monthly schema that pipes into dashboards and alerting without per-release surgery.
What should I know before requesting a sample?
Four things worth knowing upfront.
First, exemptions create blind spots. Export figures derive from Electronic Export Information filed in Customs' ACE system, and very low-value shipments that qualify for exemption never enter the record - irrelevant for bulldozers, material for anyone joining this to small-parts trade.
Second, the import mirror speaks a different dialect: import detail is keyed to HTS codes rather than Schedule B numbers, so a two-way analysis needs a code mapping, which we supply with the sample.
Third, monthly figures get revised in later releases, and the LAST_UPDATE field makes that visible. Build pipelines that re-pull rather than cache if finality matters to your series.
Fourth, classification follows configuration - the scraper line splits at a 13.7 cubic-meter bucket threshold, so a machine can change codes when its bucket changes. Anyone comparing multi-year series should aggregate to subheading level before drawing trend conclusions.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
E_COMMODITY | string | Export Harmonized/Schedule B commodity code at 2-, 4-, 6- or 10-character aggregation; the COMM_LVL parameter controls which level you get. 842911 is track-laying bulldozers, new. | 842911 |
E_COMMODITY_SDESC | string | 50-character short description of the export Harmonized code. | Bulldozers, track laying, nesoi, new |
E_COMMODITY_LDESC | string | 150-character long description of the export Harmonized code. | Track-laying bulldozers and angledozers, new |
ALL_VAL_MO | number | Total value of trade for the month, in US dollars. | 12345678 |
ALL_VAL_YR | number | Year-to-date total value of trade, in US dollars. | 98765432 |
QTY_1_MO | number | Quantity 1 for the month in the commodity's UNIT_QY1 unit - for 8429 items typically number of units shipped. | 450 |
UNIT_QY1 | string | Three-character unit-of-quantity code for Quantity 1. | NO. |
CTY_CODE | string | Four-character trading-partner country code. | 5700 |
CTY_NAME | string | Fifty-character name of the trading partner. | Canada |
VES_VAL_MO | number | Value shipped by vessel for the month, in US dollars. | 9000000 |
AIR_VAL_MO | number | Value shipped by air for the month, in US dollars. | 500000 |
CNT_VAL_MO | number | Containerized vessel value for the month, in US dollars. | 7000000 |
DISTRICT | string | Two-character customs district code, populated on port-level endpoints. | 4401 |
MONTH | integer | Two-character month of the observation. | 6 |
YEAR | integer | Four-character year of the observation. | 2026 |
LAST_UPDATE | date | Ten-character date the record was last refreshed. | 2026-08-06 |
Additional fields on request | - | Import-side variables keyed to HTS codes rather than Schedule B numbers, QTY_2 with its own unit code, weight splits alongside the container/vessel/air value columns, state-level and port-level variants, and the seasonally adjusted end-use series reaching back to 1994 - definitions and examples ship with your sample on request. | - |
What teams do with it
- Partner-country demand tracking Rank the markets actually buying American bulldozers, excavators and rollers month by month instead of relying on association bulletins.
- OEM demand sensing for investors Read monthly 8429 dollar values and unit counts as the highest-frequency official proxy for heavy-equipment order books.
- Tariff and reshoring journalism Ground every claim about equipment trade shifts in official 10-digit figures with a named government publisher behind them.
- Import-surge competitive alerts Watch the mirrored import side for HS 8429 lines where foreign machines are taking domestic share.
- Pricing and volume modeling Unit counts against dollar values give an implied average value per machine by code and destination - a defensible anchor for pricing work.
- Logistics mix analysis Vessel, air and containerized value splits show how heavy iron physically moves to each market.
Questions buyers ask
What exactly does heading 8429 cover?
Self-propelled earthmoving and compaction machinery: track-laying bulldozers and angledozers, other bulldozers, graders and levelers, scrapers, tamping machines and road rollers, forward loaders, and other mechanical shovels, excavators and shovel loaders. The heading breaks into subheadings such as 8429.11 (track-laying bulldozers, split new versus used/rebuilt), 8429.19, 8429.20.0000, 8429.30 (cut at a 13.7 cubic-meter bucket threshold) and 8429.40 (vibratory versus other), each resolving to 10-digit Schedule B numbers with their own unit of quantity.
How current is the data, and how far back does it run?
The trade endpoints extend from January 2010 to the present and are extended each month on press-release day; every record carries a LAST_UPDATE date so you can see exactly when a figure was touched. The companion end-use series, seasonally adjusted, reach back to 1994 for longer-horizon trend work.
Which countries can I break exports out by?
Roughly 240 trading partners, identified by four-character country code and name - Canada (5700), Mexico (2010) and Australia (5780) among them. The same endpoints also support US state and customs district/port cuts, so you can follow not just who buys but through which gateway the machines leave the country.
Do I get quantities as well as dollar values?
Yes. Alongside monthly and year-to-date dollar values, every commodity line carries a unit of quantity - typically number of units for 8429 items - so you get unit counts shipped, not just revenue. Dividing value by quantity gives an implied average value per machine by code and destination, which is a useful sanity check on any pricing model.
How does this differ from production-side datasets like the Annual Survey of Manufactures?
Direction and frequency. The Annual Survey of Manufactures cube for NAICS 333120 measures what US plants produce once a year - employment, payroll, value of shipments - while this dataset measures cross-border flows monthly, by destination country, down to the individual 10-digit code. Production tells you capacity; these flows tell you what actually moved and to whom, twelve times a year.
What are the caveats before I build on it?
Four worth knowing. Export figures derive from Electronic Export Information filed in Customs' ACE system, so very low-value shipments that qualify for exemption never appear. Import-side detail is keyed to HTS codes rather than Schedule B numbers, so the mirror needs a code mapping. Monthly figures can be revised in later releases, which the LAST_UPDATE field makes visible. And the scraper split at the 13.7 cubic-meter bucket threshold means some product lines change code when bucket configurations change - worth remembering when comparing years.
Datasets that pair with this one
- MachineryTrader Construction Equipment Listings The offer side of the same market: dealer asking prices for comparable machines, complementary to these realized export flows.
- FHWA Highway Statistics - US vehicle & truck registration data Domestic fleet context - registration counts that frame how much iron stays home versus ships out.
- NHTSA vPIC API (vehicle product information catalog) Decode vehicle and equipment identifiers referenced in shipment documentation into structured make-model records.
- data.gov catalog: construction machinery search The wider federal metadata catalog, searchable for machinery terms - discovery layer for related government series.
- Schedule B commodity codes explained How the 10-digit classification works and why it is the sharpest lens available on US export flows.
- Construction Machinery & Heavy Transportation Equipment data hub The full pooled industry view, from federal trade series to marketplace listings.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.