A mayday is the one radio transmission in the fire service that has to work the first time, from a person who is frightened, breathing hard, wearing gloves, and possibly unable to see the radio in his hand. Everything around that transmission is a system: a button that sends something specific, a console that displays something specific, a tactical channel that has to be emptied of everyone who is not part of the rescue, and an accountability poll that tells command how many people are actually missing. This piece walks that chain end to end and is blunt about where it breaks.

Mayday and emergency traffic: two different messages

The word itself comes out of aviation rather than the fire service, and the usual account credits Frederick Mockford, a radio officer at Croydon Airport in England, who was asked in 1923 to propose a distress word that would be understood on both sides of the Channel and who built it from the French for help me. It carried into marine and aviation practice, and the American fire service adopted it for a narrower purpose than the mariners use it for.

In current published fire service practice, a mayday means a firefighter is in trouble: lost, trapped, entangled, injured, out of air, fallen through, or separated from the crew with no way out. It is declared by the member in trouble or by anyone who sees or knows about that member’s situation, which matters because an unconscious firefighter declares nothing. Emergency traffic, by contrast, is the announcement of a condition that threatens everyone working, such as an imminent collapse, a change from offensive to defensive operations, or an order to evacuate the structure. Both interrupt routine traffic and both get an alert tone, though they produce completely different actions from command.

Departments get into trouble when the two terms blur. A company officer who announces emergency traffic when a member of his crew is missing has told command that something is wrong without telling command that a rescue has started, and the minutes spent sorting that out come off a downed firefighter’s remaining air supply. The cleanest arrangement I have seen in written SOPs keeps the vocabulary very small, with mayday reserved exclusively for a firefighter in distress, emergency traffic reserved for a hazard announcement to all personnel, and nothing else allowed to preempt the channel. Whatever your agency uses, the words should be identical in the SOP, in the dispatch protocol, and in the mouths of the officers, because a mayday that dispatch logs as emergency traffic starts the wrong clock.

The declaration: words, order, and what the report has to carry

The standard opening is the word repeated three times, followed by the unit or individual identifier, and then a pause for command to acknowledge. The repetition is not ceremony. It gives the receiving ear a chance to catch the second and third instance after the first one is stepped on or lost in the noise of a working fire, and it distinguishes the transmission from someone saying the word in the middle of a sentence about something else.

After the acknowledgment comes the report, and the fire service has never settled on one format. LUNAR asks for location, unit, name, assignment and air remaining, and resources needed. LIP asks for location, identification, and problem. Others use UCAN, which is unit, conditions, actions, needs, or a locally built acronym that serves the same purpose. The particular mnemonic matters far less than whether your members can produce it without thinking, because all of them exist to force three pieces of information out of a person whose working memory has narrowed to the size of the problem in front of him: where he is, who he is, and what is wrong. Location is the one that gets dropped, and it is the one the rapid intervention crew cannot function without.

The location element deserves specific training attention, because a firefighter who is disoriented does not know where he is by definition, and telling him to report a location he does not have produces silence. Published mayday curricula generally teach the member to report the best available approximation and then keep feeding the search: the floor, the side of the building, the room type, which direction he was crawling, the last object he touched, whether he is on a hoseline and whether he is following it to the nozzle or to the coupling. A member who transmits that he is on the second floor of side C, was searching a bedroom, and is now on a line he cannot orient has given the rapid intervention crew far more than a member who transmits that he is lost and then stops talking.

The emergency button: what the radio actually sends

On a trunked P25 system, the orange button is a signaling function and the behavior is set in the codeplug, not in the radio’s nature. The two common behaviors are an emergency alarm, which sends a data message identifying the radio to the system and to the dispatch console without any audio, and an emergency call, which does that and then grants the radio a priority transmission, frequently with a hot microphone window of a fixed duration during which the radio transmits whether or not anyone is keying it. Many fleets program both, so the alarm goes out and the hot mic follows. The hot mic is genuinely useful when a member is unable to press the PTT, and it is genuinely disruptive when it holds the tactical channel open on a radio that is lying in a snowbank, so know which one your fleet is set to and how long the window runs.

