Browse
Published interview gouge ordered by most recent submission.
Free member access
Listings show airline, role, date, outcome, difficulty, and a short excerpt. Create a free account to open preview gouges and keep full reports inside the pilot community.
Expected: include jumpseater and reach mutual agreement between CA and FO.
Learning points: do not rush the ILS, communicate fuel, and avoid answering noncritical FA call on short final.
Two-person CRM scenario: medical emergency plus deteriorating weather.
Interviewer was happy with early go-around, dispatch/base involvement, and selecting reachable COS.
Paired CRM with young captain and FO; no detailed feedback given.
Evaluator wanted the candidate to know the approach-light allowance, while still considering terrain and variables.
Technical scenario across weather and charts; included for SIM/Scenario study pool because it was scenario-based.
Expected: good decision-making and proactive resource use, not freezing at minimums.
Reported outcome: taxied back, deplaned passenger, law enforcement met at stairway.
Published Southwest Study Guide questions. Source answers were cleaned where provided; technical questions include concise captain-minded model ans...
Expected answer: FO flies, captain talks to FA, declare if serious/uncertain, and have medical ready.
This was mainly a teamwork/CRM evaluation: decision-making, involving all parties, and communicating as a crew.
Generic medical CRM prompt. Do not let the vague report stay vague; gather facts, assign roles, and use resources.
Evaluator focus: keep ATC, dispatch, FA, medical, and the other pilot in the loop and talk decisions through as a team.
Core point: windshear alert on short final is a go-around first, planning second.
The interviewer liked that the crew kept FAs, dispatch, and ATC in the loop while reassessing the plan.
Combines two priorities: smoke drives urgency, but windshear still requires respecting the go-around escape path.
This scenario is similar to the Denver smoke/windshear prompt but specific outcome was COS after a DEN go-around.
Multiple pasted variants described bomb writing in a lav/mirror/window. Stored as one consolidated security-threat scenario.
Specific variant with a suspicious passenger at the named seat and a nearby suitable runway.