Browse

Evaluator focus: communication and using resources while smoke/fire and windshear compete for attention.

Specific lesson: use dispatch and ask FAs if any medical professionals are onboard.

Debrief focused on team performance, FA communication, and what each crewmember could improve.

The scenario had no single right answer; they wanted crew resource use under thunderstorms and fuel pressure.

Timed CRM followed by debrief on what went well and what did not.

No right or wrong answer; they wanted teamwork and consensus on a safe action.

Cascading CRM scenario designed to test coordination and resource use, not a perfect ending.

Debrief: delegated tasks but did not give crewmembers enough time; dispatch can solve distance/fuel/customs questions faster.

Specific feedback: never open the cockpit door because the sick passenger could be a security setup.

Evaluator liked intercommunication, delegation, and decision-making under changing weather/runway conditions.

Reported miss: they diverted but forgot to tell FA and passengers.

Scenario ended after they declared fuel, medical, and combative-passenger emergencies and got priority.

Evaluator emphasized there are no wrong answers if CRM and resources are used well.

Timed scenario; they liked teamwork, emergency declaration, and keeping dispatch/FA/passengers updated.

Short CRM prompt; expected good decision-making and resource use.

Technical scenario from Jepp discussion; included because it is a scenario-based approach-management question.

CRM scenario with younger PIC and SIC; focus was crewed-environment behavior.

Evaluator wants decision-making, teamwork, and willingness to learn from alternatives.

Technical scenario around Exemption 3585, descent planning, procedure turn, and weather drop before FAF.

Scenario-based Jepp/91.175 technical item from the attachment.