The setting that causes the most trouble on a fireground is emergency revert. A radio can be programmed to send its emergency on the talkgroup it is currently using, which is called tactical emergency, or to switch automatically to a designated emergency talkgroup regardless of where the user was. Revert makes sense in some law enforcement fleets where a dedicated position monitors that talkgroup continuously. On a fireground it can take a distressed firefighter off the tactical channel where his own company officer and the incident commander are listening and drop him somewhere nobody on the incident is monitoring, and the member will not know it happened. Find out which way your fleet is programmed before you need to know.

Several other configuration choices are worth confirming in writing with whoever holds your codeplug. Whether the activation is silent or announces itself with tones and a display on the radio matters, since an audible emergency is reassurance on a fireground and a hazard on a covert assignment. Whether the field user can clear the emergency by holding the button, or whether only the console can clear it, determines who owns the record. How long the button has to be held before it triggers determines your accidental activation rate. On a conventional analog system, the button often does nothing useful at all unless the radios are programmed with an inband signaling scheme such as MDC-1200 and dispatch has a decoder that displays it, and plenty of small departments are carrying radios with an orange button wired to nothing anybody is watching. Coverage is the other limit: a radio in a basement that cannot reach the site cannot deliver an emergency alarm either, and if your system has fallen back to site trunking or failsoft, emergency processing may not behave the way it does on a normal day.

At the console: what appears, who sees it, and who can clear it

At a dispatch console, an incoming emergency usually produces a distinctive audible alert at the position, a visual indication on the affected talkgroup, and a display of the radio’s identifier and its alias. The dispatcher acknowledges it, which in most systems stops the local alert while leaving the emergency state active in the system, and then works the incident: alert tone on the tactical channel, an announcement that a mayday has been received from a specific unit, a time stamp, and confirmation that the incident commander heard it. Whether the console can clear the emergency for that radio, and whether doing so is permitted by policy, should be settled long before the day it happens.

Two console configuration questions decide whether any of that occurs. The first is which positions get the alert. If the fireground talkgroup is not selected or not unmuted at the position handling the incident, and the system is not configured to alert other positions on an emergency, the activation can sit on a screen nobody is looking at. The second is what happens when the talkgroup is in a patch or a multiselect with other talkgroups, since patching changes how audio and signaling flow and can affect what the console displays. Neither of these is something to discover during a working fire, and both have definite answers that your console vendor and your system administrator can give you.

The alias is the weak link that nobody budgets for. The console shows what the system’s subscriber database says that radio ID is, so if radio 1147 is listed as Engine 4 and it has actually been in a battalion chief’s pocket for eight months, the emergency display is worse than no information because it sends people to the wrong place with confidence. Agencies that issue radios to individuals and agencies that assign them to apparatus both have to reconcile the alias list against reality on a schedule, and the reconciliation is a records task that quietly protects the one transmission that matters most. Everything the console handles also lands on the logging recorder, so the emergency event, the acknowledgment, the voice traffic and the CAD entries should all carry synchronized time, which is what makes an honest reconstruction possible afterward.

Channel management in the first two minutes

The instant a mayday is acknowledged, the tactical channel has to become a rescue channel occupied by the incident commander, the distressed member, the rapid intervention crew, and the company nearest to the problem. Everyone else holds traffic. In practice, holding traffic does not happen on its own, because the crews still fighting the fire have real needs and will key up about them unless command states plainly that the channel is restricted and dispatch backs that up. This is one of the few places where a dispatcher stepping on a transmission to enforce channel discipline is the right call.

Published practice divides on how to split the incident, and it is worth knowing both arguments. One approach moves the mayday and the rescue effort to a separate channel and leaves ongoing fire operations on the original tactical. The other keeps the mayday exactly where it was declared and moves everything else to a second tactical channel. Most of the fire service instruction I have seen over the last twenty years favors the second, and the reasoning is mechanical rather than philosophical: a firefighter who is disoriented, low on air, wearing structural gloves and unable to see the display of a radio worn on a strap is not reliably going to change channels, and a member who mis-selects while trying to comply has removed himself from the only conversation that can save him. Whichever way your agency decides, write the decision down, because a fireground where half the officers learned one convention and half learned the other will split into two incidents.

Trunked systems add a wrinkle that is worth testing rather than assuming. The emergency state is associated with the talkgroup on which it was declared, and what happens to that state when the radio is turned to a different talkgroup depends on the system and the codeplug. In some configurations the emergency follows and is re-declared, in others the console indication stays behind on the original talkgroup while the user is somewhere else, and there is no way to know which applies to you except to try it on a test radio with a dispatcher watching the screen. The same caution applies to patches created on the fly, which introduce audio delay and can complicate signaling, so a patch built during a mayday is not a free action.

