Incident response

Incident & near-miss response

Practice incident and near-miss response using realistic, time-pressured scenarios. Validate containment decisions, communication, reporting quality, and escalation timing to reduce repeat events.

Incident & near-miss response
Problem
Incident response is often learned informally. Under pressure, teams miss steps or delay escalation, increasing exposure.
Outcome
Faster, safer responses, improved reporting discipline, and measurable readiness for real incidents.
Worked example

What it looks like at Nano Masters AI Airline

Role: Ramp turnaround supervisor
Format: 8-minute time-pressured scenario, delivered by link to mobile or in your LMS (SCORM)
Fictional blueprint company, used for illustration.

The situation

The hub is recovering from a thunderstorm closure, with rolling delays, gate constraints and crews close to their duty limits. During a rushed turnaround, a belt loader touches the edge of an aft cargo door. The driver says it was just a light tap and there is no visible damage. The aircraft is due to push back in twelve minutes.

The decision

The supervisor has to decide how to contain the event, who to tell and what to report, while operations control is pushing to protect the next departure wave.

Option A
Stop loading at that door, call maintenance for an inspection, inform the captain and operations control, and file a factual report that includes the driver's account.
The flight leaves late after the inspection, and the safety team receives a report with enough detail to act on. The rubric credits containment and escalation timing.
Option B
Have a lead check the door visually, release the flight when nothing is found and file a near-miss report after the wave clears.
The report arrives hours later, missing key details, after the aircraft has already flown. The scenario reveals a reporting threshold set by visible damage and a delayed escalation.
Option C
Coach the driver on the spot and skip the report, since nothing appears damaged and the station is under on-time pressure.
A later branch shows a crew at the destination finding a seal problem with no record of the contact. The scorecard flags under-reporting and a risk of repeat events.

What the scorecard shows

The scorecard covers containment choices, escalation timing, communication clarity, reporting quality and compliance with incident procedures. In this illustration, cohort results show reporting thresholds slipping specifically during irregular operations, so remediation focuses on disruption days and the group is re-tested until it meets the threshold.

What we measure

Containment decision
Whether the supervisor stops the activity and protects the aircraft before deciding anything else.
Escalation timing
Whether maintenance, the flight crew and operations control are informed before the aircraft moves.
Reporting threshold
Whether events with no visible damage are still reported in line with procedure.
Report quality
Whether the report is timely, factual and specific enough for a safety team to investigate.
Communication under disruption
How clearly the supervisor explains a delay to operations control while recovery pressure is high.

FAQ

Common questions

Yes—scenarios can test reporting thresholds and decision points that often drive under-reporting.

No—operations, supervisors, contractors, and cross-functional responders can all be assessed.

Containment choices, escalation timing, communication clarity, and compliance with incident procedures.

Identify weak points, assign remediation, and re-test until thresholds are met.
Want this use case tailored to your roles?
We generate scenarios, decision points, and scorecards in days.