Update — 2 weeks in: fuel & range, and a much better icing model Quick progress update for anyone following along. Thanks to everyone who's tried it and sent notes — a lot of this came straight from tester feedback. What's new since the original post: Fuel & wind-adjusted range. Enter your fuel on board and see how far you can actually reach along the route — a reachable-area ring that accounts for winds aloft, plus a "reserve point" marking where you'd hit your 1-hour reserve. Much-improved icing. A tester compared the plugin's vertical profile against a trusted reference on a real winter route and found it was over-calling "severe." He was right — I rebuilt the icing model so temperature (not just humidity) drives severity, validated it against that case plus several North American winter routes, and reserved "severe" for genuine freezing-rain setups. Far fewer false alarms now. Smarter cruise-altitude recommendations. They now stay within each aircraft's normal operating altitudes — no more suggesting 4,000 ft for a turboprop or the service ceiling for a piston. Compare Days weighs hazards by how severe they are, how much of the route they cover, and whether they sit at your cruise altitude — so a single patch of weather no longer tanks a day's rating. Smoother fuel entry and a few other refinements from tester reports. Still a free private beta, installed via Windy developer mode. Desktop browsers and Safari on iPad are supported. Beta page (install steps + the full aviation disclaimer): https://snickitybit.com/software/windy-ifr-plugin/ Decision support only — not a substitute for an official briefing, charts, NOTAMs, ATC clearance, or pilot judgment. I'd still love more pilots testing real routes, especially around icing and altitude calls. Thanks!

@jkross thankyou - well detailed report. This will be supported in the next version. Appreciated.

Thanks @fieldguard, your plugin is now published.

Hi @pavelmedia, I make it public here. Check it out! https://github.com/kakugirai/windy-bvmap-plugin

@rittels Thank you very much! Issue is resolved!

@jacobsjo Hello: I like the plugin, when it works. Half the time it won't load, even when I go to [install plugin] and try loading from there. Oh well, maybe something on my end. Thanks.

@abhii30mm Have you tried the Passage planner plugin? [image: 1778775021867-img_3704.jpeg] It offers several routes, but these are the best (fastest) routes according to the different models of your choice. But if you want to compare a route A with a route B that you draw yourself, I think the best way is to keep a screenshot of each of these routes in the Route planner (unless someone make a special plugin…).

Hi I'm experiencing the same issue. Plugin version is 0.3.19 and using the web-based version of Windy.

@Suty The problem has been solved, thank you.

@maxmichels Hello, can you please provide any info or link to this plugin, so we can effectively help you?

@Gregy1403 same here this is getting out of hand and I feel a lack of attention to the matter so: time for traj alternatives, open-meteo and stock leaflet has all the moving parts we need contact me directly if you want to chip in

@alknet Have a look at this SvelteKit app: https://github.com/ISmillex/adsb-flight-map.git - worked on first try for me, maybe a base for you This renders in 3D using Cesium and not 2D/Leaflet but the fetch/decode/display logic should apply it cleverly uses several open sources of ADS-B data [image: 1773504090205-b59a6272-6c11-4e6e-87d1-f6d796a34164-image-resized.png]

@blaaaaaaah Hello, unfortunately, route planner is anyhow offered in our API and it is not planned. We provide data and map visualizations as a secondary tool for third-party apps, but route planner stays only in our app.

@rittels thank you so much! Well, I think I'll wait for the next Windy update so not to submit another plugin update in the meantime. Thank you so much and looking forward for the update

@ivo EPIC! But any instructions on how to make them work on mobile? EDIT: very specific question: how to debug the app version (from a visual point of view)?

Ok so, I think I've figured it out some issues with this new implementation : For the L.geoJSON => The issue appears when I try to bind a Tooltip (layer.bindTooltip()) on the layer with the function OnEachFeature; => trigger the error "This layer type does not support tooltips." I was able to run the code before so I suppose that I've to tweak some elements now. For the L.Circle => The issue appears with mouseover because this event triggers the method setStyle of the element Circle. Then the circle disappears and there is no error in the console.. I think my installation is good with your suggestions, if you have any ideas about these issues I will be very grateful ! Thanks.