Best Arrow Setup for the Xpedition XLite 32 (2026)
Short answer: a 300–340 spine shaft cut to 29" back-of-point, a 100 gr point and a 16 gr insert — about 410.3 gr finished at 12.3% FOC, leaving the Xpedition XLite 32 near 292 fps. That is at 28" of draw and 70 lb. Six draw-length and draw-weight combinations are tabulated below, all of them inside Xpedition’s published range.
The XLite 32 is the lightest bow on this page by a clear margin and it is the one where arrow weight matters most to how the bow behaves in your hand, not just how it flies.
The recommended starting build
Every number below came out of the same engine that runs The Forge, at 28" of draw and 70 lb — the middle of this bow's published range. Nothing here is typed by hand.
- Shaft: Easton Axis 4mm Long Range, 300 spine, 9.3 gpi (.166 inside diameter; .229–.244" outside — archers shop by ID, so that is the one listed first)
- Cut length: 29" — draw length plus one inch, measured back-of-point, the Easton BOP convention
- Point: Field Point 100 gr
- Insert: Easton Axis 4mm HIT Insert, 16 gr
- Nock: Easton Axis Nock 4mm (.166), 5 gr
- Fletching: 3 × AAE Hybrid 23, 5.7 gr each, 3° offset
- Adhesive: 1.5 gr insert epoxy + 1 gr fletch glue — counted, because your scale counts it
- Total weight: 410.3 gr
- FOC: 12.3% — inside the Recommended Hunter Range (11–15%)
- Launch speed: 292 fps real-world (297 fps rated)
- Kinetic energy: 78 ft‑lb · momentum: 0.533 slug‑fps
- At 40 yards: 277 fps, 69.9 ft‑lb retained, 33.8" of drop
The spine is charted. The mass, FOC, speed, energy, momentum and drop are derived. See the note under the next table for what that distinction costs you.
Spine and build at three draw lengths
Three draw lengths inside the Xpedition-published 25"–30.5" range, at two draw weights, all on the same reference shaft. Arrow length is draw length plus one inch, measured back-of-point, which is the convention the Easton chart's length axis uses.
| Draw length | Draw weight | Arrow length | Effective draw weight | Spine window | Total weight | FOC | Speed: rated / real-world (fps) | KE (ft‑lb) | Momentum (slug‑fps) | 40 yd drop |
|---|---|---|---|---|---|---|---|---|---|---|
| 26" | 60 lb | 27" | 56.5 lb | 340–400 | 364.7 gr | 13.9% | 276 / 272 | 59.8 | 0.44 | 39.3" |
| 26" | 70 lb | 27" | 66.5 lb | 300–340 | 391.7 gr | 12.9% | 284 / 280 | 68.3 | 0.487 | 36.9" |
| 28" | 60 lb | 29" | 63.5 lb | 340–400 | 381.3 gr | 13.2% | 289 / 285 | 68.6 | 0.482 | 35.7" |
| 28" | 70 lb | 29" | 73.5 lb | 300–340 | 410.3 gr | 12.3% | 297 / 292 | 78 | 0.533 | 33.8" |
| 30" | 60 lb | 31" | 70.5 lb | 300–340 | 428.9 gr | 11.7% | 289 / 285 | 77.2 | 0.542 | 35.6" |
| 30" | 70 lb | 31" | 80.5 lb | 250–300 | 444.4 gr | 11.3% | 302 / 298 | 87.7 | 0.588 | 32.4" |
Charted versus derived, plainly. The spine window is charted: it comes
out of recommendSpineFromInputs, which reproduces Easton's published hunting selection
chart to 98% and Victory's to 89%. Effective draw weight is that chart's own intermediate
term. Everything else — total weight, FOC, speed, kinetic energy, momentum, drop — is
derived from the component sheet and a ballistics model, and derived numbers carry more error than
charted ones. Drop is computed for an arrow released level with no sight elevation, which is a
comparison figure between rows, not a hold-over.
What changes if you go heavier or lighter
One variable, four points, at 28" of draw and 70 lb on the same 300 shaft. Point weight is the lever most people reach for, so it is the one worth seeing whole.
| Point | Total weight | FOC | Effective draw weight | Spine window | Speed (fps) | KE (ft‑lb) | Momentum | 40 yd drop |
|---|---|---|---|---|---|---|---|---|
| 85 gr | 395.3 gr | 10.8% | 71.7 lb | 300–340 | 299 | 78.4 | 0.524 | 32.4" |
| 100 gr | 410.3 gr | 12.3% | 73.5 lb | 300–340 | 292 | 78 | 0.533 | 33.8" |
| 125 gr | 435.3 gr | 14.6% | 76.5 lb | 250–300 | 282 | 76.9 | 0.545 | 36.3" |
| 150 gr | 460.3 gr | 16.6% | 79.5 lb | 250–300 | 271 | 75.3 | 0.555 | 39.2" |
Read the columns against each other and the trade is obvious. Going from 85 gr to 150 gr moves FOC from 10.8% to 16.6%, costs 28 fps and 3.1 ft‑lb of kinetic energy, and gains 0.031 slug‑fps of momentum. Kinetic energy and momentum disagreeing is not an error — energy scales with the square of speed and momentum scales linearly with mass, so a heavier, slower arrow genuinely has less energy and more momentum. Momentum is the one that predicts penetration.
The direction that catches people out: adding weight at the FRONT weakens dynamic spine and pushes you toward a stiffer shaft — watch the effective-draw-weight column climb by 7.8 lb across that sweep. Adding weight at the BACK does the opposite, and at roughly half the magnitude. Heavier nocks, heavier vanes and a wrap all stiffen dynamic spine. A well-known spine calculator has that backwards; ours does not, and we show the working.
The 11–15% band is our Recommended Hunter Range for FOC. It is not a timid choice and it is not a compromise — it is where broadhead-tipped arrows recover from launch fastest without giving away the trajectory you paid for. Extreme-FOC builds have a place; a general-purpose hunting arrow off this bow is not it.
Speed: the rated number and the real one
Two speed columns run through this page and they are not the same claim. Rated is the IBO formula applied to Xpedition's published figure and adjusted for your draw length, draw weight and arrow mass — a bare bow's number. Real-world is that figure plus the measured gap between what bows of this model actually chronograph and what the formula predicts, which is where a rest, a sight, a stabiliser, a peep and a quiver all live.
| Bow | Offset vs the IBO formula | Tests (n) | Std dev |
|---|---|---|---|
| XLite 32 (2025) | -4.2 fps | 2 | 4.2 fps |
That offset is the mean of 2 chronograph tests, with a standard deviation of 4.2 fps. 2 readings spread 4.2 fps wide. That is real evidence, and it is still not your bow. Put yours over a chronograph and the whole page recomputes around the number you measure.
At the reference build the two read 297 fps rated against 292 fps real-world. Every derived number on this page — kinetic energy, momentum, drop — is computed off the real-world figure, because that is the arrow that leaves your bow.
Tuning notes for the XB32 dual cam system (XB1 module)
XB32 dual cam with the XB1 module, 80% let-off, adjustable. Xpedition publishes the spec block on the product page and it matches our catalog on every field, which is rarer than it should be — most of the twelve bows in this batch had at least one figure adrift.
Xpedition does not publish a named lateral-cam-adjustment system for this platform, so our cam-lean table has no entry rather than a guess. Tune it in the ordinary order: bare-shaft or paper at short range first, cams chase the tail, the rest moves an eighth of an inch, then broadheads confirm.
What I would actually do
A sub-four-pound bow gives back some of its accuracy in hand-shake, and the standard fix is a heavier stabiliser, which puts the weight back. The other lever is arrow mass. A heavier arrow leaves a light bow quieter and deader in the hand — you are dumping more of the stored energy into the shaft instead of into the riser. If you bought this bow for the weight and then hung a 12-inch bar off the front of it, consider going the other way and putting the grains in the arrow instead.
Draw length and mods on the Xpedition XLite 32
Two questions come before arrows: what draw lengths does this bow cover, and which module do I need. The first is published, and it is the one that changes your arrow.
- Draw length range: 25" – 30.5" (Xpedition published spec)
- Draw weights: 50, 60, 65, 70, 80 lb
The XB1 module covers the whole published span. Xpedition does not publish a public mod chart; the module is set at the shop and confirmed on a scale.
Draw length is not a comfort setting, it is a spine input. One inch is worth roughly 3.5 lb of effective draw weight — about a third of a spine class — and it moves every sight mark you have. Run your real draw length through The Forge and the spine, mass, speed and FOC all move with it; the arrow spine calculator shows the method written out; the sight tape generator reprints the tape.
Bow specifications
| Spec | Xpedition publishes |
|---|---|
| Speed rating | 342 fps |
| Axle-to-axle | 32" |
| Brace height | 6" |
| Let-off | 80%, adjustable |
| Draw length range | 25" – 30.5" |
| Draw weight | 50, 60, 65, 70, 80 lb |
| Mass weight | 3.8 lb |
| Cam | XB32 dual cam system (XB1 module) |
Every figure above read from xpeditionarchery.com — XLite 32 on 10 September 2026. If Xpedition revises them this page is wrong until we fix it — tell us at sal@sparrowexpeditions.com.
Common questions
What arrow spine do I need for a Xpedition XLite 32?
At 28 inches of draw and 70 pounds, with a 100 grain point and a standard insert, the engine's window is 300 to 340 spine on an arrow cut to 29 inches back-of-point. That window is charted against Easton's and Victory's published selection ranges. Change your draw length by an inch or your point by 25 grains and it moves, which is why this page prints six combinations rather than one number.
How fast does a Xpedition XLite 32 shoot a real hunting arrow?
About 292 feet per second with the 410.3 grain reference build on this page. The rated figure for the same arrow is 297 fps. The difference is a measured chronograph offset of -4.2 fps for this model, averaged over 2 tests. Your bow will not read exactly this. Nobody's does.
What FOC should I run on a Xpedition XLite 32?
Eleven to fifteen percent is our Recommended Hunter Range and the reference build lands at 12.3%. That band is where a broadhead-tipped arrow recovers from launch quickly without giving away trajectory. Chasing 18 or 20 percent buys penetration you can also buy with total arrow weight, and costs you drop at every distance you actually shoot.
Where do these numbers come from?
The spine windows come from the same function that runs The Forge, which reproduces Easton's published hunting selection chart to 98 percent and Victory's to 89 percent. Weight, FOC, speed, kinetic energy, momentum and drop are derived from the component sheet and a ballistics model. The bow specifications come from Xpedition's own published page, linked on this page, read on 10 September 2026. Nothing on this page was typed from memory.
Do I need a different arrow for broadheads on a Xpedition XLite 32?
No — you need the same arrow, tuned. Build the shaft on this page with field points, get it flying, then put broadheads on the same arrows and shoot them at 30 and 40 yards. If the broadhead group walks away from the field point group, that is your tune talking, not your spine choice. Fix it at the cam and the rest, in that order, and only then consider a different shaft.
Shop this setup
- Shop all arrows & shafts →
- Inserts, half-outs and collars →
- Vanes and fletching →
- Check this 300-spine build in The Forge →
Not sure the 300 is right for your draw? Put your real numbers into the arrow spine calculator — it runs the same engine as this page and it will tell you when you are between classes rather than guessing for you. Then print the tape with the sight tape generator.
Nearby bows
- Best arrow setup for the Darton TriTech 33
- Best arrow setup for the Bowtech Proven 34
- Paper tune chart and the cam-lean correction table
Built by archnerds, for archnerds — The Forge by Sparrow Expeditions. Questions, corrections and chronograph data: sal@sparrowexpeditions.com.