03_analysis

How the speeds were solved

The forward model is fully determined once the two approach speeds are chosen: impact, then separation to rest. So the speeds are found by repeating that until the simulated rest positions and headings match the documented ones, each weighted by the uncertainty recorded for that document.

The impact

Closing speed, normal
14.4 m/s
Change of speed, A
28 km/h
Change of speed, B
30 km/h
Energy dissipated
81 kJ
39% of pre-impact kinetic energy
Contact regime: common-velocity. Contact reached a common tangential velocity before separation; the tangential impulse required was within the impulse-ratio limit.

Linear and angular momentum are conserved exactly. The analysis refuses any solution whose normal impulse is not compressive, that leaves the vehicles still approaching after separation, or that would create kinetic energy.

Agreement with the documented rest positions

Trajectory match
VehiclePosition errorHeading error
A0.05 m0.4°
B0.06 m0.3°

The threshold adopted for this work is 1.5 m and 15 degrees. This reconstruction is within that threshold.

The fit was started from 25 different starting points and found 1 distinct solution. A single distinct solution across all starting points means the speeds are well determined by the rest positions. More than one means the bundle must present a range, not a point.

Which assumption moves the answer

Every uncertain input was moved to each end of its stated range with the others held at their adopted values, and the whole reconstruction re-solved each time. This is not an error bar drawn around a point answer — it is the answer, re-derived.

One-at-a-time influence, worst first
AssumptionSwing in A (km/h)Swing in B (km/h)
Tyre-road drag factor (post-impact)6.25.0
Impact-plane normal bearing5.22.5
Coefficient of restitution1.64.1
Vehicle A yaw inertia factor1.80.8
Contact point along the impact plane0.71.6
Vehicle A kerb mass1.20.1
Vehicle B kerb mass1.10.1
Impact-plane impulse ratio1.00.4
Vehicle B yaw inertia factor0.60.2

The reported range

Vehicle A
49–56 km/h
5th to 95th percentile
Vehicle B
37–44 km/h
5th to 95th percentile
Monte Carlo draws
120
120 requested, 0 failed to converge

Every input was drawn from its range simultaneously by Latin hypercube and the entire inverse problem re-solved for each draw. Draws that failed to converge are counted and excluded, never replaced.

The combined uncertainty leaves a workable speed range; the bundle presents the range, not a single figure.

The engine

CapSeal Recon reference solver
CapSeal Recon reference solver is a transparent solver built by PayFar Global Ltd and used to develop and test the pipeline. It is NOT a court-accepted commercial engine and it has NOT been validated against published staged collisions. A bundle produced with it must not be presented to an independent expert as the primary analysis (scope document section 6, step 4).

Whichever engine runs, the complete input deck — every parameter, its source and the range it is swept across — is written into the bundle, so the analysis can be re-run independently rather than taken on trust.