What the page covers
The phrase Most Wanted Passenger is useful as a player task: a suspicious or dangerous traveler appears, the checkpoint must not panic, and the airport needs a clean response. Public checked sources confirm dangerous travelers, criminals, boss pressure, and final-threat goals, but they do not provide a reliable official stat sheet for a specific named boss. This guide stays inside that boundary.
Use this page when the problem is not basic scan order anymore. If you still lose because normal passengers, bags, or papers feel unclear, start with passenger screening and the checklist. If the high-risk traveler is the first real failure, stay here.
High-risk passenger flow
| Step | Action | Reason |
|---|---|---|
| Confirm | Read the scanner or suspicious signal before acting. | False panic creates checkpoint mistakes. |
| Isolate | Keep the active passenger separate from the rest of the line. | Mixing travelers makes review impossible. |
| Respond | Use guard or team response without abandoning every station. | The airport still needs screening control. |
| Recover | Return to scan, bag, papers, or response state. | Recovery prevents one event from ruining the whole run. |
Solo response
Solo players should keep the response route compact. Handle the dangerous traveler, then immediately rebuild the checkpoint state. Ask what you were doing before the event appeared: scan, luggage, documents, or release decision. Returning to that state is more reliable than trying to remember the entire line from scratch.
Solo warning
If every high-risk passenger makes you forget the current station, your next upgrade may need to support response or speed, but your next practice target is recovery discipline.
Team response
Teams should treat a high-risk traveler as a handoff problem. The response player handles the threat. The line player keeps the queue readable. Bag and document players pause only when their station is directly involved. If every player rushes the same target, the airport can fail even if the target is stopped.
Use short callouts: wanted, response, line held, bags clear, papers hold. The goal is not dramatic communication. The goal is keeping enough shared state that the team can continue after the event.
Spending prep
If high-risk travelers repeatedly end runs after normal screening is stable, choose criminals or boss prep as the bottleneck in the calculator. If they appear while the line is already messy, improve checkpoint flow first. A defense spend cannot repair a route that was already losing passengers and papers.
Failure review
After the attempt, identify the earliest failure. Did you misread the signal? Did the active passenger mix with the queue? Did response pull everyone away from luggage or documents? Did the team lack a line role? Use that answer to choose between scanner, checkpoint, guard role, or boss prep.
FAQ
Is Most Wanted Passenger an official boss stat page?
No. This page uses the term as a high-risk traveler strategy topic because public sources do not confirm a complete stat block.
What should I do first when a dangerous traveler appears?
Confirm the signal, keep the active passenger separate, then respond without losing the checkpoint state.
Is this guide for teams?
Yes. Teams should assign response and line roles before the high-risk event starts.
What if I keep failing after stopping the target?
Review whether the checkpoint collapsed during response. The target may be solved while the airport still fails.