dataset · Philadelphia Fire Department · ArcGIS

Philadelphia Fire Department incidents

Every PFD dispatch since 2024-01-01 — false alarms, EMS assists, hazmat conditions, and the ~14% that are actual fires. Queried directly against the city's stat360_fire_incidents ArcGIS Feature Service through our Cloudflare worker proxy.

data through 2026-01-31 · 128,491 rows

incidents by category · since 2024

What PFD actually responds to

  1. False Alarm & False Call
    61K
  2. Good Intent Call
    23K
  3. Fire
    18K
  4. Hazardous Condition (No Fire)
    11K
  5. Service Call
    5.8K
  6. Unclassified
    4.9K
  7. Rescue & Emergency Medical Service Incident
    3.9K
  8. Special Incident Type
    1.0K
  9. Overpressure Rupture, Explosion, Overheat (No Fire)
    265
  10. Severe Weather & Natural Disaster
    35
0 61K max

For the narrated walk-through of these categories — by zip, by property type, plus the 63 stations that respond — see the Where Philly burns scrolly story.

Data we'd like to find

Fields and feeds that would unlock new analyses on this dataset. Mirror of the topic page list, scoped to PFD-related gaps only.

PFD apparatus dispatched

PFD · Open

The fire-incident layer publishes which incident type and where, but not which engine, ladder, medic, or specialty rig responded.

Would unlock "busiest engine," "busiest ladder," and per-rig run-volume comparisons across stations.

Where to look

  • OpenDataPhilly — Search for an "incident apparatus" or "unit dispatch" feed alongside the existing stat360_fire_incidents layer.
  • PFD FOIL request — Right-to-Know Act request for unit-level dispatch logs.
  • NFIRS extracts — The federal NFIRS database carries per-unit fields; PFD submits to it.

PFD first-due station per incident

PFD · Open

Incidents lack a column naming the station that responded; we approximate via a centroid-to-nearest-station spatial join.

Replacing the proxy with the published assignment would give exact per-station run counts and let us show overrun patterns when first-due is unavailable.

Where to look

  • PFD response-zone shapefile — A station response-area polygon set, if published, would let us assign by geometry rather than nearest-point.
  • PFD FOIL request — Same vehicle as above; ask for response-zone or unit-assignment data.

EMS-only dispatch feed

EMS · Investigating

PFD’s `stat360_fire_incidents` mixes fire and EMS via an `incident_type_category` field; an EMS-only layer with finer call-type detail (e.g. "Medical Emergency", "MVA", "Cardiac") doesn’t appear in the published catalog.

Would let the medic-unit-load story drill into call-type mix per zip and per medic unit instead of treating "Rescue & EMS" as a single category.

Where to look

  • PFD EMS division — The bureau publishes annual reports with breakdowns; ask whether the underlying feed is on ArcGIS.
  • OpenDataPhilly — Periodically check for new EMS-tagged feeds.

Narcan administrations (per-incident or aggregated)

OPIOID · Open

Overdose deaths are published; the volume of Narcan administrations (not kits distributed) per incident or per zip is not in the current pipeline.

Would let the Narcan story show "saves" alongside losses — the response side of the same crisis.

Where to look

Response time distributions by incident type

PFD · Open

Neither the fire nor the (not yet wired) EMS feed publishes per-incident response time — only annual averages in PFD’s public reports.

Would unlock "where does PFD arrive fast vs. slow" and let us compare against published NFPA targets per call type.

Where to look

  • PFD annual report PDFs — Aggregate only; would need extraction.
  • PFD FOIL request — Per-incident dispatch / on-scene timestamps.