import { Tip, Warning, Info, ProTip } from "@/components/mdx"

Dear Passengers Co-Op Strategy Guide: Team Tactics for Success

Dear Passengers co-op transforms the game from a challenging solo experience into a test of coordination, trust, and split-second teamwork. Two players in the same cockpit -- one as captain, one as first officer -- must divide responsibilities, communicate under pressure, and build systems of shared awareness that prevent problems from slipping through the cracks. This guide covers advanced team strategies that go beyond the basics. Whether you are struggling with emergency coordination or looking to optimize your crew roles for maximum efficiency, the frameworks here will elevate your co-op flights.

The Core Principle: Shared Mental Model

Before diving into specific tactics, understand the single most important concept in co-op play: the shared mental model. Both players need to maintain a similar understanding of what is happening, what is about to happen, and who is responsible for what. When mental models diverge -- when the captain thinks the first officer is monitoring cabin pressure but the first officer thinks the captain is handling it -- accidents happen.

Building a shared mental model requires deliberate communication habits:

• Verbalize observations: If you see an amber warning, say it out loud. Do not assume your partner sees it.
• Confirm assignments: When you take responsibility for a task, announce it. "I have the radios" or "I am watching engine two" eliminates ambiguity.
• Narrate intentions: Before you take an action that affects the flight -- changing altitude, adjusting cabin temperature, diverting -- tell your partner what you are about to do and why.

<ProTip> Pro Tip: At the start of each flight phase (pre-flight, climb, cruise, descent, approach), do a 30-second "phase brief" where both players verbally confirm their responsibilities for the upcoming phase. This habit alone eliminates the majority of co-op miscommunications. </ProTip>

Role Optimization: Captain vs. First Officer

The two roles in co-op are not symmetrical. The captain has final authority, and the game's systems reinforce this by routing certain decisions and callouts to the captain role. But the most effective co-op teams blur the hierarchy in practice, treating the roles as complementary rather than ranked.

Captain Responsibilities

The captain should own the "big picture" and the flight path:

• Aircraft control: The captain flies the aircraft during critical phases (takeoff, landing) and whenever the first officer needs to focus on systems.
• Strategic decisions: Diversions, altitude changes, emergency declarations -- these are captain decisions informed by first officer input.
• Crew management: The co-pilot and cabin crew ultimately report to the captain. Use the crew command wheel to assign tasks to both the AI crew and your human first officer.
• Passenger communication: When the cabin needs a captain's announcement -- during turbulence, emergencies, or delays -- the captain handles it.

First Officer Responsibilities

The first officer owns systems and external communication:

• Systems monitoring: The first officer should be the one running the systems scan, watching engine parameters, fuel state, and cabin conditions.
• ATC communication: Handle routine radio calls. The captain should only take the radio during non-standard situations or when the first officer is overloaded.
• Checklist management: Run the checklists and call out each item. The captain responds.
• Navigation: Manage the flight plan, waypoints, and approach charts. Feed the captain the information they need for the next phase of flight.

<Info> This division mirrors real-world cockpit resource management. The captain is "head up" -- looking at the horizon, the big picture, the next decision. The first officer is "head down" -- monitoring systems, running numbers, managing communications. Both perspectives are essential, and neither role is less important. </Info>

Rotating Roles

Experienced co-op teams often swap roles between flights. The captain on one flight becomes the first officer on the next. This builds empathy -- you understand what your partner needs from you because you have been in their role. It also prevents skill atrophy. A captain who never flies as first officer will lose their systems-monitoring sharpness.

Communication Frameworks

Raw communication is not enough. You need structured communication that conveys the right information in the right order, every time. Here are the frameworks that competitive Dear Passengers teams use.

The SBAR Framework

Borrowed from aviation and medicine, SBAR stands for Situation, Background, Assessment, Recommendation. Use it when you need to bring something to your partner's attention:

• Situation: What is happening right now? "Engine two oil pressure is dropping."
• Background: What is the context? "It has been trending down for the last three minutes, from 55 to 42 PSI."
• Assessment: What do you think it means? "This looks like a slow leak, not a sudden failure."
• Recommendation: What should we do? "I recommend we monitor for one more minute, and if it drops below 35, we shut down engine two and divert."

This format takes five seconds longer than saying "engine two looks weird" but gives your partner everything they need to make a decision without asking follow-up questions.

The Challenge-Response Cycle

For checklist items and confirmed actions, use the challenge-response pattern:

1. Challenge: One player reads the checklist item. "Landing gear."
2. Response: The other player verifies the state and responds. "Down, three green."
3. Acknowledge: The challenger confirms they heard. "Checked."

