Unit-2 Trip at 02:40: The Message, the Chain and the Press Line

Rewritten message:

Unit 2 (110 MW) tripped at 02:40 h on operation of generator differential protection while running at 96 MW. The 400 kV busbar and Units 1 and 3 are healthy. The unit is on barring gear; oil mist was observed at the enclosure, no fire and no injury. Revised declared capacity: 220 MW. Cause under investigation; restoration time being assessed, next update 05:30 h.

Justification, point by point:

• 'has been tripped' → 'tripped'. A completed event at a stated time takes the simple past. The present perfect reads as though the unit is still in the act of tripping.
• 'due to the generator differential protection' → 'on operation of'. The relay is not the cause; it is the protective response. Saying 'due to the relay' is technically wrong and invites the wrong question in the log.
• Delete 'The cause of the fault is due to the internal problem in the stator winding'. Two errors in one sentence: 'cause … is due to' is redundant, and the cause is unproven at 03:05. A stator fault is a hypothesis until the enquiry reports, and an unretractable written statement of cause to a system operator is a liability.
• Delete 'which was informed by the operator on duty'. The relative clause attaches to the stator winding, so it says the winding informed the operator - a misplaced modifier. If the operator's report matters, write 'as reported by the shift operator'.
• Replace 'very soon' with a committed update time. 'Very soon' is not a schedule and cannot be planned against.
• Delete 'kindly bear with us … and oblige'. The system operator is not a customer; this is a control-room communication, not a courtesy letter.
• Add the load at trip (needed against the 22:00 constraint direction), the health of the busbar and the other units, and the revised declared capacity, which the operator needs for scheduling.

Sequence:

1. System operator, immediately - the control room is informed by telephone or SCADA within the same scheduling block as the trip, followed by a written intimation the same shift, with the revised declared capacity. A generating unit cannot simply disappear from the schedule without the system operator knowing.
2. Internal escalation - station head and the corporate operations desk at once; the original equipment manufacturer and the protection engineer after the relay flags and disturbance recorder are downloaded, since the recorder data are the primary evidence and must be preserved before anyone resets anything.
3. Statutory triggers, only if applicable - any injury or fire engages the factory/state authorities within the prescribed reporting time; any oil reaching the drains engages the state pollution control board. Neither applies here, and saying so explicitly in the log protects the station later.
4. Corporate communication and, if required, the distribution company/beneficiaries - after the operator, never before.

Forced versus planned outage: a planned outage is taken with the prior consent of the system operator and is listed in the approved outage programme, so it is known to the grid in advance. A forced outage is unplanned and takes effect from the moment of the trip whether or not anyone agrees; it is subsequently reported and the declared capacity is revised, and it carries the grid-code consequences. You cannot retro-fit approval to a forced outage. That is precisely why the 22:00 constraint direction and the 96 MW loading must be on record: they show the station was complying with the operator's instruction when the trip occurred, which matters to any subsequent review.

Press line:

Unit 2 (110 MW) of the station tripped at 02:40 h on its protective relay while operating at 96 MW. There was no fire and no injury; oil mist was observed at the generator enclosure and the unit has been safely placed on barring gear. Units 1 and 3 continue to run and supply to the grid is unaffected. The cause is being investigated by the station's technical team, and a further update will be issued at 17:00 h today.

Deliberately left out, and why:

• Any statement of cause. 'Internal problem in the stator winding' would be quoted as a confirmed finding and would force the station to defend or retract it after the enquiry.
• Words like blast, explosion, smoke or fire unless they are literally true. Oil mist at an enclosure is not a fire, and the difference matters to insurers, regulators and neighbours.
• Any restoration time the station cannot meet. The press will hold you to a stated time; 'being assessed, next update at 17:00' is safer and still accountable.
• Employee names and relay details, which belong in the internal report, not a public statement.
• Any suggestion of grid impact. The other two units were running; overstating impact is as damaging as understating it.

The most dangerous sentence: 'The cause of the fault is due to the internal problem in the stator winding which was informed by the operator on duty.' It is dangerous on three counts at once - it asserts an unproven cause, it is grammatically ambiguous about who reported what, and it would be read by the public as an admission that the station knew of an internal winding problem and kept running. A press line must state confirmed facts and one honest unknown, and nothing else.