Bridge strike¶

A transport collision in which an overheight road vehicle, vessel or load impacts a bridge, overpass or tunnel structure, creating immediate and network-level safety risk.

Version: v1 · 2026-09-08 · History
Domain-specific #: 3544
Origin domain: transport safety
Subdomain: structure vehicle collisions

Core Idea¶

A bridge strike is physical collision of a moving transport unit or its load with a bridge or related constrained structure. Clearance or navigation incompatibility persists through route selection and warning barriers until movement produces contact, damaging vehicle, structure or services and disrupting the network. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

The load-bearing residual is not the broad topic of transport safety. It is infrastructure collision class spanning overheight road and vessel impacts with distinctive systemic consequences.

Scope of Application¶

Bridge strike belongs to transport safety and is useful where the analyst can specify a vehicle or vessel and load, a bridge or tunnel geometry, route and clearance information, driver or navigation decisions, warning and protection systems, an impact event, and consequences, then evaluate a transport vehicle or load physically impacts the defined bridge, overpass or tunnel element rather than merely violating a clearance rule. The scope is broad within that domain but bounded by the need for a transport vehicle or load physically impacts the defined bridge, overpass or tunnel element rather than merely violating a clearance rule. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making a transport vehicle or load physically impacts the defined bridge, overpass or tunnel element rather than merely violating a clearance rule the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name Bridge strike can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Bridge strike. Bridge strike compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: a vehicle or vessel and load, a bridge or tunnel geometry, route and clearance information, driver or navigation decisions, warning and protection systems, an impact event, and consequences. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express a transport vehicle or load physically impacts the defined bridge, overpass or tunnel element rather than merely violating a clearance rule independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of transport safety because they reuse a vehicle or vessel and load, a bridge or tunnel geometry, route and clearance information, driver or navigation decisions, warning and protection systems, an impact event, and consequences, Clearance or navigation incompatibility persists through route selection and warning barriers until movement produces contact, damaging vehicle, structure or services and disrupting the network., and type the carrier, state every parameter and convention in the definition, test that a transport vehicle or load physically impacts the defined bridge, overpass or tunnel element rather than merely violating a clearance rule, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Bridge strike Domain-specific

Parents (1) — more general patterns this builds on

Bridge strike is a kind of Failure Mode and Effects Analysis (FMEA) Prime

The proposed strict upward parent is prime:failure_mode_and_effects_analysis_fmea.

Hierarchy paths (4) — routes to 4 parentless roots

Bridge strike → Failure Mode and Effects Analysis (FMEA) → Risk → Uncertainty

Show alternative paths (3)

Neighborhood in Abstraction Space¶

Bridge strike sits in a moderately populated region (53^rd percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Risk, Scheduling & Operational Control (32 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08