Never skip the acknowledge step. Without it, the challenger does not know whether the responder actually checked or just assumed. This cycle is mandatory in real aviation for good reason.

The Emergency Callout Protocol

During emergencies, communication must be even more structured. When a critical alert triggers, use this sequence:

1. Alert call-out: Anyone who sees the alert calls it immediately. "Master caution, engine fire, engine one."
2. Acknowledge: The other player confirms. "I see it, engine one fire."
3. Assign: The captain assigns tasks. "I am flying and handling the fire. You run the engine fire checklist and talk to ATC."
4. Execute: Both players work their assigned tasks.
5. Update: At natural pause points, status updates flow both ways. "Fire handle pulled, bottle one discharged." "ATC cleared us for immediate descent."

The key rule during emergencies: never interrupt an executing action to give a status update. Finish the action, then communicate. A fire handle pull is more important than a status report.

Emergency Coordination Tactics

Emergencies in co-op are the ultimate test of teamwork. Here is how to handle the most common crisis scenarios as a coordinated pair.

Engine Failure

An engine failure in co-op should be handled using a pre-agreed division of labor:

• Captain: Fly the aircraft. Maintain altitude if possible, establish best single-engine climb speed if not. Declare the emergency to the cabin.
• First Officer: Run the engine failure checklist. Identify the failed engine (critical -- shutting down the wrong engine kills everyone). Communicate with ATC, request vectors to the nearest suitable airport.

<Warning> Critical rule: The pilot flying (usually the captain) must verbally confirm which engine has failed before the first officer runs the shutdown checklist. In co-op, both players should point at the failed engine gauge and say "engine one failed" or "engine two failed" before any action is taken. Wrong-engine shutdowns are the leading cause of co-op crashes. </Warning>

Cabin Depressurization

A loss of cabin pressure at altitude requires rapid, coordinated action:

• Both players: Don oxygen masks immediately. This is muscle-memory priority number one. You cannot help passengers if you are hypoxic.
• Captain: Initiate emergency descent. Nose down, throttles to idle, speed brakes extended if available.
• First Officer: Declare emergency to ATC. Announce to cabin crew to secure the cabin and for passengers to don masks. Monitor cabin altitude and rate of descent.

The sequence must be fast. At 35,000 feet, useful consciousness without oxygen is measured in seconds. Practice this drill together until you can execute it without verbal coordination.

Dual Emergency (Compounding Failures)

When two unrelated emergencies occur simultaneously -- say, a hydraulic failure during a medical emergency -- prioritization and parallel work are essential:

1. Captain assesses and prioritizes: Which emergency threatens the aircraft first? Handle that. The medical emergency is serious, but if the aircraft cannot fly, everyone is in trouble regardless.
2. Captain assigns split: "I am handling the hydraulic failure. You handle the medical event and coordinate with the cabin crew."
3. Both players work independently: Trust your partner to handle their assigned emergency. Do not cross-monitor unless asked.
4. Rejoin and cross-check: Once both emergencies are stabilized, come back together and ensure nothing was missed.

Resource Sharing Strategies

Co-op introduces the ability to share workload dynamically, and the best teams use this flexibly rather than rigidly sticking to role boundaries.

Workload Balancing

If the first officer is overloaded -- managing ATC during a busy approach while troubleshooting a system issue -- the captain should take something off their plate:

• Take over radio communications temporarily
• Handle the cabin announcement that was due
• Manage the flaps and gear configuration so the first officer can focus entirely on the system issue

The goal is not to stick to your assigned role. The goal is to keep the combined workload manageable so neither player hits cognitive saturation.

Cross-Monitoring

Cross-monitoring means each player occasionally checks the other's domain. The captain glances at systems while flying. The first officer glances at the flight path while working radios. This is a safety net, not a sign of distrust.

Set a rhythm: every two minutes during cruise, both players verbally confirm one thing from their partner's domain. "Altitude and heading look good." "Engines and fuel look good." This keeps the shared mental model synchronized.

<ProTip> Pro Tip: If you are playing with voice chat, establish a "quiet cockpit" rule during high-workload phases. Non-essential conversation stops. Only operational communication happens. This prevents social chatter from masking important callouts or alerts. </ProTip>

Team Composition and Compatibility

Not every pair of good solo players makes a good co-op team. Co-op success depends as much on complementary styles as on individual skill.

Matching Playstyles

Identify your natural tendencies and find a partner who complements them:

