EDITORIAL / KNOWLEDGE & DESIGN

Editorial policy & the guide

We make material readers can use, with evidence and proposals kept clearly apart. A friendly voice still has to answer for what it says.

Read this page in order
01

What this site is for

Airffic Flight Institute is a drone knowledge base and design reference for Airffic World. It organises flight regulations, operational workflows and airspace technology, and shows concretely how they translate into a product. It is not a public research body, a licensing authority or a live flight-operations service.

The explanations are drafted with AI, and regulatory entry points and definitions are checked against primary sources. The original design proposals, sample data and worked calculations are there to help you think through an implementation. Expert review, real-aircraft testing and validation with customers have not been carried out for this edition.

02

Telling sources from proposals

LabelMeaning
Source linkThe reference for the regulatory explanation or definition just before it
Original design proposalAn editorial idea or hypothesis to make things concrete
Sample data / worked exampleA fictional example that shows a structure or calculation
Checked onThe date the stated information was verified. Not updated automatically

For an actual flight, confirm with the competent authority, the local government, the site manager, and the conditions of your aircraft and operation. Please don't read a short explanation on this site as permission for any specific flight.

03

About the Hiroshima-dialect guide

The guide in the Japanese edition is a boy character called "Sky Partner" who speaks in Hiroshima dialect. He waves to welcome you, raises a finger to make a point, and tilts his head to think things through with you. Bright and curious, he never leaves anyone stuck; he starts from "why?" and finds the next step together with you.

He does not speak as any real expert or licensed professional, and he does not reduce the people of Hiroshima to a single personality. For regulation names, figures, units and control labels, accuracy of meaning comes first.

04

Update criteria

  • When a regulatory change is confirmed, review the affected articles and design examples.
  • When the same source differs by effective date or scope, state that difference explicitly.
  • Never present unmeasured performance or benefits as a track record.
  • When introducing a feature of the main product, show the confirmed scope of availability.

We don't just bump the date; we record what was checked and what was fixed. The 30 September 2026 edition added detailed explanations and design examples across the four fields, and brought the Japanese guide into Hiroshima dialect. The same update introduced the boy guide and the questions he asks that follow each article's content.

DEFINITION OF DONE

When you build it, check these.

  • Evidence and design proposals are kept distinct.
  • No qualifications, track record or features that don't exist are displayed.
  • The check date matches what was actually updated.

Design checkpoints for use in spec reviews and functional testing.

How to read this page

This page is an original design proposal. Implementation and numerical examples are not evidence of real-world results or certification. Verify them against the conditions of the work you apply them to.

Read how this was made and our editorial policy