Skip to content
GridVision AI

PJM · Pennsylvania · Public-record retrospective

Montour 230 kV: interconnection queue history

647 MW filed. 7 MW built.

GridVision AI ResearchUpdated

Thirteen interconnection requests since 2000: 1 reached commercial operation, 7 withdrew, and 5 remain active.

Built
1
Withdrawn
7
Still in queue
5

The queue record

Every interconnection request the dataset records at this point of interconnection, in filing order.

Interconnection requests recorded at this point of interconnection, with request date, capacity and outcome.
RequestedProjectTechnologyCapacityOutcome
2000-10-06Montour #2Coal7 MWBuilt2002-05-06 · 1.6 yrs
2018-09-24(unnamed)Solar100 MWWithdrawn2018-09-30
2019-03-14Montour Solar OneSolar101.6 MWWithdrawn2025-07-25
2019-09-30(unnamed)Solar150 MWWithdrawn2023-10-16
2020-03-30(unnamed)Solar20 MWWithdrawn2025-03-28
2020-03-30(unnamed)Solar20 MWWithdrawn2025-03-28
2020-03-30(unnamed)Solar50 MWWithdrawn2025-03-28
2020-03-30(unnamed)Solar50 MWWithdrawn2025-03-28
2023-03-10(unnamed)Solar14.5 MWStill in queue
2023-03-10(unnamed)Solar29 MWStill in queue
2023-03-10(unnamed)Solar29.464 MWStill in queue
2023-03-10(unnamed)Solar34.8 MWStill in queue
2023-03-10(unnamed)Solar40.6 MWStill in queue

What the record shows

  • 492 MW of the 647 MW filed here withdrew, and 7 MW reached commercial operation.
  • The one request that reached operation took 1.6 years from request to commercial operation.
  • The largest request filed here, 150 MW (solar), withdrew 4.0 years after filing.
  • Five requests were filed on 2023-03-10; all of them remain active.
  • One of the 7 withdrawals came within a year of filing.
  • By technology, the requests here were solar 12, coal 1.
  • The longest-standing active request here was filed on 2023-03-10.
  • The dataset records this point of interconnection under two spellings, which are combined here.

What a decision record would have to make explicit

  • What separated the requests that reached operation from those that withdrew, such as study results, upgrade assignments or site conditions, is not in the public queue record, so a decision record here would have to carry it as an unknown.
  • Five 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

How the PJM process works today: PJM interconnection queue. Comparing candidate nodes for a project? Read how to choose a point of interconnection.

Bring One Live DecisionOther retrospectives