Copyright

Preface

Effective Use of the International Fire Code

Legislation

Chapter 1 Scope and Administration

Chapter 2 Definitions

Chapter 3 General Requirements

Chapter 4 Emergency Planning and Preparedness

Chapter 5 Fire Service Features

Chapter 6 Building Services and Systems

Chapter 7 Fire-Resistance-Rated Construction

Chapter 8 Interior Finish, Decorative Materials and Furnishings

Chapter 9 Fire Protection Systems

Chapter 10 Means of Egress

Chapter 11 Construction Requirements for Existing Buildings

Chapter 12 Through 19 Reserved

Chapter 20 Aviation Facilities

Chapter 21 Dry Cleaning

Chapter 22 Combustible Dust-Producing Operations

Chapter 23 Motor Fuel-Dispensing Facilities and Repair Garages

Chapter 24 Flammable Finishes

Chapter 25 Fruit and Crop Ripening

Chapter 26 Fumigation and Insecticidal Fogging

Chapter 27 Semiconductor Fabrication Facilities

Chapter 28 Lumber Yards and Woodworking Facilities

Chapter 29 Manufacture of Organic Coatings

Chapter 30 Industrial Ovens

Chapter 31 Tents and Other Membrane Structures

Chapter 32 High-Piled Combustible Storage

Chapter 33 Fire Safety During Construction and Demolition

Chapter 34 Tire Rebuilding and Tire Storage

Chapter 35 Welding and Other Hot Work

Chapter 36 Marinas

Chapter 37 Through 49 Reserved

Chapter 50 HAZARDOUS MATERIALS—GENERAL PROVISIONS

Chapter 51 Aerosols

Chapter 52 Combustible Fibers

Chapter 53 Compressed Gases

Chapter 54 Corrosive Materials

Chapter 55 Cryogenic Fluids

Chapter 56 Explosives and Fireworks

Chapter 57 Flammable and Combustible Liquids

Chapter 58 Flammable Gases and Flammable Cryogenic Fluids

Chapter 59 Flammable Solids

Chapter 60 Highly Toxic and Toxic Materials

Chapter 61 Liquefied Petroleum Gases

Chapter 62 Organic Peroxides

Chapter 63 Oxidizers, Oxidizing Gases and Oxidizing Cryogenic Fluids

Chapter 64 Pyrophoric Materials

Chapter 65 Pyroxylin (Cellulose Nitrate) Plastics

Chapter 66 Unstable (Reactive) Materials

Chapter 67 Water-Reactive Solids and Liquids

Chapter 68 Through 79 Reserved

Chapter 80 Referenced Standards

Appendix A Board of Appeals

Appendix B Fire-Flow Requirements for Buildings

Appendix C Fire Hydrant Locations and Distribution

Appendix D Fire Apparatus Access Roads

Appendix E Hazard Categories

Appendix F Hazard Ranking

Appendix G CRYOGENIC FLUIDS—WEIGHT AND VOLUME EQUIVALENTS

Appendix H Hazardous Materials Management Plan (Hmmp) and Hazardous Materials Inventory Statement (Hmis) Instructions

Appendix I FIRE PROTECTION SYSTEMS—NONCOMPLIANT CONDITIONS

Appendix J Building Information Sign

Introduction

Internationally, code officials recognize the need for a modern, up-to-date fire code addressing conditions hazardous to life and property from fire, explosion, handling or use of hazardous materials and the use and occupancy of buildings and premises. The International Fire Code®, in this 2012 edition, is designed to meet these needs through model code regulations that safeguard the public health and safety in all communities, large and small.

This comprehensive fire code establishes minimum regulations for fire prevention and fire protection systems using prescriptive and performance-related provisions. It is founded on broad-based principles that make possible the use of new materials and new system designs. This 2012 edition is fully compatible with all of the International Codes® (I-Codes®) published by the International Code Council (ICC)®, including the International Building Code®, International Energy Conservation Code®, International Existing Building Code®, International Fuel Gas Code®, International Green Construction CodeTM (to be available March 2012), International Mechanical Code®, ICC Performance Code®, International Plumbing Code®, International Private Sewage Disposal Code®, International Property Maintenance Code®, International Residential Code®, International Swimming Pool and Spa CodeTM (to be available March 2012), International Wildland-Urban Interface Code® and International Zoning Code®.