• Aggressive + Conservative: The aggressive player pushes for efficiency, tight schedules, and challenging routes. The conservative player catches risks before they become problems. Together, they are faster than two conservative players and safer than two aggressive ones.
• Big Picture + Detail Oriented: One player naturally watches the horizon -- weather, route, overall strategy. The other watches the instruments -- pressures, temperatures, fuel flows. This is the ideal co-op pairing.
• Calm Under Pressure + Action Oriented: During emergencies, one player stays level-headed and talks through decisions. The other executes checklist items quickly. Both qualities are necessary.

Practice Routines

Build co-op chemistry through deliberate practice, not just playing flights:

• Emergency drills: Load specific emergency scenarios from the Training menu and practice them until the division of labor is automatic.
• Role swaps: Spend one session where you deliberately swap roles every flight. This builds mutual understanding.
• Debrief together: After every flight, talk through what worked and what did not. Be specific. "When the cabin pressure alert fired, I assumed you saw it but you were heads-down on radios. Next time I will call it out."

Communication Tools and Setup

Your communication setup matters. Here is what works best.

Voice Chat Configuration

• Use a dedicated voice channel, not in-game chat if possible. Discord or party chat has lower latency and better quality.
• Set audio balance so voice chat is slightly louder than game audio. You should hear callouts over engine noise and alerts.
• Use push-to-talk during emergencies. Hot mics during a crisis add noise exactly when clarity is most important. PTT also forces deliberate communication -- you think before you transmit.

Visual Coordination Tools

Beyond voice, Dear Passengers provides in-game tools for visual coordination:

• Shared cursor: Players can see each other's cursors on the systems panel. Point at what you are discussing.
• Co-pilot callouts: The AI co-pilot will still make standard callouts (V1, Rotate, minimums) even in co-op. Use these as shared reference points.
• Shared checklists: When either player checks a checklist item, it is checked for both. Use this to track progress without verbal overhead.

Common Co-Op Mistakes and How to Fix Them

Even experienced teams fall into these patterns. Recognize and correct them.

Silent Assumptions

The mistake: Both players assume the other is handling something, and nobody handles it.

The fix: Over-communicate during phase transitions. When moving from climb to cruise, verbally assign: "I will monitor systems for the first five minutes of cruise. You handle the cabin service setup." No task should exist in an ownership vacuum.

Backseat Flying

The mistake: The player who is not flying provides constant unsolicited input on pitch, speed, and configuration. "You are a little high." "Speed is creeping up." "You should extend flaps sooner."

The fix: Unless safety is at risk, let the flying pilot fly. Provide information ("we are 200 feet above planned altitude") rather than instructions ("descend"). The flying pilot decides how to respond to information.

Unequal Participation

The mistake: One player does 80 percent of the work while the other spectates. This usually happens when an experienced player carries a newer one without delegating.

The fix: The more experienced player should deliberately delegate, even tasks they could do faster themselves. The goal is to build the team, not to optimize one flight. Sacrifice some efficiency now for a stronger partnership later.

Integrating AI Crew with Human Co-Op

Your AI crew -- the co-pilot and flight attendants -- still exist in co-op mode. How you use them changes.

With two human players, the AI co-pilot becomes a tertiary resource rather than a primary one. Use them for tasks that are genuinely helpful to offload:

• Routine altitude and heading callouts
• Basic cabin temperature management
• Passenger announcements during non-critical phases

Do not rely on the AI co-pilot for anything that requires judgment. The AI cannot assess whether a fuel imbalance is dangerous or minor. That judgment belongs to the human first officer.

<Info> In co-op mode, you can adjust AI crew autonomy in Settings. Reducing autonomy gives human players more control; increasing it provides more of a safety net. New co-op teams may want higher AI autonomy as a buffer while they build coordination. Experienced teams should reduce it to avoid the AI making decisions that conflict with human coordination. </Info>

Putting It All Together

Great co-op play in Dear Passengers is a skill in its own right, separate from solo proficiency. It requires deliberate communication habits, complementary role definitions, and the discipline to maintain shared awareness even when workload spikes. The teams that excel are not necessarily the ones with the best individual pilots -- they are the ones that function as a single unit rather than two people in the same cockpit.

Start with the SBAR framework and phase briefing habit. Add cross-monitoring and emergency drills as you gain comfort. The result is not just higher scores but a more satisfying experience. There is nothing in gaming quite like landing a damaged aircraft at an unfamiliar airport with your co-op partner, knowing that you both did exactly what needed to be done, exactly when it needed to be done.

For more co-op content, check out our co-op guide section. If you are still learning the basics, our beginner guide and first flight tips will help you build the foundational skills that co-op play depends on.