Skip to main content
Event rules decide which flight events Stratos logs into the PIREP: engines starting, flaps moving, stalls, phase changes and so on. Flight Tracking comes with a full set. You can change any of them, add your own, or describe a rule in plain English and have it drafted with AI. Open them from Plugins → Flight Tracking → Event rules.
At a glance
  • Each rule logs a message when its conditions become true.
  • Your edits are a draft until you Save and Publish changes.
  • Pilots get published rules from their next flight. A flight in progress keeps the rules it started with.
  • Edit with AI drafts a rule from a description. Every plan gets a monthly allowance of drafts.
Flight Tracking's Event rules tab: each rule, when it fires and what it logs, with New ruleFlight Tracking's Event rules tab: each rule, when it fires and what it logs, with New rule

Edit a rule

Click a rule to open it. Each rule has:
  • A name.
  • When: one or more conditions on the flight’s data, such as Gear Control equals true. Condition adds another, and Log when all/any of these are true decides how they combine.
  • Log: the message written to the flight log. It can include live values, such as the airspeed, and Preview shows how it reads.
  • Hold true for: how long, in milliseconds, the conditions must stay true before the message is logged.
  • Skip if true when tracking starts: ignores a condition that’s already true when tracking starts until it changes, so a cold and dark start doesn’t log “Engine 1 shut down” before the engine has ever run.
Builder and JSON switch between the form and the rule as JSON. Duplicate copies the rule and Delete removes it. Drag a rule by its handle to reorder the list.

Add a rule

Click New rule at the top of the list. The toolbar beside it also has:
  • Defaults: the rules that come with Flight Tracking. Add any you don’t have; they go to the end of your list.
  • Import and Export: your rules as JSON, to bring rules in or keep a copy.

Write a rule with AI

Edit with AI on an open rule drafts it for you from a description.
  1. Open a rule, or click New rule, which opens on the prompt.
  2. Click Edit with AI and describe what the rule should do, such as “Warn when faster than 250 knots below 10,000 feet”.
  3. Click Write rule. The draft shows under the box, with anything it changes marked Changed.
  4. Click Apply to put it in place of the rule, Rewrite to try again with a new description, or Discard.
A rule open on the Event rules tab with Edit with AI showing the box to describe what the rule should doA rule open on the Event rules tab with Edit with AI showing the box to describe what the rule should do
An applied draft is an ordinary edit: check it, then save and publish it like any other change. Each airline gets a monthly allowance of drafts: 25 on Free, 250 on Pro and 1,000 on Pro+ (see pricing). The count of AI drafts left, at the right of the toolbar beside New rule, shows how many are left this month. They reset on the 1st.

Publish your changes

Your edits stay a draft until you publish them, so you can change several rules at once.
  1. When you’ve made changes, a bar at the foot of the list shows what changed. Click Save, or Discard to go back to what pilots have now.
  2. Review changes shows each change before and after.
  3. Click Publish changes.
Pilots get the new rules from their next flight. A flight in progress keeps the rules it started with.