Briefing the cabin: NITS and passenger announcements

When something goes wrong, the calm in the cabin is built on the flight deck — in two short, structured messages.

The idea

In an abnormal, the flight deck is busy and time is short — so the words aft of the door have to carry a lot in a few seconds. There are two channels, and they are not the same message. To the cabin crew you give a tight, ordered brief so they can prepare: NITS — Nature, Intentions, Time available, Special instructions — and they read it back. To the passengers you give calm, honest, plain language: what is happening, why, and what happens next.

Anxiety in a cabin is fed by three things: jargon people can’t decode, vagueness that invites imagination, and silence. Structure and plain honesty are what settle it.

Two-channel comms · a diversion

Scenario. Your twin-jet has shut down its number-two engine as a precaution. The aircraft is safe on one engine. You’re diverting to Shannon, about twenty minutes out — a normal landing, with fire vehicles meeting the aircraft as routine. Brief the cabin crew (NITS), then the passengers. Watch the cabin’s tension.

100

tense

To the cabin crew — NITS brief

Ordered, terse, complete — then read back.

To the passengers — PA

What · why · what happens next.

Pick a phrase for each line, or press play the clear brief. Nothing has been said yet — the cabin is at its most uncertain.

How it works

NITS is a container that forces the four things a cabin crew needs, in the order they need them, so nothing is forgotten under pressure. The closes the loop — you hear that the message that left the flight deck is the one that arrived. The passenger PA is a different register entirely: no procedures, no acronyms, no commands meant for crew.

NITS  — to the cabin crew (they read it back)
  N  Nature ......... what is wrong, in one line
  I  Intentions ..... what you are going to do
  T  Time available .. how long until it happens
  S  Special instr. .. what you need them to do + the trigger word

PA  — to the passengers (calm, honest, plain)
  What ......... name what they may have already noticed
  Why .......... the honest reason, in everyday words
  What next .... where, when, and what they will see / should do

Rule of thumb:  structure removes the gaps that fear fills.
                jargon and vagueness are gaps.  so is silence.

In this simulator, each clear line lowers the tension gauge; jargon lowers it only a little (the crew half-follow); vagueness barely moves it; and a couple of choices — a dismissive “nothing to worry about,” or broadcasting a crew command to the whole cabin — actually push tension up.

When to use it

Reach for the NITS + PA split when…	The trade-off / limit
Time allows a brief — a diversion, a precautionary landing, a medical hold.	In a sudden, seconds-only event you give a condensed command, not a full NITS — the structure is a target, not a straitjacket.
The crew must prepare the cabin and you need shared understanding.	Skipping the readback saves five seconds and risks a crew acting on the wrong picture.
Passengers have felt or seen something and will fill silence with fear.	Over-explaining or reading them the checklist raises anxiety instead of lowering it.

Watch out for

Jargon leaking into the PA. “EGT exceedance,” “QRH,” “drift-down” are crew words. To passengers they sound like alarms in a language they don’t speak. Say “we’ve shut one engine down as a precaution.”
Vagueness. “A technical issue” or “we’ll update you when we know more” leaves a vacuum. People imagine the worst thing that fits the words.
Silence. The most common failure. If passengers noticed the engine spool down and hear nothing, tension climbs on its own.
Broadcasting crew commands to everyone. “Cabin crew, prepare for a possible emergency landing” is a command for the crew, on the crew channel — not a line to say over the passenger PA.
False reassurance. “Everything is completely fine” when people plainly felt something breaks trust for every word that follows. Be calm and honest.
No readback. A brief you didn’t confirm is a brief you only think landed.

Worked example

An interviewer asks: “You’ve had an engine precautionary shutdown and you’re diverting. Walk me through how you communicate.” A strong answer separates the channels out loud. To the cabin crew: “NITS — Nature: number-two engine shut down as a precaution, aircraft is safe. Intentions: diverting to Shannon, precautionary landing. Time: about twenty minutes. Special instructions: normal landing, no evacuation planned, secure the cabin and brief your sections, my trigger will be ‘cabin crew be seated.’ Read that back to me.” Then to the passengers, plainly: “This is the captain. You may have felt us reduce power — we’ve shut down one of our two engines. It’s a precaution; the aircraft flies safely on one, and our procedure is to land at the nearest suitable airport. We’ll land at Shannon in about twenty minutes. You may see fire trucks by the runway — that’s routine. Please follow your cabin crew.” The interviewer is listening for the structure, the readback, and the fact that you never once said “QRH” to a passenger.

Check yourself

You’re about to make the passenger PA. Which opening line does the job?

Your first officer gives you a full NITS brief for the cabin crew. What’s the last step before it’s truly “delivered”?