EDITORIAL POLICY
Editorial policy and our guide: how we cite and how far we read
What this guide relies on, how far each source was checked, and where the editors’ own view begins — written down so readers can verify for themselves.
On this page
About our guide, Sir Airffic Go
The Japanese edition is guided by Sir Airffic Go, a boy who speaks in Hiroshima dialect, sharing the illustration and voice of the Airffic Flight Institute. The English edition presents the same content in plain English. The guide’s voice is for warmth; rules and figures follow the sources.
Reading scope, item by item
| Label | Meaning |
|---|---|
| Full text read | The body of the page was opened and read |
| Abstract read | Only the abstract or summary was read |
| Search snippet only | Only the title or snippet from search; body not read |
| Pending | An official page chosen as the source, not re-read in this pass |
A successful HTTP response or text length is never treated as “read”. We do not copy third-party text; we keep bibliographic data, URLs, reading scope, short original summaries and factual notes only.
How country sources are selected
National readership rankings are not public, so this guide never claims “the 30 most-read articles”. We search in the local language, prioritise national media, public bodies, industry associations, major operators and research institutions, and state why each item was selected. A foreign company’s case is never attributed to its home country.
Separating kinds of numbers
- Reported: measured and published by whoever carried out the work
- Estimate: calculated under stated assumptions
- Target: a goal not yet achieved
- Company claim: a vendor’s statement without independent verification
Cases where drones did not help, and studies that found no economic advantage, are kept, not deleted.
Vision and design proposals
The vision and each page’s “2035” chapter are the editors’ (Airffic World’s) outlook, written separately from descriptions of current rules and technology. For real operations, always check current official information for your location and conditions. This guide does not certify flight permission or asset safety.
Made by people and AI together
Research, writing and code are produced by people working with AI (such as Claude), with full history in Git. Research data lives in research/ and text in src/content/, in a shape anyone — ChatGPT, Grok, Claude or a person — can extend and verify. See use with AI & API.