Psych Safety, by Iterum
  1. Psych Safety
  2. Learning Lab
  3. Scenarios
  4. Facilitator notes

Facilitator notes · Aviation, 1977 · About 40 minutes

The Tenerife airport disaster, 1977

On 27 March 1977, two Boeing 747s that had been diverted to Los Rodeos airport on Tenerife collided on the runway in cloud, and 583 people died. In Fog at Los Rodeos the group takes the seats of the two crews and the control tower in turn, and makes their decisions with only what they knew at the time. It is a strong session on power gradients, speaking up and closed-loop communication, and a good first scenario for any team.

For the facilitator. In the session this event stays masked, as Fog at Los Rodeos, until the reveal at the end, so the group meets it as the people involved did, with only what they knew at the time. Keep this page for yourself before the session.

Run Fog at Los RodeosAll scenarios

An airport in fog · Kenneth Lu · CC BY 2.0 · Wikimedia Commons

What happened

KLM Flight 4805 and Pan Am Flight 1736. Both diverted from Las Palmas, Gran Canaria.

At 17:06:47, the KLM 747 struck the Pan Am 747 on the runway during its takeoff run. The Pan Am crew saw the KLM landing lights coming out of the cloud about 9.5 seconds before impact and tried to get off the runway.

583people died
61survived, all on the Pan Am aircraft

All 248 people on board KLM 4805 died, and 335 on Pan Am 1736. It remains the deadliest accident in aviation history.

What the group does

Over this session we’ll sit in several seats in turn: a captain, a tower controller, a crew taxiing in cloud, a first officer and a flight engineer.

  1. An ordinary day. Nothing goes wrong. We see how the work normally runs.
  2. The incident day. The same airport on a different Sunday. Information arrives in the order it arrived for the people involved.
  3. The reveal and debrief. What really happened, why it made sense, and what it means for us.

It needs a screen everyone can see and about 40 minutes. A facilitator is optional, and nobody needs to sign in or know the field.

What went right

The debrief looks at what people did well as well as what went wrong: most days, the same adaptations are why things go right.

What the debrief opens up

Its sections:

Some of the questions it asks the group:

Ways to debrief it

Each real incident can be debriefed three ways, chosen on its briefing screen: the standard debrief, a quick 20 to 30 minute debrief, or a learning team. To run a learning team on something from your own work, use the learning team guide.

Further reading

Key papers

Sources

Run Fog at Los RodeosAll scenarios

Stuck, or has something gone wrong?

Tell us and we’ll help. Ideas for making the Lab better are just as welcome. The Lab is in public beta and we read every message.

Help & feedback