Flyable

The Flyable guide

Flyable Data Sources & Limitations

A planning result is only as useful as its inputs. Different Flyable panels use different providers, geographic coverage and update cycles.

Data sources

Our main data sources

Different sources. Different roles. One place to start planning.

How it works together
  • Weather
  • Airspace
  • Maps & places
  • Aircraft traffic
  • Regulations
FlyableData and planning tools
  • Flight Score
  • Map view
  • Guidance

Weather and drone limits inform the score. Maps, traffic and regulations provide separate context.

Weather: Meteo.lt and Open-Meteo

Flyable uses Meteo.lt for supported Lithuanian place forecasts and Open-Meteo for other locations and coordinate-based requests, with fallback behaviour where implemented. These are forecast services. Values shown as current conditions can represent the current forecast hour rather than a sensor at your launch point. Wind above the ground is a model output, not a measurement made by your aircraft.

Weather fields include wind speed, gusts, temperature, precipitation, condition codes and visibility where available. Open-Meteo also provides the altitude wind inputs used in supported views. A model grid cannot resolve every building, valley or shoreline. The most useful extra observation is often at the actual site: look at tree movement, nearby cloud, precipitation approaching and the wind along the intended return direction.

Weather refresh and forecast age

The forecast background worker runs every 15 minutes for locations it tracks. That application interval should not be confused with the provider’s model update schedule. Reopening a page may return cached values, and a refreshed request can still contain the same forecast run. Forecast issue times and valid times answer different questions: when the provider made the forecast, and when a forecast value applies.

Availability depends on provider responses, network access and location matching. If data are missing or stale, refresh later and compare an official weather source before planning around them. The interface cannot guarantee immediate delivery of every provider update. A changing clock or a live label is not independent evidence that a new weather observation has arrived.

Airspace: OpenAIP and official national tools

The airspace client retrieves features from OpenAIP and caches responses for ten minutes. These layers provide useful geographic context around the selected location. Their presence does not mean Flyable has checked every national UAS geographical zone, active notice, emergency restriction, land-use rule or authorisation condition. Feature coverage and source update timing can differ between countries.

Use the links in our regional and country guides to reach the responsible aviation authority and official planning tools. Open overlapping features and read altitude limits, activation times and conditions. An empty part of Flyable’s map can reflect missing coverage or a failed request. It should never be interpreted as a positive clearance from an air navigation service.

Base maps and place information

Interactive maps use OpenStreetMap tiles by default. When a CARTO key is configured, the application uses the CARTO Dark Matter base map with OpenStreetMap attribution. Roads, buildings and place labels provide orientation; their appearance does not establish airspace classification or a right to launch. Attribution is displayed on the map.

Location discovery and city illustrations can use OpenStreetMap/Overpass, Wikimedia Commons, Wikipedia and Wikivoyage. Discovered city content is cached for up to 24 hours. Pictures and points of interest explain the geography and help you research an area. They are not a verified directory of approved drone sites. Check any photograph’s displayed credit and investigate the land manager before planning around a landmark.

Aircraft traffic and what an empty display means

Where available, the traffic panel displays aircraft reports returned by the OpenSky Network integration. Traffic responses are cached for 60 seconds by geographic tile. Reception, reporting equipment, provider limits and latency affect what appears. Aircraft may be absent, delayed or at a different position by the time you see a report. Helicopters and other low-level traffic deserve particular attention around harbours, hospitals and urban operating sites.

Flyable’s traffic display is situational context, not a collision-avoidance service. It cannot establish that the sky is clear or replace visual observation and the obligation to give way. An empty list can mean no reports were returned, not that no aircraft are nearby. Do not use the display as justification for a route you cannot observe safely.

Regulations and editorial review

Our guides link to EASA, the FAA, Transport Canada, the UK CAA and national aviation or air navigation authorities. Regional summaries explain how to approach a decision; official publications remain the source for the applicable requirements. Europe includes jurisdictions with different systems, so a European destination does not automatically mean EASA rules apply in the same way.

A visible last-reviewed date belongs to the editorial text. It is not the last update of an airspace feed and it does not certify that a flight is permitted today. We avoid presenting a simplified national summary as a substitute for checking the exact operation. If a source moves or guidance becomes outdated, use Contact to send the page address and a link to the official correction.

What remains with the pilot

Confirm the location, time zone, aircraft model and forecast hour. Check the manufacturer’s operating limits, current official airspace information, temporary restrictions and the requirements for your type of operation. Obtain land access and any required permissions separately. Inspect people, obstacles, weather exposure and landing options on arrival, and keep monitoring changes during the flight.

If a source is unavailable or two sources disagree, resolve the uncertainty before takeoff. Flyable combines information to make planning easier, but it cannot reconcile every legal or operational edge case automatically. Send reproducible errors with the affected URL, time and observed discrepancy; omit credentials, personal identification documents and private flight records.