The International Fire Code provisions provide many benefits, among which is the model code development process that offers an international forum for fire safety professionals to discuss performance and prescriptive code requirements. This forum provides an excellent arena to debate proposed revisions. This model code also encourages international consistency in the application of provisions.

Development

The first edition of the International Fire Code (2000) was the culmination of an effort initiated in 1997 by a development committee appointed by ICC and consisting of representatives of the three statutory members of the International Code Council: Building Officials and Code Administrators International, Inc. (BOCA), International Conference of Building Officials (ICBO) and Southern Building Code Congress International (SBCCI). The intent was to draft a comprehensive set of fire safety regulations consistent with and inclusive of the scope of the existing model codes. Technical content of the latest model codes promulgated by BOCA, ICBO and SBCCI was utilized as the basis for the development, followed by public hearings in 1998 and 1999 to consider proposed changes. This 2012 edition presents the code as originally issued, with changes reflected in the 2003, 2006 and 2009 editions and further changes approved through the ICC Code Development Process through 2010. A new edition such as this is promulgated every three years.

This code is founded on principles intended to establish provisions consistent with the scope of a fire code that adequately protects public health, safety and welfare; provisions that do not unnecessarily increase construction costs; provisions that do not restrict the use of new materials, products or methods of construction; and provisions that do not give preferential treatment to particular types or classes of materials, products or methods of construction.

Adoption

The International Fire Code is available for adoption and use by jurisdictions internationally. Its use within a governmental jurisdiction is intended to be accomplished through adoption by reference in accordance with proceedings establishing the jurisdiction''s laws. At the time of adoption, jurisdictions should insert the appropriate information in provisions requiring specific local information, such as the name of the adopting jurisdiction. These locations are shown in bracketed words in small capital letters in the code and in the sample ordinance. The sample adoption ordinance on page xxi addresses several key elements of a code adoption ordinance, including the information required for insertion into the code text.

Maintenance

The International Fire Code is kept up-to-date through the review of proposed changes submitted by code enforcing officials, industry representatives, design professionals and other interested parties. Proposed changes are carefully considered through an open code development process in which all interested and affected parties may participate.

The contents of this work are subject to change both through the Code Development Cycles and the governmental body that enacts the code into law. For more information regarding the code development process, contact the Code and Standard Development Department of the International Code Council.

While the development procedure of the International Fire Code assures the highest degree of care, ICC, its members and those participating in the development of this code do not accept any liability resulting from compliance or noncompliance with the provisions because ICC and its founding members do not have the power or authority to police or enforce compliance with the contents of this code. Only the governmental body that enacts the code into law has such authority.

Code Development Committee Responsibilities
(Letter Designations in Front of Section Numbers)

In each code development cycle, proposed changes to the code are considered at the Code Development Hearings by the International Fire Code Development Committee, whose action constitutes a recommendation to the voting membership for final action on the proposed change. Proposed changes to a code section that has a number beginning with a letter in brackets are considered by a different code development committee. For example, proposed changes to code sections that have [B] in front of them (e.g. [B] 607.2 ) are considered by the appropriate International Building Code Development Committee (IBC-Means of Egress) at the code development hearings.

The content of sections in this code that begin with a letter designation is maintained by another code development committee in accordance with the following:

[A]=Administrative Code Committee
[B]= International Building Code Development Committee (IBC-Fire Safety, General, Means of Egress or Structural);
[EB]= International Existing Building Code Development Committee;
[FG]= International Fuel Gas Code Development Committee;
[M]=International Mechanical Code Development Committee; and
[P]= International Plumbing Code Development Committee.

Note that for the development of the 2015 edition of the I-Codes, there will be two groups of code development committees and they will meet in separate years. The groupings are as follows:

