It looks like this is simply a "field to land on". On Google map, the "runway" still seems to exist ... albeit ~300m WSW from the original location @ lat: 44° 6'19.68"N, lon: 73°22'56.58"W ... which it quite likely has "always been"; these ancient WedBot submissions are known to be notoriously "inprecise".
Actually ... let's wind down (english is not my first language, what I write easily "sounds" way more controversial than it is meant to) ... I just realised that we are probably agreeing on the fact that the runway - as it is currently depicted in X-plane - does not exist ... and it likely never has.
The submission I just made does place the grass runway "where it likely was meant to be" (and where it likely still exists)
"(and where it likely still exists)" No it does not exist. Done for. FAA entry canceled and the ID "VT33" was given to a heliport.
And the imagery is from 1994. Runway is visible in that imagery.
And no I don't agree on that the field was never there. How clear do i have to be on that it was there if there its a visible runway? It lost its use. Overgrown -> got turned into regular farmland.
"Closed, FAA deletion 01/05/17. Replaced pilot info with archived link. VT33 is now: BLSG Brandon Heliport, Brandon VT." - ourairports
Well... color me blind, but I see that same stretch in all of the pictures 1994-2023 (also, if you do overlay the runway from the existing scenery, that isn't exactly where it is placed at as seen in the attachment) ... however - that having been said...
Thankfully I only moved the runway to match the map and skipped my normal "let's add the buildings and other stuff, etc." routine ... would've been very frustrating to go through all that trouble for non-existing field I can fully agree that admins can throw away my submission #104791
This is the location of the ol' field, land reconfigured:
https://maps.app.goo.gl/ErqmRQzcsRNZVyd59
Markku Post-Uttula December 5, 2024 2:19 PM
It looks like this is simply a "field to land on". On Google map, the "runway" still seems to exist ... albeit ~300m WSW from the original location @ lat: 44° 6'19.68"N, lon: 73°22'56.58"W ... which it quite likely has "always been"; these ancient WedBot submissions are known to be notoriously "inprecise".
Markku Post-Uttula December 5, 2024 2:45 PM
Gateway scenery 104791 submitted to better match present state of reality.
FlyWithNils December 5, 2024 6:37 PM
Historical imagery shows the runway where it was. It is now gone.
Private airstrips like this one appear and disappear regularly.
Markku Post-Uttula December 5, 2024 10:25 PM
Must be super historical ... My imagery only goes back 30 years - and such "runway" (aside from the the one I believe is a "runway") does not exist.
Markku Post-Uttula December 5, 2024 10:27 PM
Or... just to be clear ... are you saying that the thing that looks like a grass runway no longer exists?
Markku Post-Uttula December 5, 2024 10:43 PM
Actually ... let's wind down (english is not my first language, what I write easily "sounds" way more controversial than it is meant to) ... I just realised that we are probably agreeing on the fact that the runway - as it is currently depicted in X-plane - does not exist ... and it likely never has.
The submission I just made does place the grass runway "where it likely was meant to be" (and where it likely still exists)
I hate my language
FlyWithNils December 6, 2024 5:28 AM
"(and where it likely still exists)" No it does not exist. Done for. FAA entry canceled and the ID "VT33" was given to a heliport.
And the imagery is from 1994. Runway is visible in that imagery.
And no I don't agree on that the field was never there. How clear do i have to be on that it was there if there its a visible runway? It lost its use. Overgrown -> got turned into regular farmland.
"Closed, FAA deletion 01/05/17. Replaced pilot info with archived link. VT33 is now: BLSG Brandon Heliport, Brandon VT." - ourairports
Markku Post-Uttula December 6, 2024 5:44 PM
Well... color me blind, but I see that same stretch in all of the pictures 1994-2023 (also, if you do overlay the runway from the existing scenery, that isn't exactly where it is placed at as seen in the attachment) ... however - that having been said...
The FAA-page for VT33 https://nfdc.faa.gov/nfdcApps/services/ajv5/airportDisplay.jsp?airportId=VT33 is a much better reference (than the Google-link) for the field no longer being assigned this identifier.
Thankfully I only moved the runway to match the map and skipped my normal "let's add the buildings and other stuff, etc." routine ... would've been very frustrating to go through all that trouble for non-existing field
I can fully agree that admins can throw away my submission #104791
As per the discussion on Gateway-site, it looks like this airfield indeed no longer exists. It is ok to reject this scenery.
Julian Lockwood December 11, 2024 12:21 AM
Still visible as a landmark.