Las Vegas Fire & Rescue Fire Reporting Documentation PDF

101.00 Fire Reporting Documentation.doc Page 1 of 19 Standard Operating Procedure for Fire Reporting Documentation No: Reviewed date: Effective date: Supersedes: I. II. III. FR101.00 04/21 11/15/21 11/28/18 Type: Department: Signature: Expires: Administration – 100 series Las Vegas Fire & Rescue 11/...

101.00 Fire Reporting Documentation.doc Page 1 of 19 Standard Operating Procedure for Fire Reporting Documentation No: Reviewed date: Effective date: Supersedes: I. II. III. FR101.00 04/21 11/15/21 11/28/18 Type: Department: Signature: Expires: Administration – 100 series Las Vegas Fire & Rescue 11/15/26 INTRODUCTION A. Purpose: To provide basic instruction regarding documentation of incident responses rendered by members of the Department in compliance with the National Fire Incident Reporting System (NFIRS). B. Scope: This information is provided to all suppression personnel and those responding to an emergency scene. Though much of this instruction describes Zoll FireRMS processes, NFIRS data entry is mandatory in the patient care record system as well. C. Author: The Deputy Chief over Emergency Services, or designee, shall be responsible for the content, review, and revision of this information. RESPONSIBILITY A. It shall be the responsibility of all Las Vegas Fire & Rescue personnel to be familiar with incident reporting documentation requirements. B. It shall be the responsibility of City of Las Vegas Information Technologies to maintain records management systems for LVFR. In the event of an issue with the system(s), LVFR personnel should call the IT Help Desk. C. It shall be the responsibility of the Authorizing Member Making the Report to verify that all responding units have documented actions and narratives before marking an incident record complete. DEFINITIONS A. National Fire Incident Reporting System (NFIRS): a national system to which Department statistics must be provided regularly. This system is supported through the Federal Emergency Management Agency (FEMA), United States Fire Administration, from the National Fire Data Center. LVFR’s records management system(s) (RMS) support these reporting requirements. B. National Fire Protection Agency (NFPA): a national regulatory organization to which requested documentation must be provided regularly. A regulatory manual is provided by this organization defining various 101.00 Fire Reporting Documentation.doc Page 2 of 19 standards, objectives, and skills, which Las Vegas Fire & Rescue uses as guidelines. The NFIRS reporting format is based on NFPA 901 Uniform Coding for Fire Protection. C. D. IV. Record Management System (RMS) Report: A complete documented fire department incident report that encompasses: Incident Command with Incident Narrative, and Company Reports with Company Narratives from all units responding to a call, recording all Persons Involved. Persons Involved could include: owners, occupants, witnesses, by-standers, patients or injured firefighters. 1. This document serves as a legal document, and an essential research record. 2. The report is frequently subpoenaed and requested by insurance companies for proof, fact-findings on incidents involving injuries, damages, litigations, and insurance claims. Exposure fire: As per NFIRS 5.0 Complete Reference Guide, Chapter 3-7), exposure fire is defined as a fire resulting from another fire outside that building, structure, or vehicle, or a fire that extends to an outside property from a building, structure, or vehicle. For example, if the building fire ignites a truck parked outside, the truck fire is an exposure fire. 1. In the case of buildings with internal fire separations (i.e. strip malls), treat the fire spread from one separation to another as an exposure. Treating multiple ownership of property within a building (e.g., condominiums) as exposures, unless separated by fire-rated compartments, is discouraged. 2. When a fire involves more than one building, each building fire should be considered a separate fire, with the ignition for all but the original building fire classified as exposure fires. 3. Whenever a fire encompasses multiple exposures, each one should be documented with the same Incident number, incrementing the exposure number starting with “000” as the main. The exposure allows a verifiable count of the number of properties involved in a large fire. POLICY A. Submission of Reports 1. All electronic RMS reports shall be completed before the end of the shift to which they apply. Leaving incomplete reports is not acceptable unless the incident extends past the time of shift ending. 101.00 Fire Reporting Documentation.doc B. V. Page 3 of 19 2. It is the company officer’s responsibility to ensure that all electronic incident reports are completed by all responding units daily. 3. Failure to complete an incident report in a timely manner is cause for disciplinary action. 4. Reports should answer all questions concerning the incident, as well as paint a picture. Reports must be proofread, including: grammar, punctuation, and spelling. Reporting Requirements: 1. Complete an incident report for every call generated whenever a unit leaves the station. Only calls canceled prior to going en route do not require documentation through the records management system. This ensures all calls responded to are documented, including canceled en route, standby calls, false alarms, etc. 2. “The original report(s) should be completed by the person who gathered the data. It should reflect what was actually seen or done at the incident.” NFPA901 4.4.5 Report Completion 3. “The legal function of reporting incidents can be satisfied with a written narrative of the basic facts, or it can be as sophisticated as an automated system from which data can be retrieved on demand... An incident report must be clearly structured and must use uniform definitions and terminology.” NFPA901 4.5 Fact Finding 4. A separate Incident Report should be completed for each unique CAD-generated number. 5. “Once data has been received, it should be processed into a record useful for legal, planning, and management purposes. The first step involves checking the report for accuracy and completeness and then aggregating information into a composite record.” NFIRS901 4.6 Data Processing PROCEDURES A. Complete required fields and modules, based on individual incident scenario: 1. The basic Incident Reporting Requirement fields are defined in NFIRS 5.0 Complete Reference Guide. The complete manual is available from https://www.usfa.fema.gov/data/nfirs/support/documentation.html 101.00 Fire Reporting Documentation.doc Page 4 of 19 and also the Operations SharePoint site. This manual identifies each field specifically and its description and use. 2. Many fields populate automatically from CAD data. Other fields require manual entry. 3. Tabs and fields become active or mandatory depending on information entered on other tabs/fields. a) 4. Example: Selecting a 111 – Building fire with No aid given or received, activates the Fire and Structure modules now mandatory to complete. Dates and Times: All dates and times are entered as numerals. For time of day, the 24-hour clock is used (Midnight is 0000, 2:20 p.m. is 1420). a) Alarm time is important for three reasons: (1) as a legal requirement for recording the precise time notification was made of the incident; (2) as information for determining the frequency of particular types of incidents by time period, and (3) as the starting time to determine the length of time taken to arrive at an incident and the total amount of time spent on the incident scene. b) Enter the month, day, year (mm/dd/yyyy), and time to the exact minute when the original alarm was received by the fire department. Use numbers to indicate months of the year (i.e. 01 for January, 10 for October). The data input should match LVFR’s official time stamp, as shown in Visinet. c) Relevant times include: (1) Alarm: Time call was received. (2) En route: Time unit responded. (3) Arrival: Time arrived at the address unit dispatched to. (4) Cleared or In-service: Time unit reports being inservice or available. 101.00 Fire Reporting Documentation.doc d) Page 5 of 19 If the Member Making Report or Incident Commander is aware of a more accurate time stamp due to a communication delay or MCT failure, that time should be used. (1) Note the manual time change in a narrative stating: “the CAD time was different (xx:xx) compared to the observed time (xx:xx).” 5. Incident Number: The number assigned to the call by the CAD (typically auto populated). 6. Incident Type: Reflects the type of incident found by emergency personnel at the scene. a) DO NOT SELECT INCIDENT TYPE BASED ON INITIAL DISPATCH CODE; SELECT IT BASED ON WHAT IS FOUND ON SCENE. b) Each Incident Type has its own requirements. (i.e., a Fire in a Building [FIB] requires specifics concerning the building, materials, and structural information. Vehicle fires require specifics concerning make, model, and VIN of the vehicle damaged). c) Multiple situations may occur on one incident scene; if so, always use the lowest numbered incident type series that applies. d) (1) Example: a vehicle accident (322-324) that includes a vehicle fire (130’s) should be coded as a vehicle fire, as the 130 series is lower than 322, regardless of whether dispatched to a vehicle accident or vehicle fire. (2) If a more serious condition (lower numbered series) develops after arrival, then that incident type should be recorded. (3) Multiple actions taken or provision of medical aid can be described later in the report. Incident Types are organized into series as follows: (1) 100 Fire. Includes fires out on arrival and gas vapor explosions. 101.00 Fire Reporting Documentation.doc Page 6 of 19 (2) 200 Overpressure Rupture, Explosion, Overheat (No Fire). (3) 300 Rescue and EMS Incidents. (4) 400 Hazardous Conditions (No Fire). (5) 500 Service Call. (6) 600 Good Intent Call. (7) 700 False Alarms & False Call. (8) 800 Severe Weather & Natural Disaster. (9) 900 Special Incident Type. e) For incidents involving fire and hazardous materials or fire and EMS, use the fire codes. Always use the lowest numbered series that applies to the incident. Multiple actions taken can be described later in the report. f) For vehicle fires on a structure, use the mobile property fire codes (130–138) unless the structure became involved, i.e. parking garages. g) For fires in buildings that are confined to noncombustible containers, use codes 113–118 of the structure fire codes when there is no flame damage beyond the noncombustible container. For example: “Pot on the stove” with fire confined to pot (113). (1) h) Fire in certain non-combustible household appliances, such as a microwave, clothes dryer, or toaster oven are NOT confined fires. If they occurred in a structure, they should be coded as a 111. There are incident types reflecting situations in which no incident is found upon arrival (see 600 - Good Intent codes NOT 700 - False Alarm codes). 7. Station: Station number should reflect the first arriving LVFR unit or first LVFR unit serving as incident command. This associates the incident to the station/unit responsible for finalizing the report. 8. Aid Given or Received: Aid given to or received by another fire department, either automatically (i.e., prearranged by agreement) or mutually (i.e., requested for a specific incident). 101.00 Fire Reporting Documentation.doc a) Las Vegas Fire & Rescue deploys as part of an automatic aid system with Clark County and North Las Vegas fire departments. (1) b) Page 7 of 19 LVFR rarely gives or receives mutual aid. For NFIRS, two conditions must be true to record aid, automatic or mutual, was given or received: (1) Incident involves another fire department; AND (2) Both fire departments are at the incident (on scene or staged). c) Aid Received: LVFR handles an incident with another fire department’s assistance. FireRMS codes 2-Auto or 4Mutual. d) Aid Given (automatic or mutual): LVFR assists another fire department at an incident OR LVFR covers a vacated station while the receiving fire department is busy at an incident. FireRMS codes 1-Auto or 3-Mutual. e) Other Aid Given: LVFR responds to another jurisdiction where the legal jurisdiction’s department WAS NOT ASSIGNED TO RESPOND to the incident. (1) f) Other aid given is common for LVFR due to the automatic aid agreement with neighboring FD’s where LVFR is the only FD assigned to respond. FireRMS code 5. No Aid: LVFR handles an incident within its legal jurisdiction without help from adjacent fire departments OR LVFR is canceled en route. FireRMS code N. 9. Detector: The presence in the general area of fire origin of one or more detectors that was within the operational range of the detector(s) at the time of an incident. a) Check or mark the box if a detector alerted the occupants (regardless of whether the detector was smoke, heat, carbon monoxide, etc.). b) This block can be left blank for non-fire incidents, and can optionally be used for a carbon monoxide (CO) incident and whether a CO detector operated. 101.00 Fire Reporting Documentation.doc 10. 11. Page 8 of 19 Hazardous Materials Release: This element provides information on whether or not hazardous materials were released at the incident, what the materials were, and whether the HazMat Module should be completed. This allows LVFR to document hazardous material releases as minor spills that occur in the everyday environment without the need to complete the HazMat Module. a) Select option best describing the type of spill or release at the incident. If no hazardous materials were involved or no HazMat release, select N – None. b) Complete the HazMat Module if special HazMat actions were required, including the need for special protective clothing or equipment, or if the spill was equal to or greater than 55 gallons. Fire spread: Equals the extent of flame damage (actual burned or charred area ONLY). Do NOT include area(s) impacted only by heat, smoke, or water damage. a) This element describes the magnitude or seriousness of the fire. b) It can be used to “evaluate the effectiveness of built-in fire protection features or the effectiveness of the fire suppression force in the confinement and extinguishment of a fire.” (1) c) LVFR will use its confined rate as a performance measure. Fire spread (or confinement levels) include: (1) Object of origin. (2) Room of origin. A room is “a partitioned part of the inside of a building.” (3) Floor of origin. (4) Building of origin. (a) Describe flame damage beyond the area of origin in a one-room building such as a shed as confined to building of origin. 101.00 Fire Reporting Documentation.doc (b) d) 12. Page 9 of 19 Confined to building of origin is appropriate when the fire is on the roof or outside wall of a building. If the fire is confined to the object of origin, check Fire Confined to Object of Origin on Fire > Property > Ignition tab. (1) This select will then autopopulate Fire Spread on the Structure tab, if that tab is required. (2) Otherwise, select the correct level of spread or confinement under Structure > Description > Fire Spread. Location Type (correct incident location): Address information should self-populate from CAD with the exception of exposures where crews enter information from the original incident record. a) Address: A regular, complete street address. b) Intersection: No street address. Enter the first street in the street or highway field. The intersecting street(s) is entered in the cross street or directions field. c) In front of: No street address; however, the incident location is in front of an area with a street address. Example: a park, plaza, or common area in front of a building with a street address. d) Rear of: No street address; however, the incident location is in the rear of an area with a street address. Example: an alley running behind a building with a street address. e) Adjacent to: No street address. However, the incident location is adjacent to an area with a street address. Example: an empty lot or common area next to a building with a street address. 13. Resources or Narrative Unit Number: Enter, for example E10 using capital letter and no space between the letter and number. 14. Personnel on unit: Unit personnel should populate automatically from the rostering system. a) If personnel is incorrect or missing, the member completing the unit information should delete incorrect and add correct personnel. 101.00 Fire Reporting Documentation.doc b) 15. Page 10 of 19 If personnel is not auto-populating, contact a battalion chief and City IT Help Desk when discovered. Actions Taken: Basic Response Actions Taken field(s) are the most significant action(s) taken by each LVFR unit dispatched (use the code with the lowest numerical value first). a) This is a required field. b) Enter codes for up to the three most significant actions taken at the incident; enter the code with the lowest numerical value first. (1) Specific actions range from extinguishing fires to simply standing by. (2) c) Resources Apparatus Actions Taken field(s) (1) 16. If this is a HazMat incident and the HazMat Module is activated, list the non-HazMat actions taken on the basic tab and the Actions Taken specific to handling the hazardous materials incident in the HazMat Module. Each unit should document its most significant action(s) taken. Estimated Dollar Loss and Values: An estimate of the property and contents dollar loss is required for all fires where there is value. a) Property loss results if the building, structure, outside property, or vehicle sustained damage during the incident from flame, smoke, suppression activities, or overhaul. b) Content loss results if the contents of the building, structure, outside property, or vehicle sustained damage during the incident from flame, smoke, suppression activities, or overhaul and those contents had value (not trash or other valueless materials). c) Estimates are not intended to be legally binding. Insurance companies and property owners will obtain independent loss estimates. d) Estimates should be made in whole dollars. 101.00 Fire Reporting Documentation.doc e) 17. Page 11 of 19 If automatic or mutual aid given is selected on the Basic Response tab, estimated dollar loss is NOT available, as the jurisdiction that received the aid will report dollar loss. Fire Casualties: A person injured or killed as a result of the fire incident or while involved in the activities of fire control, attempting rescue, or escaping from the dangers of fire. a) Fire fatality includes people who die within one (1) year from injuries sustained from the fire. b) DO NOT record civilian injury or death caused by an event other than fire (i.e., gun shot wound with subsequent fire). If no fire casualties, select “NO” on the Basic Response tab. c) A FIREFIGHTER INJURY is physical damage to an LVFR employee that requires treatment by a medical practitioner within one (1) year of the fire, or at least one (1) day of restricted activity immediately following the fire incident. d) Identify and separately record the number of fire service personnel and the number of civilians or other non-fire department personnel casualties. (1) Civilians include emergency personnel who are not members of the fire department, such as police officers or utility workers. (a) (2) The total of civilian casualties includes fireincident related injuries and deaths only. Fire service casualties should include all injuries or deaths related to any type of incident. 18. Persons or Entity Involved: Enter the full name of the company or agency occupying the property where the incident occurred. This may or may not be the same as the owner. a) Owner: Enter the full name of the person, company, or agency that owns the property where the incident occurred. b) Mobile Property: Fire involving Equipment or Vehicles is required to obtain information such as make, model, and VIN of the equipment if available. This element provides detailed information that identifies the specific types of mobile property involved in an incident. 101.00 Fire Reporting Documentation.doc c) Page 12 of 19 The information in this block precisely identifies the mobile property involved in a fire’s ignition. The following information should be recorded: (1) Type: Property that is designed and constructed to be mobile, movable under its own power, or towed, such as an airplane, automobile, boat, cargo trailer, farm vehicle, motorcycle, or recreational vehicle. (2) Make: The name of the manufacturer of the mobile property that is commonly used to describe it, such as “three-bedroom” (mobile home) or “four-door” (sedan). (3) Year: The year the mobile property was manufactured. (4) License Plate Number (if any): The number on the license plates affixed to the vehicle. License numbers may also be available for boats, airplanes, and farm vehicles. (5) State: The state in which the vehicle is licensed. If a commercial vehicle is licensed in multiple states, record the NV license. If no license exists for the incident’s state, use the state license of the vehicle’s home origin. (6) VIN: The manufacturer Vehicle Identification Number that is generally stamped on an identification plate on the mobile property. 19. All fires require information concerning materials ignited, cause, and information concerning ignition. Enter the code that best describes the type of material first ignited by the heat source. Enter the first material ignited by the heat source. For example, if an arsonist poured gasoline on a wooden floor, it was the gasoline and not the wood that was the material first ignited. If an insulated wire short circuits, it may be the wire’s insulation that was first ignited; or it may be the wood studs in the wall, thermal insulation nearby, or another material. 20. Authorization: a) Officer in Charge: The ranking fire service person dealing with the incident. Position refers to the person’s rank, while assignment refers to the job held at the time of the incident. 101.00 Fire Reporting Documentation.doc b) Member Making Report: When someone other than the officer in charge completes the report, the signature of that person indicates a source for further information on the incident. In these cases, the officer in charge should review the completed report and sign it as well. (1) The incident should not be marked complete until all assigned units have completed their actions taken and narrative tasks. (a) B. Page 13 of 19 Not all ranks have the authority to uncheck the complete box. Narratives 1. Title: Name each narrative using the radio call sign of the UNIT (i.e. E10). The letter should be capitalized and no space between the letter and the number. 2. Select either Incident and/or Company for narrative type. a) INCIDENT is the master or main summary of the event stated by one unit. Typically the perspective of the unit responsible for the full report (i.e. LVFR Incident Commander or only unit on scene). (1) b) 3. There shall be only one (1) INCIDENT narrative per incident report. COMPANY is used by all other responding units. Whether documenting as INCIDENT or COMPANY,describe what was reported, what was actually discovered, unit specific operations (assigned or completed), or other conditions encountered. Describe the incident in your own words. a) Of particular importance are observations or specific information that could aid investigators, property owners, or insurance companies (i.e. correct address if dispatch address doesn’t match, VIN numbers, addresses of other structures impacted, property released to management, etc). b) Format: Acceptable narrative formats include SAC, SOAP, or a variation for EMS charting, or story-type. 101.00 Fire Reporting Documentation.doc c) Page 14 of 19 An example of SAC: (1) (2) “S” - Situation: Described as the problem/nature description of the call. (i.e., FIB, Fire Signals). This could come via dispatch, printout, air, MDT, dispatcher comments, or by-standers. Situation should indicate actual incident type found on scene, especially if different from dispatched reason (Example: S1) (a) Example S: T1 responded as part of an HLevel response to a reported FIB in a two-story duplex apartment. T1 arrived on scene and gave a BIR, confirming incident type building fire and reporting heavy smoke in two apartments. T1 established Ellis command and remained in command mode. All occupants were reported out of the building and the initial report claimed a plumber was soldering copper pipes in the bathroom of one of the apartments. T1 announced an IAP to locate and confine the fire to area of origin using an offensive interior fire attack, ventilate and obtain a life search. B1 arrived shortly after T1 and assumed Ellis command continuing with the IAP of T1. E201 assigned to FA, supported by E8 which eventually became north division. T1 assigned vent group and R301assigned I-RIT. Upon CBRNE8’s arrival they were assigned RIT, and R301’s crew became fire medical group. E3 assigned salvage group and E4 became south division. (b) Example S1: T1 responded as part of an HLevel response to a reported FIB in a two-story duplex apartment. PR states a candle burning in the bedroom caught a wooden shelf on fire and the PR put it out with water. “A” - Action: Objective findings, what was observed / seen. Overall assessment. As Incident command this would include the assignments you give. As a company unit this would include the assignment you received. (a) Example A: T1 arrived to the Alpha side of 2422 Rainbow and established Rainbow 101.00 Fire Reporting Documentation.doc Page 15 of 19 command giving a BIR that both duplex apartments were heavily involved in fire. After initial 360, command gave follow-up report and IAP to locate and confine fire to area of origin using offensive interior attack, ventilate using PPV, and conduct life search. B1 arrived shortly after T1 and assumed Ellis command continuing with IAP of T1. T1 copied new assignment of vent group. As we approached building, found heavy fire showing from Alpha side from both apartment doors and three of the four windows. Vent and FA met and agreed to focus attack on apt on A/B side or apt #1. Attack lines pulled by FA and vent prepared fan to support FA at apt 1. Vent confirmed exhaust opening on C side, fan placed in front door, a noticeable improvement made on smoke conditions interior, FA gained access to apt #2 using a second fan. Vent confirmed exhaust on C side but did not place fan into opening. Upon arrival of second FA team, vent placed fan in door and confirmed success. Vent group reported to command assignment fulfilled, ready for another assignment. Command advised vent to recycle and go to an on deck position. T1 recycled and stood by on deck. After some time, command released T1 back to service after picking up equipment. (b) Example A1: T1 arrived on scene, established command, locating command to the Alpha side of 2-story duplex and reported BIR of nothing showing with PR outside waving down FD units. Command advised all units to reduce to code 1 while command continued investigation. Entered first floor of 2121 Ellis and found no smoke or heat present. Making our way back to the bedroom, we found a small wooden shelf attached to the wall with small burn pattern with melted wax covering it. Fire was out and did not extend to the structure itself. T1 opened bedroom window to vent the burned wood odor and advised owner to close at their discretion. All other responding units cancelled before arrival. T1 terminated command and RTS. 101.00 Fire Reporting Documentation.doc (3) Page 16 of 19 “C” - Conclusion: Brief overall assessment of what was completed and accomplished. As incident command, this would include the conclusion of the scene to include transfer of property if appropriate. As a company unit, this would include the assessment of your assignment. (a) Example C: T1 responded and arrived establishing Rainbow command and gave BIR. After conducting 360, reported findings and established and announced IAP. At this point B1 arrived on scene, assumed Rainbow command from T1 and assigned T1 to Ventilation group. T1 fulfilled PPV assignment coordinating efforts with FA teams. Once done, T1 recycled and RTS. (b) Example C1: T1 responded as part of an Hlevel alarm to possible FIB in two-story duplex apartment. T1 arrived and located and est command, reported findings of nothing showing. Upon further investigations, located small shelf with burn pattern from melted candle. Command confirmed fire was out and that there was no extension, cancelled all other responding units. Command was cancelled and T1 RTS. 4. See the Las Vegas Fire & Rescue Approved Fire Abbreviations list for approved abbreviations. 5. References a) NFPA 901: National Fire Protection Agency Standard Classification for Incident Reporting and Fire Protection Data, current edition. b) NFIRS: National Fire Incident Reporting System Complete Reference Guide, January 2015. c) LVFR NFIRS Coding Guidance. 101.00 Fire Reporting Documentation.doc Page 17 of 19 Las Vegas Fire & Rescue Approved fire reporting abbreviations A AC APPROX AOS AFC B BBQ BC BIR BLDG C CBRNE CCFD CO COA D DC DIC DOA E EMS1 ENG ENGR EST EXT FA FC FCR FF FFP FIB FRI FTO HM HMT HR HVAC HWY IC ICS ISO L LIC LVFR A side (street side of the BLDG) Assistant Chief Approximately Arrived on scene Assistant Fire Chief B Side (Left side of BLDG as you face the BLDG from the ST) Barbeque Battalion Chief Brief initial report Building C Side (Rear side of BLDG as you face the BLDG from the ST) Chemical, Biological, Radiological, Nuclear, and Explosive Clark County Fire Department Company Officer Canceled on arrival D Side (Right side of BLDG as you face the BLDG from the ST) Deputy Chief Deputy incident commander Dead on arrival East Emergency Medical Services Field Coordinator Engine Engineer Established Extension Fire attack Fire Chief Fire control room Firefighter Firefighter/Paramedic Fire in a building Friday Fire Training Officer Hazmat Hazmat Team Heavy Rescue Heating ventilation air conditioning Highway Incident Commander Incident Command System Incident Safety Officer Left License Las Vegas Fire & Rescue 101.00 Fire Reporting Documentation.doc MFD MINS MON METRO MVA N NE NW NLVFD NVE PIO POS PPV PR R REHAB RIT RTS S SE SW SA SAT SCBA SFD SOP ST STD SUN S&H S&R SSSFD SWG Thur Tues TRT TX VENT VIN VV W Wed YOM YOF YR YRS 1X Multi-family dwelling Minutes Monday Metropolitan Police Department Motor vehicle accident North North East North West North Las Vegas Fire Department Nevada Energy Public Information Officer Pot on stove Positive pressure ventilation Person reporting Right Rehabilitation Unit Rapid Intervention Team Return to service South South East South West Senior Advisor Saturday Self-contained breathing apparatus Single family dwelling Standard Operating Procedure Street Stated Sunday Salvage and overhaul Search & rescue Single story single family dwelling SouthWest Gas Thursday Tuesday Technical Rescue Team Treatment Ventilation Vehicle identification number Vertical ventilation West Wednesday Year old male Year old female Year Years One time (and others i.e. 2X, 3X) Page 18 of 19 101.00 Fire Reporting Documentation.doc ***Unit Call Signs*** 6i# AR# B# CBRN# MCP E# HAZ# HR# SQ# MED# R# T# WT# Investigations unit + call sign Air Resource unit + call sign Battalion Chief unit + call sign CBRNE unit + call sign Mobile Command Post Engine unit + call sign Hazmat unit + call sign Heavy Rescue unit + call sign Squad unit + call sign Bike Medic unit + call sign Rescue unit + call sign Truck unit + call sign Water Tender unit + call sign ***Non-Fire Department Call Signs*** AMR ATF CA CORN GEM LG MA MAS MWA American Medical Response Alcohol, Tobacco, and Firearms Unit Community Ambulance Coroner Guardian Elite Medical Services Life Guard Mobile Air Mercy Air Service Medic West Ambulance Page 19 of 19