Can you fly a drone over train tracks?

You can fly a drone over train tracks in most of the United States today, because no federal rule closes the airspace above a railway to small unmanned aircraft. That answer surprises operators who have been chased off a bridge by a railroad officer, and it surprises them because the conflict is almost never about the airspace. The FAA controls the sky above the ballast. The railroad controls the ballast, the right of way beside it, and increasingly the state statute that governs both.

This article covers what federal rules do and do not say about railways, the ground level questions that decide whether a flight is lawful, the state laws that filled the federal gap, and the rulemaking now underway that could change the airspace answer. It closes with what a rail contractor should hold on file before flying a corridor.

Federal airspace rules do not single out railways

Part 107 restricts operations by altitude, visual line of sight, airspace class, and proximity to people, and none of those categories names a railway. Flying at two hundred feet along a track in uncontrolled airspace, keeping the aircraft in sight, and staying clear of people is an ordinary operation. Operators sometimes assume a prohibition exists because so many other rail activities are federally regulated, and the assumption survives because railroads discourage flying regardless of what the rule says.

There is one federal wrinkle worth knowing. Congress instructed the FAA in 2016 to create a process letting operators of fixed site facilities petition for restrictions on drone flight nearby, and railroad facilities were named among the eligible categories. That process sat unbuilt for close to a decade. The FAA published a proposal to implement it in May 2026, so the airspace answer above rail infrastructure is live rulemaking rather than settled law, and the position at the time you read this is worth checking.

What the proposal would and would not do

The proposed framework would create two designations, a standard restriction generally capped at four hundred feet above ground and confined to a facility's property boundaries, and a stricter tier for sites with credible security concerns. The proposal is petition based, so no facility receives protection automatically, and eligibility is tied to recognized critical infrastructure sectors. The Federal Register notice for the proposed fixed site restrictions sets out both the statutory background and the eligibility criteria.

The rail industry asked for considerably more than the proposal offers. Its trade association requested restrictions covering roughly 140,000 miles of track together with right of way property extending fifty feet either side, and the FAA indicated it did not regard blanket coverage of that scale as consistent with what Congress directed. The likely landing point is therefore facility specific: yards, bridges, tunnels, and terminals could end up designated, while ordinary running track stays open. Corridor flying would remain lawful; flying over a classification yard might not.

The ground is where the real restrictions live

Most enforcement against drone crews near railways has nothing to do with the airspace and everything to do with where the pilot stood. Railroad right of way is private property, and entering it to launch, land, or spot the aircraft is trespass in every state. Railroad police are commissioned law enforcement officers in most jurisdictions with authority over railway property, which means the person telling a crew to leave is not a security guard with an opinion. Launching from public land beside the corridor changes the analysis entirely.

State law has also moved into the space the federal process left empty. Numerous states passed critical infrastructure statutes that criminalize operating a drone over or near listed facilities, and railways appear on many of those lists. These statutes vary in what they prohibit, whether they require intent, and what defenses exist for authorized inspection work. An operator flying rail corridors across state lines is dealing with a patchwork, and the applicable statute is the one for the state the track runs through rather than the state the company is based in.

What a rail contractor should hold before flying

Contracted rail inspection work is usually lawful, well documented, and uncontroversial, and the paperwork is the reason. The operator holds written authorization from the railway naming the corridor, the dates, and the access arrangements, which converts the trespass question into a permission question and gives the crew something to show a railroad officer who arrives mid flight. Where a state critical infrastructure statute applies, that same authorization is generally what brings the work inside whatever exception the statute provides.

The failure mode is a crew holding permission that nobody on site can produce. An officer standing at the fence is not going to wait while somebody phones a project manager, and a stopped flight on a live corridor costs a possession window that may not repeat for weeks. The authorization, the site briefing, the named contact at the railway, and the dates it covers belong somewhere the pilot can open on a phone. So does the record of which flights ran under it, because the railway will ask. Rail clients tend to audit contractors on exactly this point, and a corridor programme that can match every flight to the authorization covering it looks materially different from one that can only produce a folder of images.

Common mistakes in flying near railways

Assuming a federal prohibition exists. No current rule closes the airspace over ordinary track to Part 107 operations. Crews that believe otherwise decline lawful work, and crews that discover it late assume the ground is equally open.

Standing on the right of way. Launching, landing, or spotting from railway property is trespass regardless of how legal the flight is. Position the crew on public land or land you have permission to occupy.

Treating railroad police as private security. In most states they hold law enforcement commissions with authority over railway property. An instruction from one carries the weight of an instruction from any officer.

Ignoring state critical infrastructure statutes. Several states criminalize drone operations over listed facilities including railways, with terms that vary by state. Corridor work crossing state lines crosses statutes as well.

Carrying permission nobody can produce on site. Written authorization that lives in a project inbox does not help a pilot at a fence line. Put it where the crew on the ground can open it in seconds.

FAQ

Is it illegal to fly a drone over railroad tracks?

Not under current federal airspace rules, which do not single out railways. The restrictions that bite are state critical infrastructure statutes and property law governing the right of way, both of which vary by location.

Can railroad police stop me flying from public land?

Their authority runs to railway property, so a crew standing on public land is in a different position from one on the right of way. Officers may still ask questions, and state statutes may apply regardless of where you stand.

Do I need permission from the railroad to inspect track by drone?

For contracted inspection work, yes in practice. Written authorization naming the corridor and the dates resolves the trespass question, gives the crew something to show on site, and usually satisfies whatever exception a state critical infrastructure statute provides.

Could the rules change?

Yes. The FAA proposed a petition based framework in May 2026 that would let qualifying fixed site facilities obtain airspace restrictions. Railway facilities are eligible, though blanket coverage of all track was not proposed.

Closing thought

Railways are the clearest case in drone work of a question that sounds like airspace and resolves like property. The sky above the track is open under federal rules, the ground beside it is not, and a growing pile of state statutes sits in between. The operators who fly rail corridors without incident are not the ones who researched the FAA position hardest. They are the ones holding written permission, standing somewhere they are allowed to stand, and able to prove both in the thirty seconds before a conversation escalates.

If you are flying corridor work along rail, FlybyOps was built for the operational record problem at the center of regulated drone work. A document vault holding authorizations with expiration tracking, a project and job hierarchy scoped by site, role based access so field crews reach what they need, and an append-only audit log are all part of how the platform keeps landowner permissions and site approvals attached to the jobs they made possible.