“Off Hour”

Star Trek: Strange New Worlds puts the crew in a crisis situation with a tight countdown to certain death.

Ticking clock survival scenarios on damaged starships are a familiar Star Trek setup. Episodes like The Next Generation’s “Disaster”, Deep Space Nine’s “Starship Down”, and Strange New Worlds’ own “Memento Mori” show how effective this structure can be: strip away resources, impose a deadline, and force the crew to perform under pressure. It’s a reliable foundation for tension, although this episode doesn’t always give that tension the weight it needs.

This story begins with an accident: the Enterprise stumbles into a wormhole and accelerates to a speed the ship can’t survive. It builds on the idea of space as a place of unpredictable danger raised in “The Griffin Incident”. Star Trek often celebrates the thrill of encountering the unknown, but sometimes the unknown is lethal. Most of the characters would argue that exploration’s rewards outweigh its risks, yet that belief is hard to hold when they’re facing destruction with no clear way out.

The danger becomes most vivid through Scotty, who best embodies the less enthusiastic view of their situation. His anxiety is well founded, since he’s already lived through the loss of a ship and crew. He carries that grief with him and brings it to the surface whenever lives are at risk. He doesn’t want to face that kind of loss again, and the weight of the crew depending on his ability to fix the problem only intensifies his fear of making a fatal mistake. He’s skilled and creative, but the trauma of his previous command has shaken his confidence.

His knowledge and improvisational skill are put to the test, throwing a series of unconventional problems at him while he works without Pelia’s guidance, and it explicitly frames this as the beginnings of him becoming the miracle worker he’s known to be. His confidence wavers, but his knowledge never does. Every challenge prompts an almost immediate solution, and he only needs help clearing the obstacles that stop him from carrying it out. It’s strong character work that highlights his creativity, but if this is meant to be an origin story, it would be more satisfying to see him encounter gaps in his knowledge as well as his confidence. Realising there are things he doesn’t yet know, and resolving to bury his nose in every technical journal he can find, as fans would expect, would give the arc more weight. As it stands, the episode’s message is slightly muddied by how effortlessly he solves each problem.

Scotty does learn an important lesson about being an engineer on a starship. He vents his frustration to Pelia about the Enterprise ending up in this situation with almost no warning, and he feels betrayed by a ship that’s supposed to keep its crew alive. Pelia reminds him that every ship glitches, but they’re also capable of miracles. It’s a poetic way of saying that a starship is more than its technical manuals, and that a great engineer has to understand what lies beyond the stated limits. She urges Scotty to trust his instincts rather than rely solely on the specifications, because that’s what separates a competent engineer from a miracle worker.

He takes Pelia’s advice to heart and confidently states that the Enterprise will hold together when they cross the warp threshold, even though the technical specifications say it won’t. When they make the jump, he touches the wall to show he’s trusting his instincts and accepting that the stated limits are conservative. It’s also a moment of connection, treating the Enterprise as something more than machinery. After the crisis ends, he repeats the gesture as if thanking the ship for holding together when it mattered. It’s a strong piece of development that moves Scotty toward the highly skilled and outwardly reckless Chief Engineer who knows exactly how far he can push the technology.

The episode also gives Chapel a parallel moment of pressure, and the other main character story belongs to her. Her commitment to the Enterprise is challenged when M’Benga reveals that he’s considering leaving. His reasons aren’t yet clear, but the focus is on how Chapel responds rather than what it means for him. She tells him she’d have to leave too, since she doesn’t believe she’d thrive under a different Chief Medical Officer. M’Benga urges her to think it over, pointing out that she’s well liked and respected where she is. He also calls her out for keeping one foot out the door, shown by her never requesting that her posting on the Enterprise be made permanent, something the show hasn’t addressed until now.

This makes sense given what has already been established about Chapel. She’s been shown to avoid commitment in romantic relationships, Spock notwithstanding, so it’s reasonable that the same attitude would shape her career choices. She tells M’Benga she’s keeping her options open, which leads to an argument that forces her to confront why she’s so reluctant to settle down.

There’s a frustrating trend on this show where characters question their place and ultimately decide they’re exactly where they need to be. It has happened with Uhura and Ortegas. Uhura spent time considering her potential and where she could best fulfil it, only to conclude that the communications station on the Enterprise is all she needs. There’s nothing wrong with that, since people choose career paths for all sorts of reasons, but there’s a clear sense that she could do far more than that role allows. Similarly, Ortegas wonders what lies beyond flying the ship and ends up accepting that flying the ship is what she’s meant to do.

In Uhura’s case, it works as meta commentary on Strange New Worlds being a prequel. Her future is fixed, so there’s only so much the show can do with her, and she has to end up at the communications station. That could have been handled by introducing her in a different context and letting her arrive there organically, but the show began with her already in that role, and her limited development was simply accepting it. Ortegas, by contrast, has no canon expectations, so she doesn’t have to conclude that flying the ship is her destiny. There’s nothing wrong with her feeling content with that, but it’s unsatisfying to watch characters resist progression when the story spends time on their doubts.

Chapel is similar to Uhura in that her future is known, so she has to end up as a Nurse when this show concludes. I’ve often pointed out that Strange New Worlds behaves more like a reboot or alternate timeline than a strict prequel, and Chapel is the clearest example of that. She does far more than act as a Nurse. She’s a researcher who leads expeditions, runs her own experiments, studies advanced medical procedures, and pursues a wide range of interests that go well beyond the role she’s meant to occupy later.

