FANDOM


This article is about the battle described in the comic. For the comic, see Battle of Fitchburg (comic).

Previous:

First Assault on Boston

Battle of Fitchburg (event)
BoF

Conflict:

Invasion of Earth

Date:

2012[1]

Location:

Fitchburg, Massachusetts

Outcome:

2nd Mass escapes Espheni forces

Belligerents

Espheni

2nd Massachusetts Militia Regiment

Commanders

Espheni commander

Captain Daniel Weaver

Strength

100+ Mechs
Numerous Skitters
Several Beamers

2nd Massachusetts Militia Regiment
*Berserkers

Casualties

Numerous Skitters
Numerous Mechs

Henry
Griffin
Uncle Scott
100+ Fighters and Civilians

 
We can't afford another Fitchburg
Weaver

The Battle of Fitchburg was costly engagement fought between the Espheni forces and the 2nd Massachusetts Militia Regiment.

DescriptionEdit

After the assault on the Mothership, the aliens counter-attacked in force four weeks after. Despite Weaver's best efforts to elude them, they eventually caught up with the 2nd Mass in Fitchburg, Massachusetts. Surrounded, a pitched battle ensued. Ben was eventually able to find a weak spot in the alien line, and the 2nd Mass punched through to escape with heavy losses. The 2nd Mass survived, but lost one hundred fighters and civilians. Its stated that the Berserkers also played a key role in the escape.

Comic DescriptionEdit

"Immediately following the events of TNT's Falling Skies season 1, the Second Mass gets pinned down by alien forces and sustains heavy losses. With an army of skitters closing in, the resistance group shields themselves in an armory in Fitchburg, ready to finish the battle once and for all."

TriviaEdit

The story of the Battle of Fitchburg was told with a short comic series called "Battle of Fitchburg."

SourcesEdit

  1. Opening panel sets this battle 4 weeks after the assault on Boston. (Eight Hours)

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.