Guide hub
This page is a pre-release starter path, not a finished walkthrough. Dear Passengers is not publicly playable yet, so the job here is to organize confirmed systems, name the open questions, and label every editorial inference.
Before boarding
The official description already gives a usable starting frame: one crew member can fly while others keep the cabin functioning, serve passengers, and react to trouble caused by weather, turbulence, cargo, and the passengers themselves.
What it does not tell us is equally important. There is no public hands-on evidence yet for mission structure, exact role switching, optimal party size, tutorial flow, scoring, or how solo mode covers cockpit and cabin work. This guide keeps those gaps visible instead of filling them with guesses.
Confirmed loop vs unknown details
Source basis: the official Steam listing. No public test build, public demo, or first-hand route guide is available to confirm deeper mechanical claims yet.
Manifest decisions
One of the clearest confirmed mechanics is the manifest tradeoff. FLEXUS says crews pick passengers and cargo before departure, with larger rewards attached to choices that also make the flight harder to control. That means the game’s tension starts in preparation, not only in mid-air reactions.
The safe beginner takeaway is an editorial inference: a new crew should probably avoid maximizing every risky option on the first run. That is not a published balancing rule. It is simply the most defensible starting hypothesis until a public build shows how sharply the difficulty curve scales.
Crew coordination
The official pitch divides responsibilities between the cockpit and the cabin, but the problems clearly overlap. Turbulence, passenger service, cargo instability, and movement through the aircraft all suggest that one person’s action can increase another person’s workload.
The coordination advice here is again editorial inference, not an announced rule: call major movement early, confirm who is stabilizing the cabin, and avoid splitting attention across multiple half-finished emergencies. That advice follows from the confirmed system list, but it still needs hands-on validation.
Editorial inference
Choose a flight plan you can observe. If the game really scales risk the way the store description suggests, a mixed or lower-chaos start should make cause and effect easier to learn.
Even if roles are flexible, the first run should have one clear pilot voice and one clear cabin responder so problems are noticed and called quickly.
Passenger comfort matters, but turbulence and loose cargo look like the kind of issues that can create cascades. Test whether stabilization beats speed.
Once a public build exists, rewrite assumptions fast. Note whether failure comes from missed service, bad manifest picks, route handling, or delayed emergency response.
Every item above is editorial preparation advice. None of it should be read as a hidden mechanic, official tutorial step, or confirmed “best strategy.”
Next briefings
Solo play and online co-op are confirmed. Maximum crew size is still unannounced.
Pilot, cabin service, passenger management, and cargo handling are confirmed responsibilities.
Preview-only crew habits based on confirmed systems, not public hands-on testing.
No public build is listed, so this site cannot offer verified route guides or controls yet.
Separate confirmed crew and passenger information from trailer-only interpretation.
Check the current PC requirements before planning a co-op session or capture setup.
FAQ
There is no public build yet, so no one can honestly publish a full start-to-finish route. Before release, the reliable preparation is understanding the confirmed flight loop and tracking what FLEXUS has not explained yet.
Before launch, focus on confirmed systems: manifest risk, cockpit-cabin coordination, passenger service, and turbulence-driven disruption. Exact priorities still require hands-on testing.
There is no official maximum player count yet, so there is no evidence-backed best party size. Solo play and online co-op are confirmed, but the ideal crew size is still unknown.
No public demo is listed on the official Steam page as of July 19, 2026.
No. The checklist and coordination advice on this page are editorial inferences built from confirmed systems, and they should be retested against a public build before being treated as strategy.
Continue briefing