She is a much richer character here than she ever was in The Original Series. In that show she occupied a specific role because she wasn’t a main character, but that limitation doesn’t apply in Strange New Worlds. This version of Chapel could easily progress to succeed M’Benga as Chief Medical Officer. Calling her a Nurse doesn’t do her justice when her knowledge and skillset are so wide ranging. Keeping her in that role runs counter to how the show has portrayed her. She’s ambitious, curious, and open to exploring almost any field before deciding where she belongs. In “Subspace Rhapsody” she sang, “My future is infinite. My possibilities are endless,” and since the characters were singing their truth, it’s clear she sees herself as capable of anything she chooses to pursue. With that in mind, a valid counterargument in her discussion with M’Benga would be that tying herself to the Enterprise might hold her back. She never makes that argument and instead asks Pike for a permanent position, which becomes another example of a character being offered the chance to grow only to resolve to stay in their lane. It’s frustrating because it actively prevents the characters from progressing.

When M’Benga is pinned by a heavy table and can’t be treated, Chapel refuses to accept it and stays with him until she’s exhausted every option, including the ones she hasn’t thought of yet. The moment personifies the argument by rendering M’Benga unable to move while Chapel remains at his side, even when it puts her in danger. In this case staying means she’ll likely die with him, but she still refuses to leave. It reinforces her loyalty, which was never in doubt, but it also suggests that Chapel is being held back by that loyalty and will never become all she can be. That doesn’t mesh with what’s been established, since she did leave to join the research fellowship before returning months later. M’Benga doesn’t hold her back from pursuing opportunities, so there isn’t strong grounding for this conflict in the first place.

The episode isn’t interested in exploring Chapel’s reluctance to commit, as the focus shifts to problem‑solving rather than forcing the conversation to play out. Her resolution doesn’t come from any meaningful examination of why she’s hesitant to stay on the Enterprise, so it lacks weight when it arrives. The problem‑solving itself works well and is a great showcase for Chapel’s resourcefulness and unconventional thinking, but as support for the arc the episode gestures toward, it falls far short of what was required.

Scotty and Chapel’s roles in the crisis sit against a backdrop of rising danger, and the episode’s disaster movie structure remains a very effective race against time experience. The stakes escalated rapidly yet organically, and the constant countdown made the urgency unmistakable. Keeping the focus on the bridge and the mess hall, where decisions were made and carried out, ensured the tension stayed centred on the right characters. It was always clear who needed to act and what they needed to do. Problems and solutions were threaded through the episode well, with most solutions failing or creating new complications, such as the probe exploding before it could gather useful data or the Ion Pod information having to be conveyed by mind meld. This kept the situation chaotic while the goal remained clear, and it allowed the characters, especially Scotty and Chapel, to shine as they used their skills and training to work through the onslaught of problems.

The disaster structure is strong, but the episode struggles to give those escalating stakes the weight they need, which weakens the impact of the resourceful problem solving by making their efforts feel less consequential. Dialogue confirms that there were deaths, but the loss is never truly felt. Pike is incapacitated early on and returns to command with nothing more than a bandaged hand, and there’s no suggestion he’s in any pain. Combined with the unacknowledged deaths, risk making the experience feel consequence free. It may have been a more compelling showcase for Ortegas if she’d had to run the bridge while Pike was out of commission, with caring for him becoming an extra problem to manage, since it would have given the crisis a human cost and made his injury matter.

These smaller moments point to a larger structural weakness, where the episode introduces consequences that should escalate the tension but resolves them before they can matter. There are some situations that could have been handled better. The increased gravity in the mess hall is solved instantly, when it could have built slowly over several scenes before becoming life threatening. That would have literally given the situation weight and added to the urgency. Una’s compound fracture initially seems like a meaningful consequence, but once she’s bandaged up it’s never mentioned again. There was an opportunity for this to highlight her command style under pressure as she made tough decisions that might send people to their deaths. Instead, she’s absolved of that when Spock and La’an volunteer for the dangerous task of crawling along the outside of the ship while being battered by radiation.

All of this leads to the episode’s weakest choice, and the solution to the problem is underwhelming because it relies on what is essentially magic. Chapel talks about a theoretical particle that may exist in abundance under the conditions they’re trapped in. If it exists, it can refuel the Enterprise and heal M’Benga’s lethal injury. It’s far too neat as a resolution and isn’t earned because it’s introduced through meaningless technobabble. For an episode that had been strong in its portrayal of skill, intelligence and resourcefulness, it feels out of place to end with a fix that arrives without effort or insight. Scotty and Chapel don’t need to do anything to earn the solution, so it falls flat.

The episode also raises a thematic thread that could have deepened the story, bringing up the recurring reference to the crew feeling fatigued and overworked as Pike pushes them from one mission to the next. Chapel mentions it in her log, and before disaster strikes the main characters are looking forward to a weekend off. It was previously established that Pike is throwing himself into work to avoid processing his grief. It’s an understandable reaction, but it has a knock‑on effect of the crew becoming overworked and resentful. This could have been a strong plot thread about grief affecting everyone around you and becoming a suffocating experience, but it’s reduced to occasional mentions and quippy remarks rather than anything meaningfully explored. It has a lot of potential and could have helped flesh out the Enterprise as a workplace with all the positives and negatives that come with that. The show is generally lacking in conflict, and having the crew at odds with Pike over his current command style would have added welcome friction. It’s another example of the episode raising a meaningful consequence and then refusing to follow through on it. It didn’t need to reshape the season, but it did need to matter in a way the episode never commits to. As it stands, it doesn’t qualify as a plot thread. It’s present, but it has no weight.

---

Verdict

An engaging episode that lets the ship’s unpredictable danger forge Scotty and reveal the instincts that will come to define him.

We’d love to know your thoughts on this and anything else you want to discuss. You can find us on Facebook, Twitter, BlueSky and Discord or just leave a comment in the comment section below. You’ll need an account for Disqus but it’s easy to set up. Don’t forget to share your rating in the “User Review” box.