tfl´s "Customer incident"

It's the latest touchy-feely term for "Passenger Action", itself another touchy-feely term for "Somebody went and did something bad."

Usually it's down to altercations between staff and passengers, attempted/executed one unders, somebody being struck down by a medical problem, somebody injuring themselves and needing assistance, etc etc etc.

Now,now MA, a genuine question deserves a genuine answer (as far as one can)

LUL tries to keep it simple by only using a few standard explanations when things go wrong. I do think they keep it too simple at times - which does cause more knowledgeable people, such as those here, to question why they have said 'X', when really 'Y' is the actual problem. When I was on the stations, I found that more often than not the public are capable of understanding better explanations than they get.

Guidelines were issued in the internal traffic circular a few months back, but i've binned it now. Customer incident / passenger action really does mean anything involving a customer. So while MA's answer may seem a little sarcastic, it's actually very true

"Customer Incident"

At least it indicates who is to blame for the delay, ie- A 'fellow passenger' .

2 part answer:

If the 'fire alert' is on a platform or at platform level, the train service will be suspended.

If the 'fire alert' does not directly affect the platform (but obviously close's the station), trains will non stop - so will be subject to 5mph at the station starter as per signalling principals.

(There no types of incident that permit running at full line speed through a station!!)

Yes there are always exceptions to the rule, but my point is that a 'fire alert' (or any other incident for that matter) does not override the signalling system in place. If a train is to non stop, it will do so in the same manner as on any other ocassion at that given location.