62,200 Pages


Published in September 2009, The Krillitane Storm was one of the last set of three original novels published featuring the Tenth Doctor in the standard BBC New Series Adventures line.

Publisher's summary Edit

When the TARDIS materialises in medieval Worcester, the Tenth Doctor finds the city seemingly deserted. He soon discovers its population are living in a state of terror, afraid to leave their homes after dark, for fear of meeting their doom at the hands of the legendary Devil's Huntsman.

For months, people have been disappearing, and the Sheriff has imposed a strict curfew across the city, his militia maintaining control over the superstitious populace with a firm hand, closing the city to outsiders. Is it fear of attack from beyond the city walls that drives him or the threat closer to home? Or does the Sheriff have something to hide?

After a terrifying encounter with a deadly Krillitane, the Doctor realises the city has good reason to be scared.

Plot Edit

to be added

Characters Edit

References Edit

  • The Doctor thinks of Donna Noble, remembering that she always knew when to stop.
  • The Ood-Sphere is mentioned.
  • The first moon landing is mentioned.
  • The colonisation of Mars is mentioned.

Notes Edit

  • This book continues the theme set by the BBC Tenth Doctor Adventures line for 2009 of featuring returning monsters from the TV series.
  • The final Tenth Doctor release connected to the BBC New Series Adventures, the Quick Reads release Code of the Krillitanes, also features the Krillitanes.
  • This story was also released as an ebook available from the Amazon Kindle store.

Audio release Edit

  • The story was released as an audiobook on 6x CD read by Will Thorp.
The Krillitane Storm Audiobook

The Audiobook cover.

Continuity Edit

External links Edit

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.