PJM · Ohio · Public-record retrospective
Marysville-Flatlick 765 kV: interconnection queue history
Three of nine requests withdrew; six are still in the queue.
GridVision AI ResearchUpdated
Nine interconnection requests since 2016: 3 withdrew and 6 remain active.
- Built
- 0
- Withdrawn
- 3
- Still in queue
- 6
The queue record
Every interconnection request the dataset records at this point of interconnection, in filing order.
| Requested | Project | Technology | Capacity | Outcome |
|---|---|---|---|---|
| 2016-04-12 | (unnamed) | Gas | 1200 MW | Withdrawn2016-10-04 |
| 2016-10-20 | (unnamed) | Gas | 1277 MW | Withdrawn2017-02-23 |
| 2020-08-31 | Oak Run Solar Project | Solar | 400 MW | Still in queue |
| 2020-08-31 | Oak Run Solar Project | Solar | 400 MW | Still in queue |
| 2021-01-29 | (unnamed) | Solar | 400 MW | Withdrawn2024-12-18 |
| 2023-03-02 | (unnamed) | Solar | 83.5 MW | Still in queue |
| 2023-03-02 | (unnamed) | Solar | 100 MW | Still in queue |
| 2023-03-02 | (unnamed) | Solar | 100 MW | Still in queue |
| 2025-03-01 | (unnamed) | Solar | 200 MW | Still in queue |
What the record shows
- 2,877 MW of the 4,160 MW filed here withdrew.
- The largest request filed here, 1,277 MW (gas), withdrew 0.3 years after filing.
- Three requests were filed on 2023-03-02; all of them remain active.
- Two of the 3 withdrawals came within a year of filing.
- By technology, the requests here were solar 7, gas 2.
- The longest-standing active request here was filed on 2020-08-31.
- The dataset records this point of interconnection under two spellings, which are combined here.
What a decision record would have to make explicit
- None of the resolved requests at this node reached operation, and the public record does not say why.
- Six requests are unresolved, so the outcome counts at this node can still change.
- The dataset records outcomes and dates, not reasons, so no cause is attributed to any outcome here.
What this does and does not show
This is a reading of a public dataset, not a customer case study: no engagement, customer or client is involved. The dataset records outcomes — what was built, what withdrew, and when — but not why any project withdrew, so no cause is attributed here. Nothing on this page claims GridVision predicted, influenced or would have changed any outcome, and a pattern at one point of interconnection does not generalise to another.
Source: Lawrence Berkeley National Laboratory, Queued Up: 2026 Edition — project-level interconnection queue dataset. Interconnection requests through year-end 2025. Used under CC BY 4.0; attribution to Lawrence Berkeley National Laboratory and GridTracker.
Related points of interconnection
- PJM · OhioBuckskin 69 kV6 requests · 1 built · 5 withdrawn · 0 still in queueRead the record
- PJM · OhioTait 69 kV5 requests · 4 built · 1 withdrawn · 0 still in queueRead the record
- PJM · OhioMarysville-Sorenson 765 kV9 requests · 0 built · 7 withdrawn · 2 still in queueRead the record
- PJM · PennsylvaniaHatfield 500 kV6 requests · 3 built · 3 withdrawn · 0 still in queueRead the record
How the PJM process works today: PJM interconnection queue. Comparing candidate nodes for a project? Read how to choose a point of interconnection.
