Just to reiterate - it’s really weird how this is occurring in 2024, where it’s almost obligatory for a small airport to have one to three individual trees right at the end of the runway, where no trees exist irl - and no other trees around it. It was problematic in 2020, but not quite in the same fashion - here it’s like something is leaking through the exclusion, at the worst possible place. This really needs to be addressed, probably worthy of a bug report.
@SaskWayne
FYI, Can be reported here for 2024:
With due respect, I think this is a wider issue with the way trees are parsed. To wit, at several airports in which I had removed trees in the World Hub using exclusion boxes, trees reappeared in 2024. And it’s weird, it’s like the rest of the trees are being excluded, but a small few leak through.
I think the only way to verify this will be to get back into the world hub and see how trees are being treated, especially where this is happening.
But it’d be a shame to have to go manually fix this when it could be a simple global tweak.
This works to a point…
Typically, I forget the actual distance, but the FAA prescribes the a distance leading up to a runway that must be clear of obstacles (trees). I know the owner of 6B6 is constantly fighting with the people surrounding his airport to clear the trees leading to the main runway, even though by Federal law, he has to.
Be that as it may, that prescribes a distance all around the asset. In this case, there also needs to be a choice to clear vegetation to a particular height parallel to the runway in line with the runway for a given distance from the ends of the runway.
There are all sorts of imaginary surfaces: Runway Protection Zones (RPZ), Obstacle-Free Zones (OFZ), etc.
Advisory Circular 150/5300-13a covers most of the design criteria, which can be variable, depending on runway usage, configuration, etc.