Operating location
NATS reference layers + NOTAM screeningSelect a site to load the map.
Basemap features do not establish permission to fly.
Airspace layers & NOTAM briefing
Reference visualisation and conservative screening—not flight clearance. NATS marks its KML visualisation “Not for operational use”. Confirm boundaries, activation and permissions in the authoritative AIP and a current official briefing. Map layer switches change visibility only; hidden layers still appear in the overlap screening.
Mapped features potentially overlapping the mission area
NOTAM candidates within two hours of the selected time
Circles show Q-line screening extents, not actual restricted boundaries. The local shortlist screens out clearly identified overseas conflict-zone advisories and notices demonstrably above the stated height envelope; excluded items and reasons remain available below. Read schedules, the full text, valid dates and any cancellations/replacements. An empty result is not proof of unrestricted airspace.
NOTAM screening pending.
Official NATS AIS · obtain a point/zone briefing · NATS contingency PIBs and full XML
Use the official briefing check below to record your independent review of the full area, height and ±2-hour window. The automated list is reference only.
Optional height-screening detail · verified terrain elevation
Only needed to screen explicit AMSL lower limits. Enter the highest terrain elevation anywhere in the operating area, not just launch elevation. Leave blank if uncertain; notices are then retained. Flight levels are not converted to AMSL.
Notices with unparsed location · manual review required
Outside the local/height shortlist · view notices and screening reasons
The NOTAM source is refreshed on demand; the published NATS contingency collection is hourly and covers approximately seven days. An independently archived copy is labelled explicitly if the official feed is unavailable. Neither this screening nor an archive replaces an official pre-flight briefing.
NATS restriction definitions/map ↗ · NATS full PIB / contingency notices ↗ · AIP Supplements / briefing sheets ↗
Coverage gaps: local byelaws, landowner access, environmental designations, uncharted small airfields, obstacles and emergencies are not exhaustively mapped. Check separately. Reference data may include Crown Dependencies: confirm jurisdiction. NATS attribution: © NATS; aviation use only, not for resale. Curved boundaries are approximated and may show artificial gaps.
Conditions at the briefing hour
Hourly outlook
Show hourly forecast data
| Time | Wind 10 m | Gust 10 m | Wind 80 m | Precip. chance | Visibility | Rain · mm/h | Temp · °C |
|---|
Forecast limitations and freshness
Model grid conditions may differ from your launch site, especially near terrain and buildings. 80 m wind is not the wind at any arbitrary flight height. No automated aircraft-limit or visibility safety decision is made. Compare forecasts with on-site observations, warnings and manufacturer limits. Data refreshes every 15 minutes while visible; refresh again before flight. Retrieval time is not model issue time. Sunset is not a legal determination of night.
Weather map · regional forecasts and recent radar
Open-source Leaflet map with Open-Meteo forecasts. Regional context only; forecast points are model samples, not weather stations or a continuous high-resolution survey. Map colours do not alter the GO/NO-GO checks.
Select a site to load regional weather.
Model point coordinates will appear after loading.
Forecast follows the flight date/hour in Europe/London. Requests form a 5 km-spaced, approximately 20 × 20 km sampling area around launch; returned model locations may be offset; panning does not fetch more points. Local terrain, turbulence and wind at flight height can differ. Forecast data: Open-Meteo · CC BY 4.0. Public API is for eligible non-commercial use; commercial users need appropriate API access. Coordinates go to weather and map providers when loaded.
Recent rain radar · optional
RainViewer is a free-access service, not an open-source data service. Free use is limited to eligible personal/educational use; commercial use requires separate provider terms. Radar shows the recent past, independently of the selected flight date. It is not a rain forecast.
Radar not loaded.
Radar uses RainViewer’s Universal Blue reflectivity palette (scheme 2). View the dBZ colour legend. These are not calibrated surface rainfall rates. Black coverage shading means no radar coverage; missing data can also appear transparent. Maximum native tile zoom is 7. Weather data by RainViewer.
Paid subscriptions and weather-service links · optional
A consumer subscription does not automatically grant API access. Open your subscribed service in its own tab and sign in there. Saved links are shortcuts, not account connections; premium layers are not imported.
Use only your own Open-Meteo API subscription key. It is sent directly to customer-api.open-meteo.com for forecasts, held in page memory, excluded from saved missions/backups, and cleared on reload. It is not a secure shared server credential. This setting applies to both point forecasts and the regional map. Other providers’ keys are not supported. Service shortcuts are stored on this device and are not included in mission backups.
Forecast exceeds configured limits
Conditions must be carefully assessed on the ground before take-off and throughout flight. The forecast may require postponing or cancelling the flight. Do not fly outside aircraft limits, legal requirements or your operating procedure. Acknowledgement records awareness; it does not authorise flight outside these limits.
GO/NO-GO required. This acknowledgement does not override weather limits or missing/stale forecast data. Reconfirm after changing the site, flight interval, weather limits or forecast.
3Open Category guidance
Incomplete profileGuidance checked against CAA sources on 10 November 2026. Simplified scope: ordinary Open operations; no assessment of exemptions, association authorisations, class documentation, airspace approval or site-specific legality. Recheck original sources before flight.
Battery management and health
Manufacturer suggestions + pilot checksBattery selection, inspection and cell health
GO/NO-GO critical fields must be completed or confirmed for a green result. Optional fields are supplementary records. Manufacturer suggestions are prefilled where verified; review your exact configuration. Current charge, condition and measured cell voltages cannot be prefilled.
Manufacturer battery suggestions · view values and source
Dual/multi-battery aircraft need a complete matched set. Record the lowest state of charge in the set, not an average. Compatibility, cell balance and physical condition must be inspected by the pilot.
Battery / matched-set record
Controller readings · cell balance & take-off charge · GO/NO-GO critical
Read the lowest and highest individual-cell voltage for each physical pack. Do not enter total pack voltage here. Cell spread = highest − lowest within that pack; paired-pack voltage mismatch is a separate check.
Defaults use the available DJI source. To edit the voltage criterion or reference, select Override and record why. An override cannot relax a verified manufacturer ceiling for a green planning result. Unknown criteria require an explicitly documented operator procedure; an operator proposal is not manufacturer approval.
References fill automatically where verified. Neither specifies the actual lowest or highest cell voltage at your present charge, temperature and load. Enter both measured readings from the DJI app below; reference values never complete the balance check.
Cell balance: incomplete.
Select/add the failed battery record first. This action records the failure and quarantines that record, then clears the selected pack, readings and supported flight time. Select a different compatible pack/set and repeat the battery checks. Other briefing entries stay in place; weather confirmation resets if the recalculated duration changes. Final review must be confirmed again.
Battery replacement history
Saved in this browser and included in the printed briefing. Failed records cannot be reused to clear this replacement check. A recorded GO means planning gates were completed, not flight clearance.
The status reports a completed balance screen only, not battery health or safe endurance. Charge state, temperature, load and rest time affect voltage. A balanced but deeply discharged or damaged battery is not serviceable; follow DJI warnings and the exact battery manual.
Flight-time allowance · GO/NO-GO critical
This sets a conservative total time from take-off to landing for this mission. The app adjusts a supported full-charge flight time for the charge actually available, preserves your landing charge, then subtracts any extra time margin. The result automatically sets the mission duration used by the weather and daylight checks.
Start with the battery record above, then complete these three inputs. A manufacturer's maximum is shown as a reference below; it is not a validated time for your payload, battery condition and weather.
Your calculated mission duration
No calculate button is needed. The result updates as you enter values. It is a planning ceiling, not a target: finish earlier when the task is complete or conditions require it. Normal return and landing must fit within this time.
Calculated automatically from the selected battery and the flight-time inputs above.
Waiting for battery and flight-time inputs.
The available duration is the largest whole minute strictly below the battery allowance (maximum 180 minutes). It includes take-off, return and landing. Weather and daylight checks use this calculated maximum duration. This estimate is not a guarantee of endurance.
Select a battery record and enter the three flight-time values above.
Example: 20-minute reference → 17-minute mission
Example only: your comparable full-battery flight takes 20 minutes to reach 25%. Your selected battery is currently at 100%, and you keep an extra 2 minutes back. The planning allowance is 18 minutes (20 − 2). Your total flight, including take-off, return and landing, must be shorter than 18 minutes. The app therefore fills in 17 minutes automatically as the maximum planning duration.
If that battery starts at 80%, the same simple estimate becomes 12.7 minutes: 20 × (80 − 25) ÷ (100 − 25) − 2. The app fills in 12 minutes. For a matched pair, the lower charge is used; two fitted batteries do not double the flight time.
Formula: full-battery time to landing charge × (starting charge − landing charge) ÷ (100 − landing charge) − extra time kept back. This is a linear planning estimate. It does not predict nonlinear discharge, wind, temperature or ageing. If you lack supporting flight data or an approved procedure, leave the time blank: the plan stays NO-GO until reviewed.
Confirm battery readiness · GO/NO-GO critical
Saved battery inventory
Select records to remove from the active inventory. Saved flight snapshots and battery replacement history are retained. Removed inventory records can be restored below.
4Pilot’s evidence record
0 / 10 recordedNO-GO · planning incomplete
Complete the required inputs and checks.
Outstanding items
This repeats the live summary at the top. GO means the configured planning gates are complete; it is not CAA approval, airspace clearance or a guarantee of safety. The remote pilot makes the final on-site decision.