Personnel accountability reports around a mayday

A personnel accountability report is a poll in which the incident commander confirms that every assigned member is accounted for, conducted through supervisors rather than by calling individual firefighters. Standard triggers include the declaration of a mayday, any sudden change in conditions such as a collapse or a flashover, a change from offensive to defensive strategy, completion of the primary search or knockdown, and elapsed time benchmarks that many departments set at ten or twenty minute intervals. The poll after a mayday answers the single question command cannot afford to guess at, which is whether one member is in trouble or whether an entire company has gone silent.

The mechanics have to be designed for the channel congestion that a mayday creates. Polling fourteen companies one at a time on the same channel the rescue is running on will consume the airtime the rapid intervention crew needs, so the workable arrangement conducts the PAR on the second channel, or through division and group supervisors who report a single number for everyone under them, or face to face at the accountability location where the passports or tags are collected. Reporting by riding position count rather than by name keeps each transmission to a few seconds, and a supervisor who cannot account for someone reports that immediately instead of waiting his turn in the poll.

Electronic accountability, whether it is tag readers, telemetry from the SCBA, or personnel tracking built into a records system, is a useful supplement and a poor substitute. It tells you where a device was last seen, which is not the same as a human being confirming that he has laid eyes on his people. Departments that rely on the screen tend to discover on the bad day that a member handed his tag to someone else, or that the reader lost the last two entries, and the poll is what catches that. The PAR also has a second function that gets overlooked, which is that it forces every supervisor on the fireground to physically locate his crew in the middle of an event that has just changed, and the act of doing that finds problems that nobody had reported yet.

Why crews hesitate, and what the record says about it

The delay between the moment a firefighter is in trouble and the moment he says so is the most studied and least solved part of this whole subject. Burton Clark, who spent a long career as an instructor at the National Fire Academy and wrote extensively on the problem, argued that firefighters fail to call the mayday because the fire service has never trained the call to the level of an automatic response, and that the skill decays because it is almost never practiced under realistic conditions. That framing has held up. A firefighter performs a hose stretch hundreds of times in a career and declares a mayday for real perhaps once or never, so the behavior competes with pride, with the belief that the problem is thirty seconds from solving itself, and with genuine ambiguity about what qualifies.

Two bodies of work are worth putting in front of your members. After the March 2001 supermarket fire in Phoenix in which Firefighter Bret Tarver died, the Phoenix Fire Department ran a large series of rapid intervention drills and published what it found, and the numbers that circulate most widely from that work are that removing one downed firefighter took roughly a dozen rescuers and something on the order of twenty minutes, with rapid intervention personnel themselves getting into trouble at a rate nobody had expected. I would go to Phoenix’s own published report for the exact figures and the conditions they were measured under rather than trust the versions that get repeated in trade articles. The other is Project Mayday, the data collection effort led by Don Abbott, which gathers mayday reports submitted voluntarily by departments across North America and has consistently reported that a large share of maydays are resolved by the member’s own crew or by self-rescue rather than by the assigned rapid intervention crew. That dataset depends on departments choosing to submit, which is a real limitation and one the project itself acknowledges, so treat it as a large collection of self-reported cases rather than a census.

The practical countermeasure is to remove judgment from the decision by writing objective triggers into the SOP, so that a member is not evaluating his own performance while short of air. Common triggers in published departmental policies include being disoriented and unable to find an exit, becoming trapped or entangled and not free within a short stated interval such as thirty seconds, falling through a floor or roof, losing contact with the crew and the hoseline at the same time, having a low air alarm activate while still inside and not at a known exit, and a PASS device activating with no response. When the trigger is a condition rather than a feeling, the argument with yourself is shorter. The other half is repetition in realistic conditions, which means a blacked-out mask and a drill run on the talkgroup crews actually work from, with a dispatcher answering at a real console, because the difference between saying the words in a classroom and saying them while breathing hard is the whole problem.

Cancelling the mayday and cleaning up the record

