Bumpy Flight works best when every player owns a lane. The experience officially promotes crew play, but it does not publish a rigid class chart. Treat pilot, cabin, engineer, and runner as practical assignments that your group chooses. They reduce duplicated work and give every warning an owner without pretending the game permanently locks a player into one job.
Fast assignment: one pilot, one cabin player, one repair runner, and one flexible helper. With fewer people, combine support jobs but never leave aircraft control unowned.
Pilot: protect the flight path
The pilot owns pitch, heading, throttle, takeoff, cruise stability, and landing. Official keyboard controls use W/S for pitch, A/D for turning, Shift to increase throttle, and Ctrl to decrease throttle. Because the pilot must coordinate several inputs, they should not leave the position for routine supplies in a co-op run.
Before takeoff, the pilot confirms that luggage, passenger, and fuel objectives shown in the server are complete. In the air, the pilot announces major changes: stable cruise, incoming storm, destination visible, beginning descent, and landing. Short warnings give the crew time to finish movement and avoid crowding the cockpit.
A pilot should use a clear control transfer if they must switch. “You have controls” and a response of “I have controls” is better than two players assuming the other is flying.
Cabin support: own passenger state
Cabin support guides passengers to seats during preparation and answers their needs in flight. Current walkthroughs describe food, water, medicine, and angry or uncomfortable passenger prompts. The exact item and location should come from the live request, not from memory of an older version.
The cabin player learns the refrigerator or food area, the order terminal, and the passenger aisle before takeoff. They announce which passenger is being helped so the runner does not deliver the same item. When a landing announcement begins, cabin support finishes the current required action and avoids starting an optional trip through the aircraft.
Cabin support also reports whether an issue appears stuck. That lets the crew decide whether to retry the interaction or continue rather than silently wasting the entire approach.
Engineer: read before repairing
The engineer handles aircraft warnings and tool routes. Recent community walkthroughs mention wing icing, storm or engine damage, and a rear power problem. They report tools such as an Ice Scraper or wrench, but these observations are beta-specific. The engineer must read the current prompt, obtain the item it names, and follow the current marker or labeled equipment.
Do not carry a remembered tool to every event. A wrong trip wastes time and can make the warning harder to diagnose. The engineer calls the problem, says “moving,” completes the interaction, and reports “clear.” During quiet flight, the engineer can help with luggage or passenger supplies while remaining ready to switch back.
Runner or copilot: remove bottlenecks
A fourth player should not invent a second pilot. Use them as a runner or cockpit observer. On the ground, they help with luggage, fuel, and supply discovery. In the air, they can fetch a requested item, relay the warning text, watch destination guidance, or help a cabin player whose path is blocked.
The runner does not override the assigned owner. Ask “need help?” before taking over an interaction. If no extra task exists, stay out of narrow aisles and interactive zones. Physical crowding can be more harmful than a moment of waiting.
Two-player crew plan
Player one remains pilot. Player two handles preparation support, passenger care, repairs, and supply fetching. Because that is a broad load, finish all visible ground objectives and learn the interior before taking off. The pilot should fly smoothly and begin alignment early, creating safe windows for the support player to move.
The support player triages aircraft warnings before ordinary cabin requests unless the active game prompt indicates otherwise. They announce when they leave the cabin for a repair. The pilot may need to accept a short passenger delay rather than destabilize the aircraft.
Three-player crew plan
Use pilot, cabin, and engineer. The engineer also owns luggage and fuel preparation; cabin owns boarding. Once airborne, the cabin player remains focused on passengers and the engineer remains focused on the aircraft and supplies. This is a balanced group because every urgent lane has a named owner.
If the engineer has no warning, they can stage near the supply route. If the cabin is clear, that player can watch announcements. Neither should sit in the pilot’s space unless asked.
Four-player and larger groups
Start with pilot, cabin, engineer, and runner. Extra players can help during preflight, but assign them specific bags or passengers instead of saying “everyone load.” In flight, avoid creating competing captains. One person still calls the approach and one person still owns each response.
If friends want to try flying, rotate pilots between complete flights. Role rotation gives each player a fair turn without risking a control change during a storm or descent.
Solo role priority
Solo play turns the roles into a decision ladder. Stabilize the plane first. Address the required aircraft warning second. Handle urgent passenger care third. Delay optional optimization until the flight is predictable again. Complete all ground tasks while stationary and learn the supply route before adding throttle.
The official page supports both preparing the aircraft and handling emergencies, but it does not provide a promise that every solo task pauses while you fly. Use conservative inputs and do not begin two cabin actions at once.
Fix role confusion quickly
If two players grab the same task, the first person to announce it keeps it and the other returns to standby. If a player cannot complete their interaction, say what failed and hand it off explicitly. If the pilot disconnects or leaves, name the replacement immediately and stabilize before continuing optional tasks.
After the run, change only the assignment that caused the bottleneck. A rough result does not automatically mean the pilot failed; late passenger care or a slow repair can also compress the landing window.
For the next step, use Boarding Passengers, Passenger Care, and Play With Friends.