Resource search

Search DataDrivenAEC

Type at least two characters to search.

Looking for live projects? Explore open projects or browse the feed.

Open the full search page →

Source verifiedGroup B only

Egress Path
Limits

Travel distance, common path, and dead-end corridor length are three separate bounded checks with separate governing provisions.

Who it's for: architects checking Group B exit-access travel distance, common path, and dead-end corridor length against separate IBC 2024 limits for the same space, at construction documents or permit review.

Scope boundary
This preview supports Group B model-code cases only. It reports each implemented limit independently and returns “cannot determine” where required conditions are missing.

How to use this calculator

1
Enter the space's occupant load and sprinkler condition
The sprinkler condition changes the travel-distance limit, the common-path limit for 31–49 occupants, and the dead-end limit.
2
State whether more than one exit is required
If so, also state whether the dead end is less than 2.5× its least width.
3
Read each of the three limits independently
Travel distance, common path, and dead-end corridor length are reported as separate implemented results or "cannot determine" — check the applicable path against each governing provision separately.

The formula

Group B exit access travel distance is limited to 200 ft without sprinklers and 300 ft with a §903.3.1.1 sprinkler system (IBC 2024 Table 1017.2). Common path of egress travel, unsprinklered: 100 ft at 30 or fewer occupants, 75 ft for 31–49 occupants; sprinklered (§903.3.1.1 or §903.3.1.2): 100 ft up to 49 occupants (Table 1006.2.1). Dead-end corridors are limited to 20 ft where more than one exit is required, 50 ft in Group B with a §903.3.1.1 sprinkler system, and not limited where the dead end is shorter than 2.5 times its width (§1020.5 and its exceptions).

Worked example

Example
A Group B space with an occupant load of 30, unsprinklered, where more than one exit is required and the dead end does not meet the 2.5x-width ratio: exit access travel distance limit = 200 ft (Table 1017.2); common path limit = 100 ft (Table 1006.2.1, 30 or fewer occupants, unsprinklered); dead-end corridor limit = 20 ft (§1020.5, ratio exception not met).

When this estimate will be off

  • Supports Group B model-code cases only, and reports each implemented limit independently.
  • Returns "cannot determine" where required conditions are missing.
  • Measurement, geometry, special occupancies, local amendments, and complete compliance are outside scope — this does not measure or approve an egress path.

Frequently asked questions

A common mistake: Supports Group B model-code cases only, and reports each implemented limit independently.

They are three separate provisions in IBC 2024 (§1017.2, §1006.2.1, §1020.5) with different inputs and thresholds; this calculator reports each one independently rather than collapsing them into a single number.

§1006.2.1 sets the unsprinklered common-path limit at 100 ft for 30 or fewer occupants and 75 ft for 31–49 occupants, while a qualifying sprinkler system (§903.3.1.1 or §903.3.1.2) allows 100 ft up to 49 occupants — enter the occupant load and sprinkler condition to get the applicable figure.

The dead-end limit in §1020.5 applies where more than one exit is required from the space; uncheck that box and the calculator returns "cannot determine" for that check rather than assuming it applies. Leaving the ratio condition unmet does not skip the check — it applies the base 20 ft limit instead of the ratio exception.

No. Measurement, geometry, special occupancies, and local amendments remain outside this calculator's scope — it evaluates only the three implemented Group B limits.

Sources and review record

Sources and method basis

Limitations

  • Returns separate Group B model-code limits only; it does not measure a path or establish geometry, occupancy, local adoption, amendments, or complete compliance.

This free IBC Travel Distance Calculator is built and maintained by DataDrivenAEC, using the relevant codes and standards. It does not substitute for professional judgment.