Taking a Risk...

I said a few days ago that I was facing a difficult decision, to choose between 'Rocket Dawn' and 'Blood of Patriots', but after a lot of thought, I've finally made up my mind. I'm going to write both of them. Meaning that 'Rocket Dawn' will now be out in early April, 'Blood of Patriots' in early May, and the next Alamo, 'Spell of the Stars' in early June. (Provisionally – very, very provisionally – I've pencilled in Vae Victis I for July and Polaris 2 for August, but that's far too far ahead for me to plan at the moment.

My reasoning in the end was simply this. Creating something new is inherently more difficult; when writing an Alamo, there are so many things I've already done, creating the major characters, the details of the setting, and so forth – which means that a lot of the hard work is already behind me. (And yes, this is a very good reason to write a long series – though to be absolutely fair, that can have problems of its own when you are dealing with large amounts of canon.)

In any case, I rate it as likely that at least one of the books will end up falling by the wayside. This will be the second try at Rocket Dawn and the third at Patriots, so I'm hopeful that I'll do better than I have in the past, but either of them can be replaced with an Alamo if the need arises. In a perfect world, I'll write both of them. (And by God, I need to get Rocket Dawn out of my system if nothing else.) Otherwise, Alamo is advanced to May, and things move on from there. Why Rocket Dawn first? Largely because I have that plot firm in my head, but I'd like more time to work on Patriots – and incidentally, on Alamo 25 as well.

So, let's talk about Rocket Dawn. First of all, I'll say that this will be different to any book I've ever written before, and that's a good thing. It should stretch me in new and interesting ways, and I think that's extremely important. Technically – sort of – it represents a very early stage in the Triplanetary universe, chronicling the first attempt at starflight, though the book completely stands alone, and about the only thing I'm using is some of the concepts of the hendecaspace drive. (Which works a little differently here, but I'll remind readers that the first – essentially broken – take on the hendecaspace drive did work differently. Lots more options, at the cost of a lot less reliability.)

All of that is just set-dressing, though; this is to be my homage to the films and books that did so much to promote spaceflight in the 1950s and 1960s, Destination Moon, Conquest of Space, the old Von Braun/Willy Ley dreams from that era – and even years later, I still pored over them as a kid, and still longed for the future they promised. Frankly, I still do today. I want my moonbases and space stations, darn it! And the less said about the flying cars, the better!

Rocket Dawn is set in a 2032 that I desperately hope does not exist, but fear for. A series of Challenger-scale disasters a decade before killed off manned spaceflight, private access to space dying before it could be truly born. Now only satellites orbit the Earth, the International Space Station de-orbited by its last crew, Russia forced out of the game with a faltering economy and China withdrawing when it was apparent there was nobody to challenge. The tattered remnants of NASA monitor failing space probes, hoping for a new chance.

And out in the Nevada desert, at an old rocket testing site, a maverick Air Force Colonel, the last astronaut recruited by NASA before the manned space program was cancelled, has gathered together the resources and personnel for one last, desperate throw of the dice, masterminded by an astrophysicist shunned by the scientific community, who believes that he has uncovered the holy grail of space travel – the secret of faster-than-light travel. From the backwater town of Dry Wells, Nevada, the last astronaut will finally rise to the heavens...

What does he do again?

When I first began work on the Battlecruiser Alamo series, one of the most important steps was to come up with a crew roster, at the very least, a list of officer roles and responsibilities. (And as I warm up to begin work on Starcruiser Polaris, I'm doing this all over again in a slightly different way, but I'll get to that in a future blog post.) I think it critical to make a science-fictional universe seem to be real, and that, in this case, meant extrapolating into the future current trends, as well as using a leavening of logic to smooth things over. I've thrown around these terms often enough that it seems sensible to actually define them for the benefit of the reader; hence this post, which looks at the key officer roles on a starship in Triplanetary service, essentially a list of job descriptions. Naturally, this is taken from the point of view of a capital ship, a battlecruiser or a battleship – I've had most experience with ships of this type...

Starting at the top, we deal with the Captain, the commanding officer of the ship. Capital ship commanders, especially battlecruiser commanders assigned on long patrols, have extraordinary latitude in decision-making, given the extensive communications lag. When operating months from home, it isn't practical to contact home; hence a capital ship commander is empowered to promote officers, or even to grant commissions in rare cases, and to enlist new crewmembers if necessary. (This is a holdover from the Interplanetary War, and perpetually resisted by the Admiralty; nevertheless, it is an ability that capital ship commanders will attempt to keep until the end.)

A Triplanetary starship commander, on the frontiers, is the Confederation, and acts in a political as well as a military role, though all of his actions are subject to later ratification. He can initiate treaty negotiations with foreign powers, sign ceasefire agreements (again, time lag makes this a necessity) and hold Admiralty courts. In essence, he bears far more resemblance to a ship captain of the Napoleonic-era Royal Navy than to a modern warship commander.

The Executive Officer is far more than just a commander-in-waiting; indeed, there have been circumstances when, upon the death of the commanding officer, a different officer of equal rank has assumed command. In essence, the Executive Officer is the ship's top administrator, responsible for seeing to the smooth running of the ship, for personnel-related affairs not important enough to refer to the Captain, and for liaising between the Department Heads. If the Captain is off-ship, the Executive Officer will assume temporary command, though commanding officers are encouraged to remain aboard their commands unless absolutely necessary.

The Operations Officer is, in many respects, a more focused version of the Executive Officer, and on smaller ships, the two roles are usually merged. His responsibility is on bridge operations, seeing to the assignment and training of bridge personnel, the most critical department on any capital ship. While his department is not the largest, it generally is deemed to be of the highest importance, and generally this officer serves as a top advisor to the Captain. Usually, he will not be present on the bridge in a battle, instead positioned in Auxiliary Control to assume command if needed. (The advice of the Executive Officer, it is usually felt, is considered essential during critical situations.)

The Systems Officer is responsible for the maintenance of the ship, as well as for all engineering functions. This is by far the largest department on a warship, usually consisting of more than half of the personnel complement. (On Alamo, for example, it is sixty-two out of a hundred-and-twelve, including the deck gangs.) This department is split into two roles; the bulk consisting of damage-control teams of four, a Petty Officer and three junior enlisted. In normal operation, they see to routine maintenance; in battle, they are positioned in strategic positions to handle key repairs where needed. The remaining personnel are specialists, trained for key systems such as the hendecaspace drive, the fabrication systems, and the communications hardware.

Combat is the sole purview of the Tactical Officer, and his responsibility is for the offensive and defensive systems of the warship. As such, this is a small but critical department, with a trio of damage-control teams permanently assigned for emergency repair and maintenance. Once again, this is usually one of the commander's top advisers, and is also a role often combined with that of the Executive Officer on smaller vessels. In addition to operating and maintaining the weapons systems, this officer has primary responsibility for the combat readiness of the crew as a whole.

With the major department heads dealt with, we can pass to the second-tier of officers, beginning with the controversial Security Officer, a role that has seen radical changes in recent years. Originally, this officer was solely responsible for internal security, considered an extremely junior role, but given the increasing range of activities of the Triplanetary Fleet, this officer has evolved to become a liaison for surface operations, prize crew commander, as well as retaining responsibility for internal security. From an assignment to be loathed, this has become a highly-prized role for junior officers on the fast-track. Usually, this officer reports to the Operations Officer, but some commanders prefer to have the Security Officer reporting directly to them.

A related role is that of Intelligence Officer, a role that has come to have two meanings. Normally, this is a junior officer responsible for the analysis of intelligence gathered by the ship during the course of a cruise, an essentially administrative role tasked with producing reports for the senior officers, as well as for the post-mission debriefings. Occasionally, however, this role will be taken by an operative from Triplanetary Intelligence, often assigned to a mission all their own, supplementary to the operations of the ship to which they are assigned.

The Political Officer is an experiment that doesn't seem to die, no matter how universally loathed they are by Fleet personnel. Technically, these are almost always civilians granted Warrant Officer status, though on occasion this role has been held by veterans returning to the Fleet, seconded by the Triplanetary Senate. Officially, these are on specific assignments related to areas of their ship's mission area; unofficially, they act as watchdogs for the Senate, monitoring and 'advising' their commander, to provide a voice that would otherwise be unavailable given the communications lag. As hated as this role is, it still keeps returning periodically.

A newly-created role, brought about buy the increased scope of Fleet operations, is that of the Science Officer, which has replaced the earlier title of Astrogator. Typically trained in one of the space sciences, this officer's role is to co-ordinate any scientific activities, with responsibility for astrogation and the sensor systems; as such, he reports to the Systems Officer. As a recently-created role, this has led to several young scientists being offered short-service commissions, while the Fleet Academy adapts to the changed strategic situation.


Perhaps the hardest-worked junior officer on a starship is the Deck Officer, responsible for the maintenance of the starship's shuttle fleet, as well as flight assignments. Though the shuttle complement of a starship can vary wildly, this usually involves working on six to twelve small craft of varying types, as well as a half-dozen pilots. Often, the Deck Officer will be promoted from the ranks; this is a common role for a Warrant Officer, or occasionally a Chief Petty Officer on smaller ships. This officer, naturally enough, reports to the Systems Officer.

Finally, we have the Weapons Officer, a recently-created title designed to give assistance to the Tactical Officer; typically a junior officer recently out of the Academy, this officer shadows the Tactical Officer, assisting with weapons maintenance, combat drills, and serving as a relief for prolonged combat situations. All signs are that this will be a highly-prized role for a junior officer, and replaces the 'Administrative Officer' in the ship's hierarchy, the responsibilities of that role being dispersed more widely.

Not covered here are other officers, largely because they fall outside the role of a major department head. All starships carry a Medical Officer, reporting to the Systems Officer, but it is rare that more than a doctor and a couple of paramedics will be on staff, occasionally a surgical aide; in wartime, this role is expanded. Fighter squadrons and Espatier platoons have their own hierarchy, those officers reporting to the Operations Officer and Security Officer respectively.

Vault of Eternity is out!



The Battlecruiser Alamo is lost, stranded in an unknown corner of the universe, untold light-years from home. On the planet Dante, a hostile wasteland, lies an abandoned alien city that might hold the answers they desperately seek, a way back to their own galaxy. As Captain Marshall and his crew begin their desperate search, they face the nemesis that was drawn into the maelstrom with them, a United Nations Dreadnought whose commander, General Estrada, will stop at nothing to secure the way home for themselves alone. Can the Battlecruiser Alamo unlock the secret of the wormhole, or will they be stranded forever, doomed to sail the stars for all eternity…

February Lack Of Status Report..

February was, being honest, an interesting month to live through, and as far as writing goes, I must confess somewhat frustrating. I had planned to release the first book in the 'Starcruiser Polaris' series near the middle of the month, but that had been based upon the idea that I had finished it – or even managed to complete a draft I liked. Which I didn't. I got half-way through books that were perfectly reasonable, maybe even pretty good, but not good enough. I'd half-expected that, to be honest – I went through something very similar with 'Starfighter', and to be honest, my failure was that I persisted too long, which has meant no book out in February.

I am happy, however, to report that this sad state of events will not persist for long, and that at some point within the next few days, the latest book in the Battlecruiser Alamo series, 'Vault of Eternity', will be out. You'll be even happier to know that this isn't a cliffhanger, not really – originally, I thought I was going to end up breaking the book in two, but in the completed work, it didn't go that way. (Which is as good for me as I suspect it is for you – I hate writing the second part of a two-parter; it's always a miserable task.)

I'll be taking a few days off to get over this one, and then taking another crack at Starcruiser Polaris, this time returning to an old idea that was inspired by – in all seriousness – the early life of Captain Von Trapp. Yes, the Sound of Music guy. No, I have not gone completely insane. In his first career, he was a submarine commander in the Austro-Hungarian Navy, and wrote a fantastic book about the final years of the First World War, 'To the Last Salute', that I can absolutely recommend. I won't go into more details than that, except that this will be rather more epic than my usual fare, and will hopefully go to four books – though we'll have to see how it plays out. If it works, then I'll be releasing it early in April; I already have a fantastic cover, and I really want to see it out there!

My failed drafts in February (so far this year, I've got considerably more unused material than published output, which is something I have to do something about) have thrown my schedule into total turmoil, to the point that I'm not going to give specific dates for a while; the next book should be out in about five weeks, I hope – unless it all falls apart again, in which case there will be an Alamo in about seven. At the latest, the next Alamo, continuing the current arc, will be out in May, probably towards the middle of the month, with, all being well, the second Polaris out in June.

As for the next project, that remains a trip to Ancient Rome – specifically, Roman Aegyptus of the late 1st Century AD, in the time of the Emperor Domitian. I'm at the very early stages on this one at the moment, but I will be posting more here and on a new sister blog I'm about to start – which will be advertised here, closer to the time. (This will remain for my Military SF; the new blog will cover Ancient World.) Military action/adventure, but in a completely different context, of course. It's something I've been wanting to do for years, and I'm finally going to be starting it soon. First two of these out this year, all being well – probably one month apart, meaning I intend to build up a little backlog prior to launch.

So, with luck, the next post on this blog will be the announcement of a new book...