AEP Baku Gavin 765 kV Route Filed for Ohio Siting Review
AEP Ohio Transmission Company has placed a proposed 765 kV transmission route into Ohio’s public siting record, giving landowners, agencies, contractors, and local officials a clearer view of where the Baku-Gavin line could be built.
The company’s certificate application describes about 51 miles of new 765 kV transmission line between the proposed Baku substation in Pike County and the existing Gavin substation in Gallia County. The preferred route listed in the filing is 51.3 miles and generally uses a 200-foot right of way, covering about 1,244 acres.
The route is not final. A proposed route in a certificate application remains subject to the Ohio Power Siting Board process, including staff review, public notice, hearings, possible revisions, and a certificate decision.

The filing puts the preferred route and exhibits on the record
The certificate application is the key document now available for review. According to the project materials, the Baku-Gavin proposal would connect a proposed Baku substation in Pike County with the existing Gavin substation in Gallia County.
The application package includes project, route, environmental, and land-use exhibits. These materials matter because they move the discussion from a general project concept to a mapped route with affected areas, right-of-way requirements, and siting details that can be reviewed in the case record.
Item | Detail from the application materials |
Applicant | AEP Ohio Transmission Company |
Project | New 765 kV transmission line |
Connection | Proposed Baku substation to existing Gavin substation |
Counties identified | Pike, Jackson, and Gallia counties |
Preferred route length | 51.3 miles |
General right of way | 200 feet |
Approximate right-of-way area | 1,244 acres |
Siting venue | Ohio Power Siting Board |
Case to watch | 26-0426-EL-BTX |
The company’s project page and overview map provide a public-facing summary of the route. The full application gives the detailed exhibits that siting participants typically use to evaluate route location, land use, environmental considerations, crossings, access, and construction issues.
For firms that work in survey, engineering, land services, access planning, construction, and restoration, this is the point where the project becomes easier to track. The route is now tied to a formal case number and siting milestones rather than only broad planning language.
The proposed corridor crosses three southern Ohio counties
The application identifies affected townships in Pike, Jackson, and Gallia counties. Those counties form the geographic frame for local review, landowner outreach, agency comments, and the field work that may follow if the project advances.
The Baku-Gavin line is part of the transmission system rather than a small distribution rebuild. A 765 kV line is among the highest voltage classes used on the bulk electric system in the United States. That means the siting record will draw close attention to route geometry, right-of-way width, structure locations, land impacts, and access needs.
The preferred route’s stated right of way, generally 200 feet, is also central to how the filing will be read. A corridor at that scale affects more than the centerline. It can involve vegetation clearing, construction mats or temporary workspaces, access roads, structure pads, laydown areas, gates, culverts, property restoration, and long-term maintenance rights.
The application’s approximate 1,244 acres of right of way gives reviewers a measurable footprint. It does not mean every acre would be disturbed in the same way. Some areas may involve full clearing, while others may involve access, restoration, or operational restrictions. Still, the acreage number helps define the scale of the siting case.

The Ohio siting process still controls what happens next
A certificate application does not approve construction by itself. It starts a formal review before the Ohio Power Siting Board.
For this case, the key docket reference is 26-0426-EL-BTX. That case number is the place to watch for staff findings, procedural entries, hearing notices, changes to the route record, and the final certificate decision.
Several types of activity can occur after an application reaches the public record:
Completeness and procedural review
The board process sets the schedule and confirms what materials are in the record.
Staff report
OPSB staff typically reviews the project and publishes findings that address need, route impacts, environmental issues, land use, and recommended conditions.
Public notices and hearings
Notices and hearings give affected parties and local communities a way to follow the case and participate under the board’s procedures.
Possible route changes
The preferred route can be revised during the process if the record supports changes or if the applicant updates the proposal.
Certificate decision
The board decides whether to approve, deny, or approve with conditions.
That sequence is why the route should be read as proposed, not final. The route is now visible in a formal filing, but the siting case still has to run its course.
For landowners and local governments, the next documents may be as important as the application itself. Staff reports and hearing notices often clarify issues that are not fully apparent from a map alone. Those filings can show where concerns have been raised and what conditions may be placed on construction if the project is approved.
The route record creates planning signals for field services
The business significance of the filing is practical. A mapped preferred route gives service providers a corridor to study and a timeline to follow.
Survey, engineering, land, access, construction, and restoration needs tend to become more visible as a transmission project moves through siting. The application does not award that work, and approval is not guaranteed. Still, the public route record helps companies align business development, staffing, equipment planning, and local research with the expected project path.
The most relevant work areas include:
Boundary, topographic, environmental, and construction survey support
Geotechnical investigation and structure site access planning
Civil and transmission engineering coordination
Title review, easement support, and landowner contact processes
Temporary and permanent access road planning
Clearing, matting, erosion control, and laydown area preparation
Construction logistics across multiple counties
Restoration, reseeding, drainage repair, and closeout documentation
The route length also matters for scheduling. A 51.3-mile preferred route across three counties can involve many separate access points, road crossings, landowner constraints, environmental windows, and staging decisions. Even before construction, early field activity can require careful coordination so crews work within permissions and siting limits.
The AEP Baku Gavin 765 kV Route Filed for Ohio Siting Review is especially relevant for teams that monitor major transmission work in the Midwest and Appalachia. Large-voltage transmission projects can create multi-year planning needs, even when the early public milestone is only a siting application.

Maps should be read with the application, not alone
The overview map is useful because it shows the proposed route at a broad level. It helps readers understand the general path between the Baku and Gavin endpoints and the counties involved.
But route maps have limits. They do not always show parcel-level details, environmental constraints, access plans, or the full set of exhibits included in the application. A line on a map can also look simpler than the field conditions it crosses.
The strongest read comes from using the map and application together.
The map can answer:
Where does the preferred route generally run?
Which communities or townships appear near the corridor?
How does the route connect Pike County to Gallia County?
The application can help answer:
What right-of-way width is proposed?
What environmental and land-use exhibits support the route?
What alternatives or route details are part of the case materials?
What construction assumptions are described?
Which areas may need closer review during the OPSB process?
For contractors and consultants, this distinction matters. A map can help identify opportunity areas, but the application record is what supports more serious planning. It provides the details needed to compare route segments, estimate field complexity, and monitor future changes.
The most important filings to watch next
The next meaningful updates will come through the OPSB case record and related project materials. The filing to monitor is case 26-0426-EL-BTX.
The highest-value items to watch are:
Staff report
This will likely be one of the most important public documents after the application. It can summarize staff analysis and recommended certificate conditions.
Hearing notices
Notices indicate when and where formal participation opportunities will occur.
Route revisions
Any change to the preferred route, alternate route, structure assumptions, or access approach can affect landowners and service needs.
Certificate decision
The board’s decision will determine whether the project can move forward and under what conditions.
Updated maps and project page materials
Public-facing project updates can help confirm whether changes in the docket have been translated into new route materials.
This is also the period when local details can surface. Road use, access points, drainage repairs, restoration standards, crop issues, and tree clearing concerns often become more specific as the case record develops.

Source documents now available
The public materials identified for the Baku-Gavin filing include the certificate application, AEP’s project page, and an overview map. These are the core sources for tracking the project at this stage:
The key takeaway is simple: the Baku-Gavin route is now specific enough to study, but not final enough to treat as settled. The application brings the proposed 765 kV corridor into public view, while the Ohio Power Siting Board process will determine what happens next.





Comments