AVIATION SAFETY

Runway incursion safeguards

This example represents a runway incursion as a barrier problem. The hazard is routine surface traffic near a runway; the top event is an unauthorised entry, not the collision that may follow. The left side identifies clearance and visibility threats and the barriers intended to stop them. The right side shows actions that can avoid or manage the outcome once the top event occurs. Use the diagram to structure a surface-safety conversation across pilots, controllers and vehicle operators. Airport procedures, equipment and roles vary, so replace the labels with the controls and terminology used locally. This qualitative diagram is not an operational clearance procedure or a replacement for aviation regulations.

UPDATED 2026-09-24
TYPEBowtie
EXAMPLERunway incursion safeguards
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Airport surface-safety review

Key decisions

  • Hazard: Include all surface traffic.
  • Top event: Define runway entry without clearance.
  • Prevention: Separate communication and visibility controls.
  • Recovery: Show alerts and emergency actions.

When to reuse this

Use as a high-level safety workshop aid; apply airport-specific procedures.

FAQ

Frequently asked questions

What is a runway incursion?01
It is an unauthorised presence on a protected area of an airport intended for aircraft operations.
Why is collision a consequence?02
The unauthorised entry occurs first and may be detected or managed before a collision.
Can vehicle operations be included?03
Yes. Vehicle clearances, routing and driver training are common threat-side controls.
MAKE YOUR OWN

Try the diagram makers.

Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.