Structured as a summary under Rule 36(9)(b) of the Uniform Rules of Court: assumptions, inputs, method, results, uncertainty, conclusion. Written in the first person so that an independent expert can adopt it — and marked draft until one does.
This is a draft summary of expert opinion prepared in the structure of a summary under Rule 36(9)(b) of the Uniform Rules of Court. It has been generated by CapSeal Recon from the sealed evidence listed in section 4 and is placed before an independent reconstruction expert for review, correction and, if the expert is satisfied, adoption and signature.
Until it is adopted and signed by that expert it is a draft and it is not expert evidence. The expert, not the software and not the party, is the witness.
| Item | Detail |
|---|---|
| Claim reference (anonymised) | CLAIM-A |
| Intersection | Main Road / Church Street (anonymised) |
| Date and time of collision | 2023-04-17T07:42:00+02:00 |
| Control at the intersection | Signal-controlled (robot) |
| Vehicle A | Vehicle A (eastbound, Main Road) - 2016 Toyota Corolla Quest |
| Vehicle B | Vehicle B (northbound, Church Street) - 2019 Volkswagen Polo Vivo |
| Prepared on | 26 August 2026 |
| Status | DRAFT - not signed, not expert evidence |
| Prepared by | CapSeal Recon 0.2.0 for PayFar Global Ltd |
| Reviewing expert | [to be appointed] |
The expert who adopts this report does so on the following terms, which are reproduced here so that they are part of the document the court reads.
I was instructed to determine, so far as the physical evidence allows, the speeds of the two vehicles at the instant of contact, the order in which they entered the intersection, and whether each driver's account of the collision is capable of producing the physical evidence recorded at the scene.
The analysis is a two-vehicle planar reconstruction. It does not address occupant kinematics, injury causation, vehicle defect, or the conduct of either driver beyond what the physical evidence establishes.
Every document and file I considered is listed below. Each was hashed on receipt and recorded in a sealed manifest with a chain-of-custody log; the manifest travels with this report as 00_manifest and can be re-verified independently.
All 10 evidence files in this bundle are intake-sealed. They were hashed and timestamped on receipt by PayFar; integrity is asserted from intake onward only. No file in this bundle is capture-sealed, so capture-time integrity is not asserted for any of them. This is the expected position for a retrospective POC claim.
| Item | Category | File | Provenance | Timestamp authority | SHA-256 |
|---|---|---|---|---|---|
| E001 | vehicles | A_damage_front.png | intake-sealed | http://timestamp.digicert.com | 7f1f7e0ba8d71be7... |
| E002 | vehicles | B_damage_left.png | intake-sealed | http://timestamp.digicert.com | 522d43c86294174b... |
| E003 | rest_positions | scene_rest_positions.png | intake-sealed | http://timestamp.digicert.com | adfba5d12f67040e... |
| E004 | rest_positions | police_ar_form.pdf | intake-sealed | http://timestamp.digicert.com | ae475c85c243ac8f... |
| E005 | scene | assessor_measurement_sheet.csv | intake-sealed | http://timestamp.digicert.com | 76242bdda24a0ca9... |
| E006 | statements | driver_statements.txt | intake-sealed | http://timestamp.digicert.com | 31d05e9e66c350de... |
| E007 | telematics | telematics_A.csv | intake-sealed | http://timestamp.digicert.com | d9bbc8d1073f4187... |
| E008 | video | dashcam_B_frames.png | intake-sealed | http://timestamp.digicert.com | efbbce974c9bffde... |
| E009 | outcome | outcome_record.txt | intake-sealed | http://timestamp.digicert.com | 5abdcc976f8ead6b... |
| E000 | statements | claim.yaml | intake-sealed | http://timestamp.digicert.com | a64d028d93466e03... |
Provenance tiers: capture-sealed material was hashed at the moment of capture; intake-sealed material was hashed on receipt and no assertion is made about its integrity before that moment.
The table below lists every numerical assumption the analysis depends on, the value adopted, the range over which the analysis was repeated, how confident I am in the value, and where it came from. Nothing else was assumed.
The following parameters were not documented for these vehicles and were taken from a specification database or a segment-class default: cg_from_front_axle_ratio, cg_height_m, front_overhang_share, height_m, kerb_mass_kg, length_m, occupant_mass_kg, payload_mass_kg, track_m, wheelbase_m, width_m, yaw_inertia_factor. Each was swept across the range shown, so the effect of that estimation on the answer is visible in section 9 rather than hidden in a single figure.
| Applies to | Parameter | Adopted | Range tested | Confidence | Source |
|---|---|---|---|---|---|
| Vehicle A | kerb_mass_kg | 1215 kg | 1142 to 1288 | indicative | Manufacturer published specification (indicative) [toyota_corolla_quest_2016] |
| Vehicle A | occupant_mass_kg | 75 kg | 70.5 to 79.5 | indicative | claim file: 1 occupant(s) at 75 kg unless stated |
| Vehicle A | payload_mass_kg | 0 kg | 0 to 0 | indicative | not recorded on the claim file; taken as zero |
| Vehicle A | length_m | 4.53 m | 4.258 to 4.802 | indicative | Manufacturer published specification (indicative) [toyota_corolla_quest_2016] |
| Vehicle A | width_m | 1.76 m | 1.654 to 1.866 | indicative | Manufacturer published specification (indicative) [toyota_corolla_quest_2016] |
| Vehicle A | height_m | 1.46 m | 1.372 to 1.548 | indicative | Manufacturer published specification (indicative) [toyota_corolla_quest_2016] |
| Vehicle A | wheelbase_m | 2.6 m | 2.444 to 2.756 | indicative | Manufacturer published specification (indicative) [toyota_corolla_quest_2016] |
| Vehicle A | track_m | 1.48 m | 1.391 to 1.569 | indicative | Manufacturer published specification (indicative) [toyota_corolla_quest_2016] |
| Vehicle A | cg_from_front_axle_ratio | 0.45 - | 0.396 to 0.504 | class-default | class default [c_segment] - C-segment / compact sedan or hatch |
| Vehicle A | cg_height_m | 0.54 m | 0.4752 to 0.6048 | class-default | class default [c_segment] - C-segment / compact sedan or hatch |
| Vehicle A | front_overhang_share | 0.55 - | 0.45 to 0.65 | indicative | CapSeal default: share of total overhang ahead of the front axle |
| Vehicle A | yaw_inertia_factor | 0.9 - | 0.8 to 1 | indicative | CapSeal default: k in Izz = k*m*(L^2+W^2)/12 |
| Vehicle B | kerb_mass_kg | 1070 kg | 1006 to 1134 | indicative | Manufacturer published specification (indicative) [vw_polo_vivo_hatch_2018] |
| Vehicle B | occupant_mass_kg | 150 kg | 141 to 159 | indicative | claim file: 2 occupant(s) at 75 kg unless stated |
| Vehicle B | payload_mass_kg | 0 kg | 0 to 0 | indicative | not recorded on the claim file; taken as zero |
| Vehicle B | length_m | 3.97 m | 3.732 to 4.208 | indicative | Manufacturer published specification (indicative) [vw_polo_vivo_hatch_2018] |
| Vehicle B | width_m | 1.68 m | 1.579 to 1.781 | indicative | Manufacturer published specification (indicative) [vw_polo_vivo_hatch_2018] |
| Vehicle B | height_m | 1.47 m | 1.382 to 1.558 | indicative | Manufacturer published specification (indicative) [vw_polo_vivo_hatch_2018] |
| Vehicle B | wheelbase_m | 2.47 m | 2.322 to 2.618 | indicative | Manufacturer published specification (indicative) [vw_polo_vivo_hatch_2018] |
| Vehicle B | track_m | 1.46 m | 1.372 to 1.548 | indicative | Manufacturer published specification (indicative) [vw_polo_vivo_hatch_2018] |
| Vehicle B | cg_from_front_axle_ratio | 0.44 - | 0.3872 to 0.4928 | class-default | class default [b_segment] - B-segment / small hatch or sedan |
| Vehicle B | cg_height_m | 0.53 m | 0.4664 to 0.5936 | class-default | class default [b_segment] - B-segment / small hatch or sedan |
| Vehicle B | front_overhang_share | 0.55 - | 0.45 to 0.65 | indicative | CapSeal default: share of total overhang ahead of the front axle |
| Vehicle B | yaw_inertia_factor | 0.9 - | 0.8 to 1 | indicative | CapSeal default: k in Izz = k*m*(L^2+W^2)/12 |
| Scene | drag factor | 0.75 | 0.65 to 0.85 | published range | published range for asphalt / dry - no site measurement |
| Impact | restitution | 0.08 | 0.00 to 0.20 | published range | Structural vehicle-to-vehicle impact at this closing speed. |
| Impact | impulse ratio | 0.45 | 0.30 to 0.70 | published range | Inter-vehicle tangential impulse ratio; not directly measurable. |
The scene was modelled to scale from the source stated below together with the assessor's site measurements. Accuracy is bounded by those measurements; no survey-grade scan was carried out.
| Item | Value |
|---|---|
| Coordinate frame | Local plane, origin at the intersection centre, +x east, +y north, metres |
| Scene basis | Municipal orthophoto tile 2023-06 (demonstration reference) |
| Measurements | Assessor site visit, tape and hand laser, per CapSeal measurement protocol v1 (demonstration) |
| Plan uncertainty | +/- 0.20 m |
| Surface | asphalt / dry |
| Light and weather | daylight / clear |
| Rest position A | (0.20, 6.10) m, heading 334 deg, +/- 1.0 m and 10 deg - SAPS Accident Report sketch and tow record, located from the datum by the assessor |
| Rest position B | (5.40, 11.90) m, heading 20 deg, +/- 1.2 m and 12 deg - Scene photographs supplied by the insurer, located from the datum by the assessor |
| Contact point | (-1.75, 5.25) m - Located from the gouge mark recorded in the scene photographs and the upstream edge of the debris field. |
| Impact plane normal | 270 deg (bearing), acting from B onto A |
| Item | Vehicle A | Vehicle B |
|---|---|---|
| Description | 2016 Toyota Corolla Quest | 2019 Volkswagen Polo Vivo |
| Mass at collision (kg) | 1290 | 1220 |
| Yaw inertia (kg.m^2) | 2285 | 1700 |
| Length x width (m) | 4.53 x 1.76 | 3.97 x 1.68 |
| Damaged face | front | left |
| Crush-energy analysis | not available - momentum only | not available - momentum only |
Where no published crush stiffness coefficients exist for a model, no crush-energy analysis was performed for that vehicle and the reconstruction rests on momentum and trajectory matching alone.
The reconstruction was carried out in four steps.
| Item | Detail |
|---|---|
| Engine | CapSeal Recon reference solver |
| Vendor | PayFar Global Ltd |
| Version | 0.2.0 |
| Court-accepted commercial engine | NO |
| Validated against published staged tests | NO |
| Statement | 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). |
The reconstruction reproduces the documented rest positions to within the figures in the second table. That agreement is what gives the speeds their weight: they are not read off a formula, they are the speeds that put both vehicles where they were actually found.
Vehicle B crossed its stop line 1.14 s before vehicle A crossed its own, on a 5th-to-95th percentile interval of 1.02 to 1.27 s. The interval does not include zero, so the entry order is established by the physical evidence at this confidence.
Signal phase timing was requested from the municipality and was not obtained. Conclusions are framed on entry order and speed, not on light colour. No clip in this bundle shows a signal head, so this reconstruction makes no statement about which vehicle had a green light. It establishes entry order and speed.
| Quantity | Value | Range across all tested assumptions |
|---|---|---|
| Speed of A at contact | 52 km/h | 49 to 56 km/h |
| Speed of B at contact | 40 km/h | 37 to 43 km/h |
| Change of speed (delta-V) of A | 28 km/h | - |
| Change of speed (delta-V) of B | 30 km/h | - |
| Energy dissipated in the impact | 81 kJ | - |
| Vehicle A crossed its stop line | 0.30 s before contact | 0.26 to 0.33 s |
| Vehicle B crossed its stop line | 1.43 s before contact | 1.29 to 1.59 s |
| Item | Position error | Heading error |
|---|---|---|
| Vehicle A rest position | 0.05 m | 0.4 deg |
| Vehicle B rest position | 0.06 m | 0.3 deg |
The threshold adopted for this work is 1.5 m and 15 degrees. This reconstruction is within that threshold.
No single figure is offered for either speed. The ranges in section 8 are the 5th to 95th percentile of a Monte Carlo sweep in which every assumption in section 5 was drawn from its stated range simultaneously and the whole reconstruction re-solved for each draw.
The combined uncertainty leaves a workable speed range; the bundle presents the range, not a single figure.
120 of 120 Monte Carlo draws produced a usable solution; draws that failed to converge are excluded and counted, not replaced.
| Assumption | Swing in A's speed (km/h) | Swing in B's speed (km/h) |
|---|---|---|
| Tyre-road drag factor (post-impact) | 6.2 | 5.0 |
| Impact-plane normal bearing | 5.2 | 2.5 |
| Coefficient of restitution | 1.6 | 4.1 |
| Vehicle A yaw inertia factor | 1.8 | 0.8 |
| Contact point along the impact plane | 0.7 | 1.6 |
| Vehicle A kerb mass | 1.2 | 0.1 |
| Vehicle B kerb mass | 1.1 | 0.1 |
| Impact-plane impulse ratio | 1.0 | 0.4 |
| Vehicle B yaw inertia factor | 0.6 | 0.2 |
Each assumption was moved to each end of the range in section 5 with all others held at their adopted values, and the whole reconstruction re-solved.
| Assumption | Setting | Value | A (km/h) | B (km/h) | Rest residual (m) |
|---|---|---|---|---|---|
| Tyre-road drag factor (post-impact) | low | 0.65 | 49 | 37 | 0.09 |
| Tyre-road drag factor (post-impact) | high | 0.85 | 55 | 42 | 0.17 |
| Coefficient of restitution | low | 0 | 52 | 39 | 1.02 |
| Coefficient of restitution | high | 0.2 | 50 | 43 | 1.32 |
| Impact-plane impulse ratio | low | 0.3 | 53 | 40 | 0.12 |
| Impact-plane impulse ratio | high | 0.7 | 52 | 40 | 0.06 |
| Vehicle A kerb mass | low | 1142 | 52 | 40 | 0.15 |
| Vehicle A kerb mass | high | 1288 | 51 | 40 | 0.17 |
| Vehicle B kerb mass | low | 1006 | 51 | 40 | 0.17 |
| Vehicle B kerb mass | high | 1134 | 52 | 40 | 0.13 |
| Vehicle A yaw inertia factor | low | 0.8 | 51 | 40 | 0.23 |
| Vehicle A yaw inertia factor | high | 1 | 53 | 40 | 0.27 |
| Vehicle B yaw inertia factor | low | 0.8 | 52 | 40 | 0.09 |
| Vehicle B yaw inertia factor | high | 1 | 52 | 40 | 0.06 |
| Contact point along the impact plane | low | -0.5 | 52 | 39 | 0.51 |
| Contact point along the impact plane | high | 0.5 | 51 | 41 | 0.45 |
| Impact-plane normal bearing | low | 260 | 57 | 37 | 0.63 |
| Impact-plane normal bearing | high | 280 | 52 | 40 | 0.17 |
Each driver's account was then run through exactly the same physics, with the same masses, the same impact geometry and the same road surface. The only thing changed was the speeds each account asserts. The question asked is narrow: does that account put the vehicles where they were found?
The account of the driver of vehicle A cannot produce the documented rest positions. Run through the same physics, with the same masses, the same impact geometry and the same road surface, it leaves vehicle B 15.8 m from where it was found (and the worst heading error is 54 degrees), against a tolerance of 2.4 m and 24 degrees. The gap is what the animation shows.
The account of the driver of vehicle B can produce the documented rest positions: run through the same physics it leaves both vehicles within 0.06 m and 0.3 degrees of where they were found. This account is not excluded by the physical evidence. It does not follow that it is what happened - more than one account can be consistent with the same evidence.
An account that is not excluded by this test is not thereby established. More than one account can be consistent with the same physical evidence, and where that is so this report says so rather than choosing between them.
| Account | Speeds asserted (A / B) | Worst rest-position error | Worst heading error | Result |
|---|---|---|---|---|
| The account of the driver of vehicle A | 50 / 75 km/h | 15.8 m | 54.5 deg | not physically consistent |
| The account of the driver of vehicle B | 52 / 40 km/h | 0.1 m | 0.3 deg | physically consistent |
Tolerance applied: 2.4 m and 24 degrees, being the consistency threshold widened by the recorded uncertainty in the rest positions themselves.
On the physical evidence recorded at the scene, the collision is reconstructed as follows. The reconstruction reproduces both documented rest positions to within 0.06 m and 0.4 degrees.
I express no opinion on which driver was at fault, or on the apportionment of damages between them. What the physical evidence constrains is set out above; the legal consequences of those facts are for the court.
Nor do I express an opinion on which vehicle had a green light, except to the extent stated in section 8.
The following limitations apply to this analysis and should be read with the conclusion.
The following are recorded so that no reader takes them as implied.
I have read this report. It reflects my own opinion, formed on the material listed in section 4 and on my own examination of the analysis. I understand that my duty is to assist the court and that this duty overrides any obligation to the party engaging me.
Expert: [to be appointed]
Qualifications:
Registration:
Signature and date