Analysis of Front Suspension Ball Joint Separations in Motor Vehicle Crashes
Bibliographic record
Abstract
In crash analyses, components or component assemblies are evaluated to identify if they were damaged as a result of the crash or if they lost function prior to the crash. Determining the circumstances that cause a component to become disabled can be useful when evaluating the cause of a crash. This study focuses on spherical ball joints commonly used in automotive suspension systems. Analyses can include the evaluation of the ball joint itself, the surrounding components, evidence at the scene, and the circumstances of the specific crash. In this study, the causes and conditions for a ball joint separation are analyzed, in part, through both component level testing and full vehicle testing. Laboratory tests were performed on upper ball joint assemblies where loads were applied in multiple directions and the residual damage to the components was measured and documented. Full vehicle testing was performed to analyze vehicle response to suspension ball joint separations on independent front suspensions. A lower ball joint separation test was conducted with the staged ball joint separation occurring as the vehicle was being operated. An upper ball joint separation test was conducted by disconnecting the upper ball joint prior to testing and evaluating the modified vehicle response to driver inputs. Residual damage to suspension, components, and the test surface were analyzed as well. Case studies of ball joint separations are presented and compared to the controlled test results.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".