Walk into any firehouse in the five boroughs—from the quiet reaches of Tottenville to the chaotic intersections of the South Bronx—and you’ll see a clipboard or a digital screen. It’s not just a schedule. It’s the tally. To an outsider, the "Runs and Workers" report issued by the FDNY every year looks like a dry spreadsheet of numbers and company identifiers. But to a New York City firefighter, these stats are everything. They are the metric of sweat, the proof of danger, and the primary data point used to argue for more resources or, sometimes, to justify closing a firehouse door for good.
The term FDNY runs and workers basically refers to the statistical breakdown of how many times a specific unit leaves the floor (a run) and how many times they actually hook up to a hydrant or stretch a line (a worker).
It sounds simple. It isn't.
What People Get Wrong About FDNY Runs and Workers
Most folks think a "run" is a fire. I wish. In reality, a run is any time the bells go off and the rig pulls out of the bay. It could be a 10-75 (a working fire), sure, but it’s much more likely to be a medical emergency, a stuck elevator, a false alarm triggered by burnt toast, or a "water leak" that turns out to be a burst pipe in a basement.
The "worker" part is where the prestige—and the exhaustion—lives. A "worker" is generally defined as an incident where the unit is actually put to work. For an engine company, that means putting water on fire. For a truck (ladder) company, it means venting, entering, and searching.
You’ll often see Engine 75 in the Bronx or Engine 290 in Brooklyn sitting near the top of these lists. Why? Because the density of those neighborhoods combined with the age of the building stock creates a perfect storm for constant activity. When people talk about FDNY runs and workers, they are often looking for the "busiest" house. But "busy" is a relative term. A company might have 5,000 runs but only a fraction of those are "workers." Conversely, a squad in a different borough might have fewer total runs but a higher percentage of serious fires.
The Politics of the Numbers
The FDNY is a massive bureaucracy. It’s a city agency with a budget that is constantly under the microscope of City Hall. This is where the FDNY runs and workers data becomes a political weapon.
Back in the 1970s—the "War Years"—these numbers were staggering. Firefighters were jumping from one working fire to the next, sometimes never returning to the firehouse for an entire shift. Today, while the total number of "runs" has actually increased due to the department taking on more medical calls (CFR-D), the number of actual structural fires has generally trended downward over the decades thanks to better building codes and smoke detectors.
However, don't let the "less fire" narrative fool you. The work has changed, but it hasn't slowed down.
If a company shows low "runs and workers" numbers over several years, they end up on a list. Not a good list. They end up on the "maybe we can close this engine to save $5 million" list. This happened famously during the Bloomberg administration and has been a recurring threat in various budget cycles. Neighborhoods fight back. They point to the "response time," which is the third leg of the runs and workers stool. If you close an engine with low "workers," the next closest engine has to travel further, and in New York traffic, three minutes is the difference between a room-and-contents fire and a total loss of life.
Engines vs. Trucks: A Different Kind of Tired
It’s worth noting that engines and ladders view these stats through different lenses.
- Engines are the workhorses of the medical system. If you call 911 because your grandma is having chest pains, an FDNY engine is often the first on the scene because they are already patrolling or stationed closer than the nearest ambulance. This inflates their "runs" massively.
- Ladder companies (the "trucks") don't go on every medical call. Their runs are often lower, but when they do go out, it’s usually for something mechanical or structural.
The FDNY runs and workers reports usually separate these, and if you look at the 2023 or 2024 data, you’ll see the gap. A busy engine might hit 6,000 runs. A busy truck might hit 3,500. Both crews are beat by the end of a 24-hour tour, but for different reasons.
The Physical Toll of Being "Top of the List"
There is a certain pride in being the busiest house in the city. You’ll see it on the house patches and the t-shirts. "The Big House," "The Tin House," "The Fire Factory." But there’s a dark side to high FDNY runs and workers stats.
Sleep deprivation is a silent killer in the department. When a company is "catching" (going to fires) every night, the long-term health effects are real. We’re talking about cardiovascular stress, increased risk of cancer from carcinogen exposure that isn't properly washed off because the bells go off again, and mental burnout.
The stats don't show the "near misses." They don't show the firefighter who almost fell through a weakened floor in a private dwelling in Queens. They just show a "1" in the worker column.
Understanding the "10-75" and Beyond
To truly grasp FDNY runs and workers, you have to understand the codes that trigger the stats.
- 10-75: This is the signal for a working fire. When this is transmitted, the "worker" count for the assigned units begins.
- All Hands: This means all units initially dispatched are being used.
- Second, Third, Fourth Alarm: This is where the numbers swell. A 5th alarm fire in a warehouse in Brooklyn will put "workers" on the boards for dozens of companies across multiple boroughs.
Interestingly, "total runs" are often driven by "10-92" calls—malfunctioning alarms. In a city of 8 million people and millions of old sensors, the FDNY spends a massive amount of time chasing ghosts. It’s frustrating for the members, but it’s a vital part of the "runs" data because it proves the unit was unavailable for other calls during that time.
Data Transparency and Where to Find It
If you’re a buff or a researcher, you aren't just looking for a summary. You want the raw stuff. The FDNY used to be a bit more guarded with this data, but in the age of Open Data NYC, you can find annual reports that break down every single company.
You’ll find these reports on the official NYC.gov FDNY page, usually under the "Citywide Performance Reporting" or "Annual Reports" section. Independent sites like NYC Fire Wire or various community forums also track these religiously, often posting monthly breakdowns of which engines "worked" the most.
Why do people care so much? Because it’s the scoreboard of the city. For a kid growing up in Brooklyn, seeing that the local engine is the "busiest in the city" is a point of neighborhood pride. For the city council member, it’s the data they need to demand a new firehouse.
How Modern Tech is Changing the Stats
We are seeing a shift. GPS tracking and "Starfire" (the FDNY’s dispatch system) are getting better at "closest unit dispatching." In the old days, you stayed in your "box." Now, the computer knows exactly where every rig is. If Engine 231 is out on a medical call, the system automatically adjusts the "runs" for the surrounding companies.
This has actually leveled out the FDNY runs and workers numbers slightly. You don't see the massive outliers as much as you did thirty years ago, because the workload is being distributed more efficiently by the algorithms. But algorithms don't fight fires. People do.
Honestly, the numbers only tell half the story. You can have a "worker" that consists of blowing out a small grease fire in five minutes. Or you can have a "worker" that involves a six-hour slog through a freezing taxpayer building in the middle of January. Both count as "1" on the spreadsheet.
Actionable Insights for Using These Stats
If you are looking at FDNY runs and workers data for real estate, safety research, or just out of interest, keep these points in mind:
- Look for the Ratio: Don't just look at total runs. Look at the ratio of runs to workers. A company with 4,000 runs and 800 workers is seeing a lot more "fire duty" than one with 6,000 runs and 200 workers.
- Check the "CFR-D" Stats: If you want to know how much medical work a house does, look for the CFR-D (Certified First Responder, Defibrillator) run count. This tells you about the neighborhood’s health needs more than its fire risk.
- Understand Seasonality: Numbers spike in the winter. Space heaters, old boilers working overtime, and closed-up windows lead to more fires and more carbon monoxide calls.
- Contextualize Neighborhood Growth: If a neighborhood like Long Island City or Downtown Brooklyn has a massive influx of high-rises, the "runs" will skyrocket due to elevator rescues and alarm malfunctions, even if the "workers" (fires) stay low.
The FDNY runs and workers report is the heartbeat of the department. It’s a messy, complicated, and deeply human set of numbers that tells us where the city is hurting and where the help is coming from.
To stay truly informed, check the FDNY Vital Statistics reports annually. They provide a granular look at response times alongside these run totals, offering the most complete picture of emergency services in New York. If you are advocating for fire safety in your own community, use the "workers" data to show the actual fire load your local station handles—it's much more persuasive to local boards than "runs" alone. Look at the three-year trend, not just a single year's spike, to see the real story of a neighborhood's safety profile.