Breakfall Clearance
Check breakfall floor clearance against travel, reach, and buffer.
Description
A one-dimensional breakfall clearance budget adds anticipated travel, performer reach and a buffer.
A one-dimensional breakfall clearance budget adds anticipated travel, performer reach and a buffer. The sum can be compared with a measured clear floor length.1
Check breakfall floor clearance against travel, reach, and buffer.
When to use Breakfall Clearance
Use this tool to check breakfall floor clearance against travel, reach, and buffer.
Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
How to use Breakfall Clearance and understand its results
- Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
- Enter fallTravelMeters, performerReachMeters, clearFloorLengthMeters, requiredBufferMeters using the field table and calculation rules, then run the tool.
- Read requiredClearanceMeters, clearanceMarginMeters, adequate. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| fallTravelMeters | Planned fall travel (m) | number; minimum: 0 | Required |
| performerReachMeters | Performer reach allowance (m) | number; minimum: 0 | Required |
| clearFloorLengthMeters | Clear floor length (m) | number; minimum: 0 | Required |
| requiredBufferMeters | Required buffer (m) | number; minimum: 0 | Required |
Enter nonnegative lengths in meters. Return required clearance, signed remaining margin and inclusive adequacy flag. Exact equality passes this numeric check.
required=travel+reach+buffer; margin=clearLength−required Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| requiredClearanceMeters | Required clearance (m) | number; minimum: 0 |
| clearanceMarginMeters | Clearance margin (m) | number |
| adequate | Clearance is adequate | boolean |
{
"input": {
"fallTravelMeters": 2,
"performerReachMeters": 1,
"clearFloorLengthMeters": 4,
"requiredBufferMeters": 0.5
},
"output": {
"requiredClearanceMeters": 3.5,
"clearanceMarginMeters": 0.5,
"adequate": true
}
}Limitations and assumptions
Floor condition, fall dynamics, lateral clearance, technique and obstacles are not evaluated. A passing length budget does not establish that a breakfall is safe.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Fight-Beat Continuity: Reconcile scripted and rehearsed fight-beat identifiers. For a complementary task, use Exit Capacity: Calculate exit capacity from supplied clear widths and capacity rate.
References
-
Breakfall Clearance — tool.io
Similar or alternative tools
- Fight-Beat Continuity
Reconcile scripted and rehearsed fight-beat identifiers.
- Exit Capacity
Calculate exit capacity from supplied clear widths and capacity rate.