Group A Codes
(Heard in 2012, Code Change Proposals Deadline: January 3, 2012)
Group B Codes
(Heard in 2013, Code Change Proposals
Deadline: January 3, 2013)
International Building CodeAdministrative Provisions (Chapter 1 all codes except IRC and ICCPC, administrative updates to currently referenced standards, and designated definitions)
International Fuel Gas CodeInternational Energy Conservation Code
International Mechanical CodeInternational Existing Building Code
International Plumbing CodeInternational Fire Code
International Private Sewage
Disposal Code
International Green Construction Code
ICC Performance Code
International Property Maintenance Code
International Residential Code
International Swimming Pool and Spa Code
International Wildland-Urban Interface Code
International Zoning Code

Code change proposals submitted for code sections that have a letter designation in front of them will be heard by the respective committee responsible for such code sections. Because different committees will meet in different years, it is possible that some proposals for this code will be heard by a committee in a different year than the year in which the primary committee for this code meets.

For example, Section 907.2.13.1.2 of this code (and the IBC) is designated as the responsibility of the International Mechanical Code Development Committee. This committee will conduct its code development hearings in 2012 to consider code change proposals in its purview, which includes any proposals to Section 907.2.13.1.2.

Note also that every section of Chapter 1 of this code is designated as the responsibility of the Administrative Code Development Committee, and that committee is part of the Group B portion of the hearings. This committee will conduct its code development hearings in 2013 to consider all code change proposals for Chapter 1 of this code and proposals for Chapter 1 of all I-Codes. Therefore, any proposals received for Chapter 1 of this code will be deferred for consideration in 2013 by the Administrative Code Development Committee.

It is very important that anyone submitting code change proposals understand which code development committee is responsible for the section of the code that is the subject of the code change proposal. For further information on the code development committee responsibilities, please visit the ICC web site at www.iccsafe.org/scoping.

Marginal Markings

Solid vertical lines in the margins within the body of the code indicate a technical change from the requirements of the 2009 edition. Deletion indicators in the form of an arrow () are provided in the margin where an entire section, paragraph, exception or table has been deleted or an item in a list of items or a table has been deleted.

A single asterisk [*] placed in the margin indicates that text or a table has been relocated within the code. A double asterisk [**] placed in the margin indicates that the text or table immediately following it has been relocated there from elsewhere in the code.

The following table indicates such relocations in the 2012 International Fire Code:

Note that these * and ** margin markings are not shown for the Chapter reorganization of the IFC in this 2012 edition. For information on this reoranization, please see page vii.

Coordination between the International Building and Fire Codes

Because the coordination of technical provisions is one of the benefits of adopting the ICC family of model codes, users will find the ICC codes to be a very flexible set of model documents. To accomplish this flexibility some technical provisions are duplicated in some of the model code documents. While the International Codes are provided as a comprehensive set of model codes for the built environment, documents are occasionally adopted as a stand-alone regulation. When one of the model documents is adopted as the basis of a stand-alone code, that code should provide a complete package of requirements with enforcement assigned to the entity for which the adoption is being made.

The model codes can also be adopted as a family of complementary codes. When adopted together there should be no conflict of any of the technical provisions. When multiple model codes are adopted in a jurisdiction it is important for the adopting authority to evaluate the provisions in each code document and determine how and by which agency(ies) they will be enforced. It is important, therefore, to understand that where technical provisions are duplicated in multiple model documents that enforcement duties must be clearly assigned by the local adopting jurisdiction. ICC remains committed to providing state-of-the-art model code documents that, when adopted locally, will reduce the cost to government of code adoption and enforcement and protect the public health, safety and welfare.

Italicized Terms

Selected terms set forth in Chapter 2, Definitions, are italicized where they appear in code text. Such terms are not italicized where the definition set forth in Chapter 2 does not impart the intended meaning in the use of the term. The terms selected have definitions which the user should read carefully to facilitate better understanding of the code.

Resources