Flying in Europe | Separating Aircraft Classes from Operational Categories

In EASA's Open category there are conditions such as visual line of sight and altitude on top of the aircraft conditions. A 120 m limit is generally stated, but check the original text, including exceptions and how it relates to terrain. If you exceed the Open conditions, confirm with the authority whether Specific or another category applies.

Reading the common framework is one thing; looking up the authority and geographical zones of the country you actually fly in is another. The app should store the country, the jurisdiction, the registering entity and the area covered. A label that just says "registered in Europe" doesn't tell anyone what was verified.

Operator registration and aircraft class marking are different things too. Because a camera or similar sensor can make operator registration relevant even for a light aircraft, don't steer people with "under 250 g means nothing is required"; send them on to EASA's overview and the authority's guidance.

• Specify the country and the date and time of the flight first.
• Confirm aircraft class, weight, camera and so on, with evidence.
• Enter operating conditions such as distance from people, visual line of sight and altitude.
• Show the training, registration and geographical-zone items that need checking.
• For an unknown class or an older aircraft, check the applicable official treatment.

You don't have to show every input at once. Present only the questions the previous answers make necessary, in order, and you get both a short UI and a rigorous sorting of conditions.

Someone using the app in Japanese may be flying in France. Setting the display language to Japanese must not apply Japan's rules. Hold them as separate values, such as language=ja and jurisdiction=FR. Where a translation isn't available, show the original text and its source, and never fill in decision-relevant sentences by guesswork.