Customer Reviews

A Time to Kill (Star Trek The Next Generation)

5 star:		(7)
4 star:		(4)
3 star:		(1)
2 star:		(0)
1 star:		(0)

 

 

I read "A Time to Kill" as the I did the other installments of this series and came out of it with mixed reactions. Four stars goes to the plot. This has to be one of the more original plots of the trek books to come out this year. It really is an allegory of the times we're living in; a story about a planet with a dictator-like leader who's actions nearly destroy his people and his planet. It also is about the Federation having to face it's own past actions that could lead to a dispute between the Federation and the Klingon Empire with Tezwa caught in the middle.

There are many things which to praise. First, this is a book that features Earth and the Federation political arena there. In the past books, we seem to meet Starfleet's many admirals who run the show. Well, there are appearances by the admiralty- including Ross, Nachayev, and Janeway- but it's the President and his advisor, Azernal, who take the spotlight. While you feel for the President who's caught in a crossfire, you can't help yourself but to despise the character of Azernal. Throughout the book he's playing a dangerous game that may keep the Federation out of more trouble but at the same time will lead to the sacrifice of many things.

This book also features Qo'nos and the Klingons. I'm usually not a big fan of Klingon-centric novels but David Mack works them into a complex plot, choosing not to portray them just as the warriors we know them as but equals to the Federation. Martok is a great contrast to the Federation President; ready to defend the Klingon's interests and avenge the deaths of many Klingons claimed by Tezwa and a Federation mistake. Worf, now ambassador of course, finds himself in a tough position that makes for a great conflict. After rising to a respectful position in the Klingon Empire, having a family once again and friend within Martok, does he betray all of that and give it away to answer a desperate plea sent by Picard?

The Enterprise also takes a beating and lands itself in a position of defending a planet that it also must conquer in order to ensure peace. The Klingons are racing to the planet, ready to destroy it and anything that lies in its path. The entire book is centered around the anticipated arrival of the Klingon fleet. The crew of the Enterprise are turned into commandos, given the task of going down to the Tezwa world and shutting down the dangerous weapons that nearly claimed the Enterprise and did destroy countless Klingon lives. Riker, La Forge, Data and Vale are all deployed on this mission that spans the entire alien world, each has to complete their part of the away mission in order for Picard to oversee a peaceful outcome. All the while, back on Earth, Azernal looks for a way to cover up the Federation's involvement.

I thought overall it was a good novel. It didn't have that usual sci-fi feeling and I felt as if it could easily parallel things we're experiencing in our own lifetime. Prime Minister Kinchawn is definately a villan worthy of the Enterprise crew. This isn't a black and white story. The book ends with one part of the problem being resolved but an entirely new situation being introduced for Picard and crew to solve. Mack also does a great job of integrating other Treks into this story. New Frontier's Danteri play a minor role in the book, Janeway and the EMH mobile emitter tech has a part as well, an ambassador from Bajor is introduced at the end as if to follow up the DS9-Relaunch series and even the Starfleet Corps of Engineers get a mentioning. All of these elements come together to make for a rich and original plot.

There are certain flaws that I felt took away from the near perfect novel. Each scene gets its own chapter, making for a choppy, staccato feeling to the book. I felt as if it could have come off better if these scenes were grouped together in the usual dozen or so chapters. Instead, the book has 66 chapters with scenes cut up and spread out throughout the novel. After getting to the end, there were certain scenes or plot lines that I personally was left not truly understanding or remembering. The reader knows this is going to be a hard away-team mission; it feels drawn out and almost a chore to follow each team throughout the book and read about all of their actions. I'd rather have seen the Qo'nos scenes extended. While in other books the featured crewmember gets their time to shine, Worf seems to be reduced to a guest appearance. I also was left questioning Worf's actions. In Deep Space Nine he seemed to have made many sacrifices to reclaim his Klingon honor and heritage. Suddenly in one book, with one simple call from Picard, he hesitates for a moment before setting out to destroy his Klingon honor and acclaim? He seemed more human after living among the Klingons since the end of DS9 than he did when portrayed on Deep Space Nine and his Next Generation days.

