Transmission Outage Tickets

PJM's Transmission Facilities Outage List (TFOL): one row per outaged facility per outage ticket, covering active, scheduled, and planned transmission outages across the footprint.

Outages & Grid Events data

Download data

Native record

event_time x ticket x facility

5-minute source, polled every 15 minutes publication cadence

Evidence

Observed market data

Published observations from the named source

Time basis

Point-in-time records

UTC · event_time

Overview

Each row carries the zone, facility type, station, voltage, equipment, status, outage type, cause, reschedule count, first scheduled start, submission time, and PJM's at-risk flag. event_time is the outage start and end_time its scheduled end. PJM republishes the whole list about every five minutes, and published_at is the report's own generation stamp. A reschedule writes a new row under the new start time, so a ticket's current state is its row with the newest published_at, not the newest row or the latest start. status separates a request (Received) from a commitment (Approved, Active). PJM withholds market-sensitive tickets before publication, so a facility missing from this list is not proof that it is in service. A scheduled outage does not by itself establish that a constraint will bind or that prices will separate. Source: PJM eDART.

Query contract

Preserve one canonical row per (event_time, ticket, facility) before aggregating.

Analysis rules

Group only after preserving the declared grain: event_time, ticket, facility.

Schema24

Column

Type

event_timeDateTime64(6, 'UTC')

end_timeDateTime64(6, 'UTC')

published_atDateTime64(6, 'UTC')

ticketLowCardinality(String)

zoneLowCardinality(String)

facility_typeLowCardinality(String)

stationLowCardinality(String)

voltage_kvNullable(Float64)

equipmentString

facilityString

statusLowCardinality(String)

prev_statusLowCardinality(String)

outage_typeLowCardinality(String)

causeString

open_closedLowCardinality(String)

recallLowCardinality(String)

rtepBool

at_riskBool

on_timeBool

reschedule_countInt32

first_startNullable(DateTime64(6, 'UTC'))

submitted_atNullable(DateTime64(6, 'UTC'))

last_evaluatedNullable(DateTime64(6, 'UTC'))

ingested_atDateTime64(6, 'UTC')

Sample data

event_time	end_time	published_at	ticket	zone	facility_type	station	voltage_kv	equipment	facility	status	prev_status	outage_type	cause	open_closed	recall	rtep	at_risk	on_time	first_start	submitted_at	last_evaluated	ingested_at
2059-03-01 14:30:00.000000	2059-06-15 20:00:00.000000	2026-09-19 01:48:29.000000	987691	DOM-C	LINE	NANNA4	500	NANNA4 -MIDLOTH 576A	LINE NANNA4 500 KV NANNA4 -MIDLOTH 576A	Received	Submitted	Continuous	OUTAGE REQUEST RECEIVED BY PJM PLANNING PERSONNEL; . . . . outage type . . .		Duration	true	false	true	2059-03-01 14:30:00.000000	2023-02-07 15:00:00.000000	∅	2026-09-19 01:52:36.992791
2059-03-01 14:30:00.000000	2059-06-15 20:00:00.000000	2026-09-19 01:48:29.000000	987691	DOM-C	BRKR	NANNA4	500	NANNA4 WT576 CB	BRKR NANNA4 500 KV NANNA4 WT576 CB	Received	Submitted	Continuous	OUTAGE REQUEST RECEIVED BY PJM PLANNING PERSONNEL; . . . . outage type . . .		Duration	true	false	true	2059-03-01 14:30:00.000000	2023-02-07 15:00:00.000000	∅	2026-09-19 01:52:36.992791
2059-03-01 14:30:00.000000	2059-06-15 20:00:00.000000	2026-09-19 01:48:29.000000	987691	DOM-C	BRKR	NANNA4	500	NANNA4 57602 CB	BRKR NANNA4 500 KV NANNA4 57602 CB	Received	Submitted	Continuous	OUTAGE REQUEST RECEIVED BY PJM PLANNING PERSONNEL; . . . . outage type . . .	O	Duration	true	false	true	2059-03-01 14:30:00.000000	2023-02-07 15:00:00.000000	∅	2026-09-19 01:52:36.992791
2059-03-01 14:30:00.000000	2059-06-15 20:00:00.000000	2026-09-19 01:48:29.000000	987691	DOM-C	BRKR	MIDLOTH	500	MIDLOTH H6T576 CB	BRKR MIDLOTH 500 KV MIDLOTH H6T576 CB	Received	Submitted	Continuous	Repair/Replace: Conductor; OUTAGE REQUEST RECEIVED BY PJM PLANNING PERSONNEL; . . . . outage type . . .		Duration	true	false	true	2059-03-01 14:30:00.000000	2023-02-07 15:00:00.000000	∅	2026-09-19 01:52:36.992791
2059-03-01 14:30:00.000000	2059-06-15 20:00:00.000000	2026-09-19 01:48:29.000000	987691	DOM-C	BRKR	MIDLOTH	500	MIDLOTH 563T576 CB	BRKR MIDLOTH 500 KV MIDLOTH 563T576 CB	Received	Submitted	Continuous	OUTAGE REQUEST RECEIVED BY PJM PLANNING PERSONNEL; . . . . outage type . . .		Duration	true	false	true	2059-03-01 14:30:00.000000	2023-02-07 15:00:00.000000	∅	2026-09-19 01:52:36.992791

Coverage

8.5% complete13,798 gap days1,280 days with data

Show coverage history

Coverage: 8.5%Days with data: 1,280Gaps: 13,798

2059

2058

2057

2056

2055

2054

2053

2052

2051

2050

2049

2048

2047

2046

2045

2044

2043

2042

2041

2040

2039

2038

2037

2036

2035

2034

2033

2032

2031

2030

2029

2028

2027

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

gaplessmore

Related outages & grid events data

Related outages & grid events data
Dataset	Description
Generation Outages by TypePJM · daily	PJM's daily generator-outage outlook by report date, target forecast date, and region. Each row separates total, planned, maintenance, and forced outage capacity in MW for PJM RTO, Western, or Mid Atlantic - Dominion. This is generation availability evidence from PJM Market Data, not distribution-customer outage data. Source: PJM Market Data.
AlertsISONE · ISO-NE source publication	ISO-NE's published Alerts source feed. This catalog page exposes the physical schema, coverage, and latest source rows without inventing a normalized grain for publisher-shaped snapshot fields. Use the documented key and event time when comparing revisions or vintages.
Curtailed Non-Operational GeneratorsCAISO · daily	CAISO's prior-trade-date report of planned and forced generator curtailments. publish_time is the report vintage; curtailment start and end are the operating interval.
Customer Outages by CountyODIN · 10-minute snapshot	Live county-level customer outage snapshots from ORNL/DOE's ODIN public county map API. Ask the Grid queries the nationwide grid='us' archive and derives each live product map from its exact state-FIPS scope, so every supported grid uses the same accumulated history. Each row is an active county outage at that snapshot with county FIPS, state FIPS, affected meters, contributing utility rows, and the ODIN county polygon. Missing county rows at a snapshot mean zero or cleared public ODIN outage, not stale carry-forward. This is distribution/customer outage data, not ISO generation or resource outage data.