throbber

`FEDERAL ENERGY REGULATORY COMMISSION
`WASHINGTON, D. C. 20426
`September 19, 2025
`
`OFFICE OF ENERGY PROJECTS
`
`Project No. 15353-002 – Oklahoma
`Oologah Lake Dam Hydroelectric Project
`Hybrid Renewables LLC
`
`VIA FERC Service
`
`Tafweez E. Chauhan
`Managing Director
`Hybrid Renewables LLC
`1530 Key Blvd.,
`Suite 1104, Arlington, Virginia 22209
`
`Reference: Authorization to Use the Traditional Licensing Process
`
`Dear Mr. Chauhan:
`
`On June 2, 2025, Hybrid Renewables LLC (Hybrid Renewables), filed a Notice of
`Intent (NOI) to file a license application to construct and operate the proposed
`40-megawatt (MW)
` Oologah Lake Dam Hydroelectric Project, located on the Verdigris
`River in Oklahoma. Hybrid Renewables also filed a pre-application document (PAD) for
`the proposed project and requested to use the traditional licensing process (TLP) for the
`proposed project.
`
`On June 5, 2025, Hybrid Renewables filed documentation with the Commission
`showing that it published a notice of its request to use the TLP in the June 5, 2025 edition
`of the Oologah Lake Leader. The notice contained the information required in section
`5.3(d)(2) of the Commission’s regulations, including a statement requesting that
`comments on the request to use the TLP be filed with the Commission by July 5, 2025.
`
`On July 3, 2025, the United States Army Corps of Engineers (USACE) filed
`comments on the PAD indicating the need for more stakeholder engagement and certain
`studies but did not object to the use of TLP. On August 4, 2025, Hybrid Renewables
`filed a revised NOI and PAD,1 acknowledging the need for additional studies identified
`by the USACE and agreeing to more proactive engagement with stakeholders.
`
`1 Hybrid Renewables filed the revised NOI and PAD because Commission staff
`
`
`
`
`
`
`
`
`Project No. 15353-002 -2-
`
`Staff have reviewed the revised PAD and information provided by Hybrid
`Renewables and finds that, although there could be complexity associated with some
`resource issues, the TLP is expected to be the most cost-efficient licensing process for the
`proposed project, interested resource agencies, and other stakeholders. The TLP also
`provides more pre-filing flexibility in terms of the timing of the process steps, including
`study plan development. Moreover, there is a reasonable amount of information
`available regarding resources associated with the project, suggesting a minimal level of
`anticipated controversy associated with study planning during the pre-filing period.
`Therefore, the TLP process is deemed appropriate for developing the license application.
`Hybrid Renewables’ request to use the TLP is granted.
`
`Section 4.38 of the Commission’s regulations describes the pre-filing steps that
`need to be completed when preparing an application for a hydropower license under the
`TLP, including consultation and conducting necessary studies [18 C.F.R. § 4.38(a) -(h)].
`Specific steps that will need to be carried out during pre-filing consultation include an
`initial joint agency/public meeting and site visit [§ 4.38(b)(3)]; an opportunity for
`participants to request studies [§ 4.38(b)(5)]; preparation and participant review of a draft
`application [§ 4.38(c)(4)]; and a meeting to resolve any disputes on the draft application
`[§ 4.38(c)(6)]. Please note that the initial joint agency/public meeting is required to be
`held no sooner than 30 days, nor later than 60 days, from the date of this letter
`[§ 4.38(b)(3)(ii)].
`
`If you have any questions, please contact Kristine Sillett at (202) 502-6575, or via
`email at
`kristine.sillett@ferc.gov.
`
` Sincerely,
`
`
`
`
`Nicholas Jayjack
` Director
` Division of Hydropower Licensing
`
`
`rejected the original filing for lack of documentation of consultation and demonstrated
`due diligence in preparing the PAD. Hybrid Renewables’ revised filings corrected the
`deficiencies.
`
`
`
`
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket