Fireground Radio Traffic Examples By Phase (Arrival, Attack, PAR, Overhaul)

New firefighters tend to think that radio work is something they will pick up by listening. They are half right. You do absorb a lot just by riding the rig and hearing how the senior people talk to dispatch and to command. The problem is that a working fire is not the time to start translating what you hear into what you should say. By the time the first hose line is moving, the volume on the radio doubles, the cadence speeds up, and a probie who has not rehearsed the phases will go silent at exactly the moment the officer needs information.

This post walks through what fireground radio traffic actually sounds like across the four phases that show up on almost every structure fire. Arrival and size up. Initial attack and benchmarks. PAR cycles and accountability. Overhaul and termination. The examples below are written in the cadence and structure that aligns with NFPA 1561 incident management principles and the post-2001 trend toward clear text radio communication. They are not 10-codes. They are not perfect scripts. They are patterns you can rehearse out loud until the rhythm is in your bones.

If you take one thing from this post, take this. Radio is not a personality test. The crews who sound calm and competent on the radio are not naturally calmer. They have rehearsed the patterns so many times that the words come out without thinking, which frees their brain to do the actual work of running a fire.

The arrival report is the single most important radio transmission on a working fire. It sets the tactical tone for every unit responding, it gives the chief a mental picture before they roll up, and it tells dispatch how to handle the rest of the assignment. A good arrival report is short, structured, and predictable.

The pattern most agencies have converged on includes the following elements in roughly this order. Unit identifier. On scene confirmation. Building description. Smoke and fire conditions. Action being taken. Command declaration. Resource needs.

Here is what that sounds like on a one story residential with light smoke from the eaves.

"Engine 12 on scene. One story single family residential, approximately 1,500 square feet, light smoke showing from the Bravo side eaves. Engine 12 will be investigating, no command at this time, all other units continue."

Same building, working fire visible from the Alpha side.

"Engine 12 on scene. One story single family residential, approximately 1,500 square feet, heavy smoke and fire showing from a Side Alpha bedroom window. Engine 12 stretching a 1 and 3 quarter inch attack line for an offensive interior attack through the Alpha side. Engine 12 has command, Main Street Command. Truck 5 your assignment is search and ventilation, Engine 8 your assignment is water supply and a backup line."

Notice what is in there and what is not. The size up is observational. It says what is visible. It does not editorialize. The command declaration is unambiguous. The assignments are short and directive. There is no story telling. There are no apologies for the radio traffic being incomplete. The next units know exactly what they need to do before they even arrive.

A few common rookie patterns that score poorly. Burying the building description. Using vague terms like "smoke showing" without describing volume, color, or location. Forgetting to declare command, which leaves the next due unit guessing whether to pass command or take it. Stacking too many resource requests into one transmission so dispatch cannot copy.

Once the attack is underway, the radio traffic shifts from descriptive to benchmark driven. Benchmarks are the verbal markers that tell command a tactical objective has been completed. They let the chief track the progress of the fire from the command post without having to ask every two minutes.

The most common benchmarks on a structure fire include water on the fire, primary search complete, secondary search complete, vertical or horizontal ventilation in place, utilities secured, fire under control, and loss stopped. Each benchmark is transmitted by the unit responsible for that task, in clear text, with the unit identifier and the completed action.

What it sounds like.

"Command from Engine 12, we have water on the fire."

"Command from Truck 5, primary search complete, all clear on the first floor."

"Command from Truck 5, vertical ventilation is in place over the Alpha side."

"Command from Engine 12, fire is under control."

These are not full sentences. They are not stories. They are clean, identifier first, completed action second. The reason for that structure is that command is tracking a tactical worksheet and needs to check off boxes as benchmarks come in. If the radio traffic is wrapped in extra words, the box does not get checked, and command may end up calling the unit back to confirm.

A common probie mistake during the attack phase is reporting interesting observations as if they were benchmarks. "Command from Engine 12, we found a pet in the back bedroom." That is useful information but it is not a benchmark and it should be delivered as a face to face report or as a structured transmission, not buried in the benchmark cadence.

PAR stands for Personnel Accountability Report. It is the periodic check that every member assigned to the incident is accounted for, by name or by riding position, by their company officer. PAR cycles are typically called every 10 to 20 minutes on a working fire, and they are also called any time conditions change significantly. Examples of triggering events include a flashover, a partial collapse, a sudden change from offensive to defensive operations, or a missing member.

The flow is initiated by command and answered by each company officer.

"All units, Main Street Command, PAR check."

"Engine 12, PAR of three on the attack line, Alpha side interior."

"Truck 5, PAR of four on the roof, Alpha side."

"Engine 8, PAR of three on water supply at the hydrant."

"Battalion 2 to Main Street Command, all companies PAR, accountability is good."

The PAR is not just a roll call. It is a verification that the officer has eyes on or voice contact with every member of the crew. If an officer cannot confirm a member, the correct answer is not to fudge the count. The correct answer is to transmit a partial PAR and immediately escalate. "Engine 12 to Command, PAR of two of three on the attack line, missing one." That transmission triggers an immediate location attempt and may rapidly escalate to a mayday and the deployment of the RIT team per NFPA 1407 principles.

Probies riding the rig should know two things about PAR. First, your officer is responsible for accounting for you, so stay within voice or sight contact at all times. If the officer turns to grab a tool and you wander, you have just made the officer's job harder on the next PAR cycle. Second, learn to keep your radio quiet during a PAR. Step on a PAR transmission and you may delay command's ability to confirm accountability, which in a deteriorating situation is a safety issue.

Once the fire is out, the radio cadence slows down but it does not stop. Overhaul has its own traffic patterns and the termination of command has a clean structure that signals the incident is closing out.

During overhaul, the company officers report progress and any findings to command. Findings might include hidden fire in a void space, structural concerns, or items of evidentiary interest if the cause is suspicious. The radio traffic stays brief and observational.

"Command from Engine 12, overhaul is in progress in the Alpha side bedroom, we have opened the ceiling and are checking the void space."

"Command from Engine 12, we have a hot spot in the attic above the Alpha bedroom, requesting Truck 5 to bring the thermal imager."

When command transitions or terminates, the transmission is explicit. The transition from one chief to another follows a face to face briefing in person and a single radio transmission to announce the change. The termination of the incident is a transmission to dispatch confirming all units are clear or returning to service.

"Dispatch from Main Street Command, the fire is under control, no extension, no injuries reported. Engine 12, Engine 8, and Truck 5 will remain on scene for overhaul. Engine 14 and Medic 3 are clear to return to service."

The pattern is the same as the arrival report. Short. Structured. Predictable. The same discipline that opened the incident also closes it.

Reading radio traffic in a blog post will not get the cadence into your mouth. You have to rehearse it the way you rehearse a hose load or a knot, with repetition and feedback. The most useful drills you can do as a probie or as a newly promoted company officer are tabletop drills where the captain calls out a scenario and you deliver the appropriate radio transmission out loud. Do thirty arrival reports for thirty different building types. Do fifteen PAR responses where the captain randomly omits a member and you have to catch it. Do ten command terminations.

If you do not have a captain who can run drills with you on demand, StruckBox includes a tactical fire simulator that scores your size up reports and radio communication against the patterns described above. You speak into your phone, the AI grades you on structure, completeness, and tactical priority, and you get written feedback on what would have scored well with a real incident commander and what would have lost points. It runs in the cadence of a real incident, which is the part that books and lectures cannot replicate. Reps with feedback is what closes the gap between knowing the patterns and being able to deliver them when the smoke is showing.