Something else that bothered me about the book was that there were some character simply pushed into the background. The "A Time to..." series had done a great job of finally finding a place for Beverly Crusher and Deanna Troi on the Enterprise. They weren't just the ignored and flat characters they were in the actual show but important members of the crew who could go outside their usual duties and offer something to the plot. Crusher only appears once or twice but all the build-up she had been given during the start of the series and through the last novel, "A Time to Hate," seems to have fallen off. She's just a doctor who may have a job. She's avoiding Picard and apparently hasn't been speaking to him as they usually have. I find that hard to believe based upon how she was in Next Generation and in this series. Troi, who ended "Hate" with questions about her own career and having really contributed to the Delta Sigma situation is stripped of all that made her a great character and is left rather stale. She's just the counselor and suddenly she's crying and an emotional 1950s lady in distress at the end. To me, these things were unfortunate. Why not find a way to work the entire crew into the fold as the past books have?

This book also felt as if it didn't fall into the rest of the "A Time to..." series. Perhaps it's the fault of the setup of the group. We don't hear how the admiralty and Starfleet Command reacted to Picard's actions at Delta Sigma in the last books. We just skip ahead to this new mission without much mentioning of the events of past books. Even when meeting with the admirals, I felt as if that entire "A Time to be Born" had never happened. From how it was being hyped, it wasn't something that was easily going to be forgotten. Nachayev, Janeway, and Ross who have all been involved to some degree in the Enterprise's "A Time to..." events come off as if they have amnesia and this is just another mission worthy of the Federation's flagship. Also, the La Forge and Data plot of the resource situation, something rather big and important, isn't even given a mentioning. "A Time to Kill" seems to have set off on its own, like an unruly child, being a tad bit rebellious and setting itself apart from the rest of the group. That's good in a way because it makes for an interesting novel that's above average. It's bad in that it gives the "A Time to..." series a rather interupted feeling.

This review though is bases solely on this novel. The next in the series, "A Time to Heal," is a continuation of this novel and may deal with some of the short commings I personally felt this novel had. Alone, it is a good novel though and worthy of your money and time. I don't feel as if reading the past novels are really required for this installment but it certainly wouldn't hurt.

As I have read every other entry in the "A Time To..." series, with the exception of the forthcoming novel: "A Time for War, A Time for Peace," (October 2004) I can honestly say that "A Time to Kill" is the best story, so far.

Well-written and fast-paced, little time is wasted on the introspection of the main characters. Instead, the plot quickly opens, revealing a new, post-Dominion War Federation that can no longer disguise its misdoings beneath the guise of "Patriotism."

Assigned a mission they are not even expected to accomplish successfully, the crew of the USS Enterprise-E must, and does, endeavor to to save the lives of billions of innocent (and not-so-innocent) people from annihalation.

I thoroughly enjoyed this book because it dared to explore the notion that the (UN)ited Federation of Planets is concerned firstly with its own survival and secondly with maintaining its apparently sterling reputation. It was also nice to see Worf in action again.

I give this book Three Stars because it outshines every other title in this series, including its sequel "A Time to Heal," which is a decidedly undisguised criticism of current world events. The reason I didn't rate the book higher is twofold: predictability and continuity.

Predictably, as with every TNG storyline, Picard and his crew are an incredibly moral bunch that NEVER have bad days or commit transgressions of the "Prime Directive," even when it seems that half the crew is dying for no apparent reason.

Continuity in the bloated Star Trek pantheon has become as tenuous as it is in the Star Wars universe. With so many different authors writing so many different stories, it has become difficult to keep track of everyone and everything. Primarily, I was/am confused about the roll of the Corps of Engineers (except as a vehicle to keep the "Scotty" character viable). And I am confused about the shadowy spy organization mentioned in both "A Time to Kill" and "A Time to Heal." Who are they? What are they? Why are they? As it is overly presumptuous to assume that every reader has read every book and series, I think it is the duty of a responsible author to engage disparate thematic elements, not simply evoke them.

Additionally, I am always amused by the tactics Star Trek writers employ to negate the technological advantages of Starfleet. How can a society with faster-than-lightspeed vessels equipped with energy weapons/shielding, and matter transportation and replication capabilities, be constantly rendered essentialy useless? If the Federation and its Starfleet just concluded a massive war with the Dominion on the heels of numerous conflicts with the Borg, Romulans and Cardassians, where are their shock troopers? Where are their dedicated combat warships? Where are their fleet defense fighters/shuttles? How can any force so strategically impotent defend the interests and sovereignty of an interstellar government?

