Shark bridge lock failure

Used 8 times

First logged:
December 15th, 2017 at 7:05pm

Latest alerts

December 15th, 2017 at 8:18pm: Northeast Corridor; NJCL train #2313, the 8:02pm from Bradley Beach is up to 20 min. due to shark bridge lock failure.

December 15th, 2017 at 8:11pm: Northeast Corridor; NJCL train #3373, the 7:54pm from Spring Lake is up to 15 min. late due to Shark bridge lock failure.

December 15th, 2017 at 7:46pm: Northeast Corridor; Update: NJCL train #3363, the 6:45 from Bradley Beach is operating up to 60 min. late due to earlier Shark bridge lock failure.

December 15th, 2017 at 7:44pm: Northeast Corridor; Update: NJCL train #3361, the 6:19pm from Bradley Beach is operating up 75 min late due to earlier Shark bridge lock failure.

December 15th, 2017 at 7:43pm: Northeast Corridor; Update: NJCL train #4372, the 6:04pm from Belmar is up to 95 min. late due to earlier Shark bridge lock failure.

December 15th, 2017 at 7:38pm: Northeast Corridor; Update: NJCL train #3363, the 6:45 from Bradley Beach is up to 60 min. delayed due to Shark bridge lock failure. An update will follow.

December 15th, 2017 at 7:06pm: Northeast Corridor; NJCL train #3363, the 6:45 from Bradley Beach is delayed due to Shark bridge lock failure. An update will follow.

December 15th, 2017 at 7:04pm: Northeast Corridor; Update :NJCL train #3361, the 6:19pm from Bradley Beach is delayed due to Shark bridge lock failure. An update will follow.