So, after my less than entirely satisfying encounter with late-period Enterprise and the serialised storytelling which seemed to define the series at that point, it seemed sensible to check out a much earlier, non-serialised episode and see if this was any more to my taste. (I know I have looked at a couple of first-season episodes in recent weeks, but not with any particular intent beyond just watching the show with my critic’s socks on. Some people have a critic’s hat, I have critic’s socks.) I ended up watching the first ‘normal’ episode to follow the pilot: Fight or Flight, first shown in October 2001 and written by the show’s creators, Rick Berman and Brannon Braga.
The episode kicks off with another of those peculiar non-grabby cold opens which are practically part of Enterprise‘s format: Hoshi visits the sickbay to look in on one of the animals genial Dr Phlox is looking after. Then again, part of the premise of the story is that the Enterprise has been out in space for a couple of weeks and nothing worth mentioning has happened, beyond discovering a slightly poorly slug, so it’s a bit difficult to see how else they could have pepped things up a bit.
Various things are used to establish the fact that this is still a ship and crew that is coming together: Phlox still treats the humans as specimens to be observed, there’s an odd squeak under the floor of Archer’s room, the torpedoes won’t shoot straight and T’Pol is a mood hoover in whatever room she happens to enter. Everyone (apart from the Vulcan) is getting frustrated by the lack of activity and is keen to get on with some proper exploring.
They get their chance when they come across an alien cargo ship, apparently derelict in space (the Easter egg in the script is that the aliens eventually turn out to come from Axanar, which later – which is to say, back in the 1960s series – had a medal named after it, not to mention a fan-made Trek movie which ended up causing immense ructions between the Trek rights holders and creative fandom). Despite T’Pol’s declaration that the Vulcan thing to do would be to let well alone and carry on with their original course, Archer goes aboard and insists that Hoshi comes along to translate, despite the fact she gets claustrophobic in an environment suit. The ship seems abandoned, until the boarding party discovers some odd machinery hooked up to the corpses of fifteen or so of the original crew, who have been murdered and strung up from the ceiling…
Fight or Flight does do a good job of establishing that the Trek principles that were in effect throughout the series set in the 2360s and 2370s no longer apply here in the 2150s: Enterprise is one small ship slowly heading out into a largely unknown galaxy, without the immense power of Starfleet and the Federation to back it up. There is much more of a sense of peril, which is most effectively communicated by the fact that Archer’s initial response to finding the dead crew is to pull his people out of there and warp out of the area as fast as possible.
Needless to say, they go back, but run afoul of the aliens who murdered the other ship’s crew, and here the episode’s A-plot and B-plot rather-too-neatly intersect, as you might expect from a Berman and Braga script: Hoshi has been struggling all episode with the realities of exploring the unknown, and has been contemplating asking to be taken home so she can return to a purely academic environment where she is more comfortable. But, needless to say, when the climax arrives, she conquers her self-doubt, develops the ability to speak an alien language practically spontaneously, and saves everyone from the bad guys. I suppose it makes up for the fact that most of her earlier scenes made heavy use of an extended metaphor where she was compared to a sickly mollusc.
It’s all very glib, pat, and predictable, and it feels like it’s taking up bandwidth that could have been more profitably used to develop more interesting elements of the story: the murderous alien villains seem quite promising, but turn up too late to do more than be generically threatening before they are disposed of, for example. However, for me the really interesting development of the episode is one which barely receives any emphasis at all.
To begin with, Archer and the other human characters are just keen to start exploring and meeting new alien species, which is fair enough: this is the sort of thing which a lot of Trek pays lip service to, although (if we’re going to put on our pedantic socks) only a comparatively tiny number of episodes, across all the series, revolve around genuine exploration. But exploring only goes so far in terms of creating conflict and drama, and so there has to be a little bit more to it than just being menaced by natural phenomena and hostile aliens – it can’t just be scientific observation, there has to be an element of virtuous self-expression to it as well. Starfleet ships don’t just zip around looking at stuff, where possible they get involved and try to do the right thing – you could argue that the whole notion of the Prime Directive is, in dramatic terms, just a device to increase the conflict involved in this kind of situation.
The shift in Archer’s attitude from ‘let’s explore!’ to ‘let’s explore virtuously!’ thus seems to me to be what this episode is really about, but – in what seems to be another key Enterprise trope – rather than handling it through a dramatic scene, with different characters arguing their points of view, and the actors getting a chance to shine, Archer just thinks about it at lot, mostly off-camera, and eventually announces his decision to everyone else. It is in the failure to provide these key moments of character, tension and drama that Enterprise seems to consistently fall down: it seems to treat the resolution of rather hackneyed character arcs, most of them limited to individual episodes, as being of higher importance. Having hit upon a successful formula during the making of TNG – most latter episodes are built around a single character tackling a particular issue in this way – they seem to have been reluctant to abandon it, and it’s this which keeps Fight or Flight from being a more satisfying episode or reaching its full potential as anything more than meat-and-potatoes Trek.
Leave a Reply