The Aerolync widget is a small button that visiting pilots see on your aerodrome's own website. It opens into a panel with up to three tabs — Live Status (runway status, sunrise/sunset, duty contact), PPR Request (the request form) and Pilot Info (opening hours, free text and downloadable documents such as charts) — in the visitor's own language (25 European languages, automatically detected). Submitted requests arrive directly in the PPR module, where they are reviewed and answered.
The first time you open PPR → Widget, a widget is created for your organisation automatically, with a unique sitekey and sensible defaults — you only tailor it and embed it.
The widget is self-contained and isolated from your website's styling: it cannot break your site and your site cannot break the widget.
See it in action
This page runs a live demo of the widget, connected to a fictitious demo organisation: the button at the bottom left of your screen is exactly what visiting pilots see on an aerodrome website. Open it and browse the three tabs, or jump straight to the request form:
Note
requests submitted through the demo go to the demo organisation only and are not processed. Feel free to walk through the form up to the confirmation.
Embedding
Place this snippet just before the closing </body> tag of your website:
<script src="https://cdn.aerolync.com/widget/v1/widget.js"
data-sitekey="YOUR_SITEKEY" async></script>Your sitekey identifies your aerodrome and is shown read-only in the widget settings. It is not a secret — abuse is prevented server-side by the allowed domains list and rate limiting.
Note
the widget only works on domains listed under Allowed domains in the widget settings. Add every hostname you use (for example example.com and www.example.com).
Opening the widget with your own buttons
Besides the built-in button (the "pill"), your website can open the widget from its own buttons and links, or control it programmatically. Your web developer finds the complete technical reference — data attributes, the JavaScript API, CSP guidance and troubleshooting — on the widget integration page in the Developer section.
Configuration
Everything is configured per widget in PPR → Widget (requires the Settings write permission):
| Section | What you control |
|---|---|
| General | Widget active, header name and ICAO, base colour, position on the page, and the ready-to-copy embed code. |
| Tabs | Which tabs visitors see: Live Status, PPR Request, Pilot Info. |
| Opening hours | Whether an ETA outside your opening hours only warns the pilot (default) or blocks the request entirely — Block requests outside opening hours on the PPR Request tab. |
| PPR form | Per block and per field: shown or not, and required or optional. Unused blocks (e.g. Handling) can be switched off entirely. |
| Scheduler | Whether requests appear in the scheduler, in which calendar and on which line, and whether an accepted PPR becomes an active line. Pick a calendar without picking a line and a dedicated "PPR" line is created for you automatically. |
| Pilot info | Free text for the Pilot Info tab, documents (PDF, PNG, JPG — max. 10 MB each) that visitors can download, and external links (title + URL) to pages on your own website. |
| Advanced | Auto-open on page load with a configurable delay, and the allowed domains — the websites that may load this widget, one per line. |
Two settings deserve extra attention:
- Default timezone (Advanced tab) — the timezone the widget uses until the visitor picks one themselves: UTC (the aviation standard, default) or the visitor's local time. Whenever the active timezone is not the visitor's local time, its abbreviation is shown directly after the times (for example
08:00 UTC) at the sunrise/sunset line and in the opening hours. - Auto-accept requests (PPR Request tab) — new requests skip the pending state: they are approved automatically, the pilot immediately receives the approval e-mail, and the flight appears in the scheduler as accepted. Your team is still notified of every request. Use this when requests never need manual review; blocking outside opening hours still applies.
Text and colours adapt automatically: the widget calculates readable contrast from your base colour, and all interface text follows the visitor's language.
What the visitor experiences
- The pilot fills in the form; the phone field offers a country-code picker with per-country validation, and times are entered in UTC by default (the aviation convention — the visitor can switch time zone).
- After validation a summary screen shows everything that was entered. The pilot must accept the privacy statement (shown expandable in their language, with your organisation's name) before sending.
- On submission the pilot immediately sees a confirmation with a reference number, and receives an acknowledgement e-mail. Your team is notified at the addresses configured under Config → Settings → PPR notifications.
- When you accept or reject the request in the PPR module, the pilot automatically receives the decision e-mail — see the module overview for the full flow.
Opening hours in the widget
When opening hours are configured for your aerodrome, the Pilot Info tab shows them as a weekly overview (Monday to Sunday, following the season that applies today) with upcoming exception dates — public holidays, special events — listed separately. Times follow the time zone the visitor selected; hours defined as sunrise or sunset are shown as the word in the visitor's language rather than a clock time.
If the pilot picks an arrival time outside those hours, the summary screen shows a clear warning before sending. With Block requests outside opening hours enabled the request cannot be submitted at all — and the same rule is enforced server-side.