Star Trek is a great and wonderful world of imagination and insight. But it is beginning to crack under the weight of its own expansiveness. I hope that Paramount allows new authors to take the franchise in whole new directions (i.e., New Frontier) before disenfranchised fans begin to feel that the Star Trek saga is no longer viable; that it is A Time to Move On.

This book starts with a seven page recap of the series, and then plunges right into an incredible political intrigue. At one-third through the book, where previous books of the series are ending their recaps, it switches over to commando missions. The pacing never lets up. The descriptions are very clear and the action scenes are very dramatic and generally well done. The characterisations start out a bit flat, but are excellent during the commando sections. The plotting of the story is remarkable. We follow six commando teams, plus asides to the Enterprise, Qo'noS, Earth and other places. I do not think I have read a book that follows so many characters at once. I certainly have never read a book that does it so well, completely clear about who is doing what. On a minor note, there are references to many events since the Dominion War, including from books that have not been released yet, seamlessly worked in. Also, I finally get an explanation of the Federation politics that has underlain the series. That is really interesting, but I do not know why they did not present it earlier. Last, the scope of this story is huge. If the Enterprise crew fails, a war to the finish with the Klingon Empire is an absolute certainty, and the characters never forget it or allow us to. I have only one complaint. Koll Azernal is neither devious nor capable enough to sustain his plots. He probably would have come unglued long before this. That does make me look forward even more to the next book, though, as then the real master schemers should get into the action. It is worth mentioning at this point that this book, unlike previous books in the series, is a complete story in itself. The next book is also the next story. Obviously, I give this my highest recommendation.

