TARDIS Index File

Frostfire (audio story)

58,897articles in progress
Add New Page
Talk0 Share
Cc101 frostfire big
Doctor: First Doctor
Companion(s): Vicki, Steven
Main enemy: The Cinder
Main setting:
Key crew
Publisher: Big Finish Productions
Writer: Marc Platt
Director: Mark J Thompson
Music: Lawrence Oakley
Sound: Lawrence Oakley and Robert Dunlop
Cover by: Simon Holub
Release details
Release number: 1.1
Release date: January 2007
Format: 2 episodes on 1 CD
Production code: BFPDWCC01
ISBN 978-1-84435-263-0
←Previous Next→
The Companion Chronicles
none Fear of the Daleks

Frostfire was the first release in the Companion Chronicles audio range. It was the first story of season 1. It was written by Marc Platt and featured Vicki Pallister.

Publisher's summary Edit

Vicki has a tale to tell.

But where does it start and when does it end?

Ancient Carthage. 1164 BC.

Lady Cressida has a secret. She keeps it deep in the cisterns below the Temple of Astarte with only one flame for warmth. And it must never get out.

Regency London, 1814 AD.

The First Doctor, Steven and Vicki go to the fair and meet the fiery Dragon, the novelist Miss Austen and the deadliest weather you ever did see.

But which comes first?

The Future or the Past?

The Phoenix or the Egg?

The Fire or the Frost?

Or will Time freeze over forever?

Plot Edit

Part one Edit

to be added

Part two Edit

to be added

Cast Edit

References Edit

Biology Edit

  • The Cinder mentions the Doctor's hearts.

Buildings Edit

Individuals Edit

  • The Doctor, Vicki and Steven Taylor are joined on this adventure by Jane Austen.
  • The Doctor, Vicki, Steven and Jane met a beadle in London in 1814.

Locations Edit

Music Edit

  • The Doctor dances a gavotte with Jane Austen.

Notes Edit

Textless cover art

Textless cover art

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.