A mayday ends when the incident commander says it ends, after the member is physically accounted for and a PAR confirms that nobody else is missing. The member himself does not cancel it, and neither does the officer who declared it, because the commander is the only person with the whole picture and the self-rescued firefighter who transmits that he is fine is frequently standing outside while somebody else is still unaccounted for. The cancellation goes out in plain language on the channel, with the time noted, and command then decides whether the incident returns to the original channel assignment or stays split.

The console side has to be closed out as well. The emergency state for that radio ID has to be cleared, by dispatch under most sensible policies, and the clearing should be logged with a time. Agencies that let field users clear their own emergencies tend to end up with an incomplete record and with radios sitting in an active emergency state for hours because nobody noticed. Whoever owns the console needs a standing instruction covering who clears, when, and what gets written down.

Accidental activations are the part nobody wants to handle, and handling them badly is how a department teaches itself to ignore the button. The correct posture is that every activation is treated as real until a voice confirms otherwise, and the confirmation is a direct query to that unit rather than an assumption based on the fact that the fireground sounds calm. At the same time, somebody should be counting them. If your QA or communications officer pulls twelve months of emergency activations and finds that most of them came from three radios carried by members who hang them on a seat belt buckle, that is a mounting problem or a button hold time problem with a cheap fix, and fixing it protects the credibility of every future activation. The same review should pull the audio and CAD timeline from any real mayday and walk it through with the crews involved, measuring the interval from the first indication of trouble to the declaration, from the declaration to the acknowledgment, and from the acknowledgment to the rapid intervention crew’s entry.

What to do at your agency

• Have your radio system administrator take one spare portable, press the emergency button on every fireground talkgroup in the codeplug with a dispatcher watching the console, and document on one page whether the radio sends an alarm, a call or both, whether there is a hot mic and how long it runs, whether the radio reverts to a different talkgroup, and whether the emergency state follows the radio when the user changes talkgroups.
• Ask your dispatch center manager in writing which console positions receive the audible and visual emergency indication for your fireground talkgroups when those talkgroups are not currently selected at the position, and get the answer in a document you can keep.
• Have your communications officer reconcile the subscriber alias list against the current radio assignment roster this month, and correct every entry where the alias no longer matches who or what is carrying that radio.
• Put one item on the agenda of the next officers’ meeting that already occurs: decide and record in a single paragraph in the existing fireground SOP whether the mayday stays on the original tactical channel while other operations move, or the reverse, and which channel the PAR is conducted on.
• Have the training officer run one drill this quarter in which the mayday is declared on the real talkgroup to the real dispatcher with a blacked-out mask, and in which the declaration is made by a company officer for a missing member rather than by the victim.
• Have your QA or records officer pull the last twelve months of emergency button activations from the system logs, count them, identify any radio or member responsible for repeated accidental activations, and fix the carry method or the button hold time rather than accepting the noise.
• Verify with your SCBA and PPE officer that the emergency button on the radio as actually carried, in the pocket or on the strap your members use, can be found and pressed with a structural glove on, and change the carry method where it cannot.

Takeaways

• A mayday means a firefighter is in distress and emergency traffic means a hazard threatens everyone working, and an agency that blurs the two words will lose minutes sorting out which one it has.
• The declaration is the word three times, the identifier, and then a report containing location, identity and problem, with location being the element most often dropped and the one the rapid intervention crew cannot work without.
• The orange button is a programmed function rather than a guaranteed behavior, and emergency alarm, emergency call, hot mic duration, silent operation, hold time and emergency revert are all codeplug choices your agency either made deliberately or inherited by accident.
• Emergency revert can pull a distressed firefighter off the talkgroup his officer and his commander are monitoring, which is defensible in some law enforcement fleets and dangerous on a fireground.
• On a conventional analog system the emergency button frequently does nothing at all unless inband signaling is programmed and dispatch has a decoder watching for it.
• The person in trouble should never be ordered to change channels, because operating a channel selector in zero visibility with gloves on is a single point of failure in the worst possible place.
• Personnel accountability reports after a mayday should run through supervisors on a second channel or face to face, reporting counts rather than names, so that the rescue channel stays available.
• Hesitation is a training problem, and the fixes that work are objective triggers written into the SOP so the member is not judging himself, plus repetition under realistic conditions with the actual radio and the actual dispatcher.
• Only the incident commander cancels a mayday, only after a PAR confirms everyone is accounted for, and the console emergency state has to be cleared and logged so the record of what happened survives the night.