Update: we have received a statement from the MTA, which follows the original story below.
Looks like another day of royal F train delays, with a sprinkling of assault and battery:
— Hunter Walker (@hunterw) October 30, 2014
Tempers running high w/ F train delays. Just saw a lady bonk another lady on the nose. AND nose-bonker was wearing a neckerchief! @the_SDB
— Tiffany Liao (@Tiff_Liao) October 30, 2014
Early reports claim that, due to signal problems, some F trains were rerouted to the D line. Others also reported an F switching to a G, and vice versa (which we’ve certainly covered before):
Once the F Train arrived, it turned on us, becoming a G Train, ejecting all at a half-ghost-town. @… http://t.co/MnMy6ABlIv
— Thomas L. Strickland (@ThomasLS) October 30, 2014
I waited half an hour for a G train that never came; instead the F inexplicably rolled up and everyone got on it because nothing makes sense
— Kaye, and a skeleton (@ohkayewhatever) October 30, 2014
Some sublimated the experiences, letting the creative juices flow:
Happy scenes such as this make me wish that I had an F train voodoo doll and an unlimited supply of pins. pic.twitter.com/cVZ4ULsNIs
— Sara Wood (@woodsarawood) October 30, 2014
@ThomasLS so much depends upon an absent F train filled with distraught sighs under Park Slope.
— Emily (@emilyhughes) October 30, 2014
For the rest of us, how do we cope?
— conrad doucette (@conrad) October 30, 2014
(Brooklyn Brief is checking in with the MTA to find out what happened).
Update 1: The Pols are on it.
— David G. Greenfield (@NYCGreenfield) October 30, 2014
— Barry Spitzer (@bspitzer) October 30, 2014
Update 2: We have received a statement from the MTA:
“A problem with a switch south of Church Av that caused delays for about ½ hour. G service suspended between Church and Bedford-Nostrand.”