The "shadowy spy oprganization" (aka "Section 31) in the "A Time To.." series mentioned in the review below did NOT originate in any novel, it first appeared in the televised DS9 episode "Inquisition".

As for the 'bloated' continuity, I really don't see it as being a problem in the current Star Trek novel universe. The continuity displayed is more in simply keeping consistant with previously published novels rather than being dependent upon them (as contrasted to the Star Wars novel universe and its NJO, which while entertaining, was heavily dependent on previous novels).

As for David Macks A Time to Kill/Heal duology, I thought it was a brilliant and gripping tale which shows an accurate parellel to current world events. Trek has always been at its best when it comments on the state of the world WE live in.

The conclusion of the series, "A Time For War, A Time For Peace" by Keith R. A. DeCandido is much better capstone for the TNG crew than the shaky 'Nemesis' feature.

I think if Paramount hired the current batch of Trek novelists to do the shows and movies (as opposed to the hacks who currently do Trek for Paramount) Trek would be in a much better place than it is today.

This is the seventh book in this series and the first of the two written by David Mack. I am not sure why I liked this novel but it is getting the highest rating I can give it.

This novel is a step into the ability of the Enterprise crew to pull off true miracles. They are given a mission that they are expected to fail at but with little time, less help and incredible levels of luck, they pull of this feat of greatness and surprise.

The real power of this story is the portrayal of the Federation. If you enjoyed the Deep Space Nine episode `In the Pale Moonlight' then you will love this novel.

"A Time to Kill", the seventh installment in the current "A Time to..." series of Next Generation novels, weaves together for the reader a complex storyline, enthralling characterizations, deep convictions, and heartfelt emotions.

Focusing around a rising problem on the neutral world of Tezwa, the United Federation of Planets is rushing to prevent a disaster that could spread into a quadrant-wide conflict. In an effort to cover-up for possible treaty breaches in the past, the Federation now finds itself stuck between the Klingons, Starfleet, and the people of Tezwa, each of whom could uncover the secrets that might plunge the Alpha Quadrant into a new and sustained conflict that would cost countless lives.

David Mack is a relative newcomer to Star Trek fiction, having previously penned the "Starfleet Survival Guide" and a reference to the "New Frontier" book series. His previous fictional works have both been in the "Starfleet Corps of Engineers" series. "A Time to Kill" and its follow-up "A Time to Heal" represent his first full-length paperback novels, and Mack comes to the table with a tour-de-force read that I simply couldn't put down.

At the risk of sounding like a crazed internet gusher, I was utterly stunned at the magnificent accuracy with which Mack was able to write the beloved crew of the Enterprise-E, as well as Worf and Martok. As each character appeared in the novel, I could literally see, hear, and experience this novel like it was a movie or television show.

Mack's story is deeply complex, and to truly delve into the complexity needs to be avoided for this review, for to truly reveal the nature of the complexity would be to spoil the sheer joy of reading this novel. Mack goes to great lengths to make this story a fast-paced thriller, and succeeds with short chapters that make it easy to follow the many plots that meet within the covers of this book.

Seeing the struggles of power in the Tezwan capital, the political machinations behind the scenes in their planetary council, and seeing the sacrifices of good Starfleet officers has never been so palpable or enjoyable in my experience of reading Star Trek novels. This novel has a soul all it's own, one that will draw the reader in and that simply won't let go.

David Mack makes a worthy addition to the roster of novel-length Star Trek fiction writers, and has earned a nearly flawless review from me.

This is a Star Trek novel for the ages, and one can only hope that "A Time to Heal", Mack's follow-up (due within the month) will bring the story to the boiling head it needs to enter into October's finale for the "A Time to..." series, "A Time for War, A Time for Peace", penned by Keith R. A. DeCandido.

David Mack's entry into the A Time to... series of books opens up a lot of political intrigue that could shake the Federation to its core. A Time to Kill is another outstanding entry into this series. Marred only by a mildly "everything works out for the best" atmosphere that doesn't quite fit the difficulty of the Enterprise's mission, Mack still gives us a stellar book. The style fits the situation perfectly, making the reader read "just one more chapter" until the end of the book is reached.

Federation president Min Zife has a problem. During the Dominion War, the Federation sold advanced weaponry to the ruler of Tezwa to establish a fallback option in case the war went badly. Unfortunately, the ruler of Tezwa, Kinchawn, is a power-mad zealot who is willing to go to war with the Klingons to satisfy his own material needs. This would be very bad for Zife, as any war between the Klingons and Tezwa would reveal the weapons on the Klingon doorstep, sparking a war between the Federation and the Klingon Empire. Unfortunately, Kinchawn uses the weapons to wipe out a fleet of Klingon ships and almost takes out the Enterprise as well during a diplomatic mission to calm hostilities. The Klingons want blood, and the Enterprise is sent to try and resolve the crisis before the Klingons can discover what's there. Captain Picard must find a way to neutralize the weapons as well as neutralizing the Klingon fleet that's been sent to conquer Tezwa, all at the same time. How will he do this? It will take coordinated attacks to prevent the guns from firing on Tezwa, as well as a little help from Ambassador Worf on the Klingon homeworld to stop the Klingons. If one thing goes wrong, the Federation will be plunged into a war that will weaken both parties, leaving everything open for the Romulans.

A Time to Kill is quite intricate, almost too much so. Enterprise personnel must disable all six guns at the same moment, and Worf must come through at the same time. If even one thing goes wrong, everything goes wrong. Yes, the assault teams have their problems and setbacks, causing what tension there is in the novel, but everything ends up being a little too convenient. One thing that doesn't quite work out leaves a plot point for the next novel, but otherwise it feels a little unrealistic. I felt this would be the case when the situation was set up, so by the time it actually happened, I had grown used to it and went along for the ride. Thus, it's not a major problem. It's just something that's mildly annoying at the time.

Otherwise, A Time to Kill is a non-stop thrill ride, full of tension. The book has very short chapters, adding to the intense feeling. The chapters jump from one assault team to another, back to the Enterprise, to the President's office, as well as to another secret organization that's watching all this from elsewhere. There is a lot at stake, which just adds to the tension. It's almost like a music video, never giving the reader time to relax. The only parts that seem to drag a bit are the ones on Qo'nos, but that's only in relation to the rest of the book. I found Worf's attempts to do what Picard needs him to do to be duller than the events on Tezwa.

The book is very plot-driven, but Mack does do a good job with the characters as well. Dr. Crusher is still considering the offer to assume the position of Head of Starfleet Medical, and she's hurt that Picard hasn't come to her about it. Picard, meanwhile, is hurt that Crusher hasn't come to him to talk to him about it. This does seem a little bit "high school," but it doesn't come out that way in the book (well, not very much). Instead, the book examines their relationship as it has gone throughout the years of the television series and the movies. It's actually quite effective.

Even better is the characterization of the assault teams. We get to see a lot of new characters in action, and we're given some meaty looks at them. Most impressive (though a bit clichéd), is Razka, a reptilian non-commissioned security guard who acts like most sergeants do in war films. He's experienced, he's gruff, and he gets the job done. He is stereotypical, but I still found myself drawn to him. Maybe it was the scales. The other security officers are also given a lot to do. One thing this series has been wonderful with has been the security officers. They are not just nameless redshirts, and they aren't treated that way, either. We are starting to really get to know some of them, and while some of them die, some of them don't. Since the characterization of them is so good, it actually hurts when one of them does die.

One annoying aspect of characterization, however, was Zeitsev, one member of the mysterious organization that is following all of these events. His superior officer, a Vulcan, is evidently very attractive and he has a crush on her, despite her being a lot older than he is. This crush does nothing in this book except detract from the character. I hope it becomes a plot point somewhere in the next two books, as otherwise it just stands out as a grating character trait with no purpose.

This entire series has been a slow starter, but the last three books have been wonderful. They keep the reader coming back for more, wondering what's going to happen next. The end of A Time to Kill leaves a nice cliffhanger as well as a possible opportunity to comment on current events. We'll see what A Time to Heal gives us. I know I'm reading them as fast as I can.

David Roy

A Time to Kill is most definitely head and shoulders above the previous six "A Time To" novels. The book is dense, but also moves at a lightening quick pace.

In many ways, A Time to Kill is more how I have always envisioned Trek: decisions made at the very top and bottom of the chain of command have repercussions upon each other and create a more epic feelings. The leaders of other galactic empires have been important characters in Trek. Why hasn't the Federation president? Here we finally get to see how the Federation works from the top executive down to the lowest noncoms onboard the Enterprise.

The story itself is just far more large-scale and important than I've considered the stories at the center of the previous "A Time To" books. Those felt like they were spinning their wheels. A Time to Kill hits the ground running. The interstellar incident created on Tezwa was endlessly fascinating and each side's reaction and behavior was what we would expect. The book culminates in a heavy dose of covert ops and Mack (and editors) effortless cross-cuts between them to keep a steady pace.

Continuity bits were sprinkled about to create just the right amount of effect to remind us when the books are specifically taking place. Character work is across the board pretty good. I especially like Data's conundrum of trying to remember emotion as if from a dream. The plot seamlessly works in Will Riker's growth from throughout the "A Time To" series and doesn't call attention to itself. Like when it becomes readily apparent that Will just may be feed up with away missions and is all the more incentive to move over to the Titan. However, Christine Vale (and now Jim Peart) still draw a complete blank in my mental picture beyond their dedication to the job.

There's very little to nitpick in the book. One scene that sort of stood out for me was how the Enterprise seemed to effortlessly enter the Tezwan atmosphere and fly right over the city. Never got the impression before that the Sovereign's could fly so low to a planet surface. Secondly, "scanning for bio-signs" of particular species has become standard procedure anymore, so I'm curious as to why they couldn't just scan for Riker when he didn't check in and beam him up.

Probably best of all about A Time to Kill is that it's probably the first "A Time To" book that also felt pretty self-contained and could be read on its own. The other books have not felt that way.

Now all that said...there is the discouraging trend in Trek literature lately to make the Trek universe as grungy and depressing as real life that seems so overt and self-conscious as to border on exploitation. There's a heavy dose of cynicism in the latter "A Time To" books where the tiresome cliche of government corruption makes the Federation just as villainous as the Romulans or whomever. The corrupt admiralty was already a worn out cliche in the Trek universe, so I guess the writers and editors have decided to move on up the chain of command. So while I can really enjoy the book on its own, I really don't like the pattern that A Time to Kill started that progressed in the sequel.

This is an excellent story, better by far than any of its predecessors in this miniseries. It is fast-moving, full of action, the characterizations are excellent, and the plot is not simplistic. I'm even willing to forgive it the fact that it ends on a cliffhanger, as that cliffhanger is only a subplot; the primary plot is, in fact, wrapped up nicely within the one book. This is how continued stories SHOULD be continued.

Have purchased books from Amazon for two years, am always pleased with their system of delivery and quality of product