The primary Roblox source was reviewed on 2026-08-08. Exact values or steps that source does not confirm remain labeled unknown until reproduced in the current version.
Identify the current objective first
Enter through the official Roblox listing and read the exact objective text that the current version presents. The launch research does not contain that text, so no task name or order is quoted here. Record the wording before following an outside tutorial, because a similarly named task may have changed or may refer to another phase.
Do not assume that landing is always the first objective or that every server follows the same sequence. The high-level theme confirms landing tasks, not a fixed opening script.
- Use the official experience entry.
- Quote the current objective exactly.
- Note the observation date and visible version wording.
- Keep task order marked unknown until reproduced.
Learn controls from live prompts
No keyboard, mouse, controller, or mobile mapping is verified in the research record. Use the current interface for every input, and do not borrow a control scheme from a different Roblox flight game. A key that commonly performs an action elsewhere is still unverified here.
For a future control entry, a useful report includes device type, exact prompt, action context, result, and date. A screenshot can support the wording, but it must belong to the current game and should not expose private account information.
- PC controls — unknown.
- Controller controls — unknown.
- Mobile controls — unknown.
- Alternate layouts and remapping — unknown.
Treat flight values as version-specific evidence
The source does not establish fuel capacity, consumption, speed, altitude, angle, timing, damage, or any other numerical threshold. Those values should not appear in a beginner route until the current game explicitly states them or a repeatable test establishes their role.
When the interface displays a number, preserve its label and unit rather than guessing what it controls. Seeing a value does not prove a required target, and a failed attempt does not by itself prove which variable caused the failure.
- Fuel values and behavior — unknown.
- Landing speed or angle — unknown.
- Damage and failure thresholds — unknown.
- Recommended targets — needs current-version verification.
Coordinate without inventing roles
Because the experience is multiplayer, players can choose to communicate about visible objectives. The evidence does not name a pilot, copilot, engineer, attendant, or any other formal role, and it does not establish role permissions. Use only labels the current interface actually assigns.
Rewards, maximum player count, best staffing, emergencies, and private-server rules also remain unknown. Continue to How to Land for the landing verification framework or Crew Roles for a precise account of what would be required before a duty can be documented.
- Communication is an optional player practice, not a confirmed mechanic.
- Formal role list — unknown.
- Role-specific controls or permissions — unknown.
- Best crew composition — unknown.