Skip to Content
CrashComputeTraffic Crash Investigation Tools
Menu

Transparent by design

Know what the number means—and how it was checked.

CrashCompute keeps the method, inputs, arithmetic, and limitations visible so an investigator can review the work and another reviewer can reproduce it.

01 Source02 Verify03 Record

Published software check

Validation snapshot

All checks passed
66 / 66checks passed
0failures
US + metricunit systems exercised
v1.9.1checked August 4, 2026

This is a reproducible software check, not an external certification. Run the current suite and preserve its output with each important project record.

01 · Calculation policy

Separate the arithmetic from the opinion.

CrashCompute is a calculation and documentation aid. Each worksheet keeps case inputs separate from derived results and, where applicable, displays the equation, substituted values, unit conversions, and worked arithmetic.

The person using the result remains responsible for selecting a method that fits the evidence and supporting every material input.

Correct arithmetic is not proof of applicability.Corroborate important conclusions with physical evidence and an independent method.

02 · Source discipline

Make the method traceable.

Worksheet source notes identify the equation or guidance implemented when a published method is used. Before reporting a result, confirm that the selected source and edition apply to the assignment.

Source titleAuthor or issuing bodyEdition or yearPage or sectionJurisdictional guidanceMethod limitations

Common source families include vehicle-dynamics and traffic-crash analysis texts, SAE technical literature, NHTSA material, AASHTO roadway guidance, MUTCD traffic-control guidance, and manufacturer-specific EDR/CDR documentation. Inclusion does not imply endorsement by a publisher or agency.

03 · Software verification

What the built-in suite checks

The app recomputes expected values independently and compares them with worksheet output using defined tolerances.

01

Equation checks

Known inputs are compared with independently computed numerical results.

02

Unit checks

Equivalent US customary and metric cases are checked for agreement.

03

Coverage checks

Every calculation worksheet is exercised in both unit systems and checked for finite output.

Suite coverage

19 check groups
Motion and roadwaySpeed · Drag · Yaw · Airborne · Time · Sight
Collision dynamicsMomentum · Rotation · Crush · Energy · Geometry
Road users and vehiclesPedestrian · Motorcycle · Heavy vehicle
System integrityExtended worksheets · Units · Solar · Map · Coverage

The suite demonstrates

  • Specified examples return their expected result within tolerance.
  • Unit conversions agree for equivalent physical cases.
  • Default worksheet paths complete without invalid numerical output.

The suite does not determine

  • Whether evidence or measurements are reliable.
  • Whether a formula applies to the event under investigation.
  • Whether assumptions, uncertainty, or reporting are professionally sufficient.
Run it in your browser.Save or print the result with the app version when a project requires a software-check record.
Open verification suite

04 · Reproducible review

Preserve the path to the result.

A concise review record helps another investigator understand what was measured, what was assumed, and what was calculated.

  1. Define the questionIdentify the physical evidence and the question the worksheet addresses.
  2. Preserve the inputsRecord each measurement, original unit, source, assumption, and uncertainty range.
  3. Confirm applicabilityState why the equation fits and note conditions it does not model.
  4. Check the workReview the displayed arithmetic and independently spot-check the result.
  5. Archive the recordRecord the app version, export the worksheet, and preserve the supporting source material.

Minimum source record

Fields to preserve with the worksheet

Evidence
Item, location, collection method, and original measurement
Method
Equation name and reason it applies
Authority
Source, edition, year, and page or section
Uncertainty
Supported range, sensitivity, and limiting assumptions
Software
CrashCompute version and verification output
Corroboration
Independent method, reviewer, or comparison used

Units, precision, and rounding

  • Preserve the original field measurement and enter the unit shown.
  • Use unrounded intermediate values when available.
  • Report only the precision supported by the least precise material input.
  • Use ranges or sensitivity testing when a single value is not defensible.

05 · Change control

Make corrections visible.

CrashCompute displays its current version in the app and verification output. A material equation or implementation correction should be accompanied by a version change and a repeat of the relevant verification checks.

Found a calculation or citation issue?Email the worksheet name, inputs, expected result, source, and app version to crash@crashcompute.com.Do not send confidential case evidence unless you are authorized to do so.

06 · Scope and limitations

The tool supports judgment. It does not replace it.

CrashCompute does not determine which marks, measurements, events, or records are reliable. It does not replace training, calibration, inspection, peer review, or professional judgment.

Vehicle configurationSurface conditionRoadway gradeBraking statePost-impact motionTiming uncertaintySource-specific limits