Air carrier Captain reported similar sounding SID designations was a factor in a track deviation departing GMMX/RAK.

Date: 2026-01 · Aircraft: Commercial Fixed Wing

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-clearance|ground-event-encounter-other-unknown

Synopsis

Air carrier Captain reported similar sounding SID designations was a factor in a track deviation departing GMMX/RAK.

Narrative

Operations at RAK introduce several systemic; non-standard threats that increase crew workload and elevate risk during ground and departure phases. These threats are primarily procedural and communication-based rather than individual-performance related. The following observations are provided to support hazard identification and potential mitigation.Threat and error management analysis. Ground operations - pushback / tow procedures. Non-standard pushback practices. Language barriers between flight crew and ground personnel. Lack of standardized communication protocols during tow reconfiguration.While complying with pushback instructions; ground personnel indicated they do not normally tow beyond [Gate] XX. Though adequate clearance existed behind the aircraft and taxi-out under own power appeared feasible; a safety concern arose when I requested the aircraft be repositioned forward. Without notifying the flight deck; the towbar was disconnected; turned; and reconnected. The crew was not instructed to set the parking brake; nor advised that the tow configuration had changed.Tow operation conducted without flight deck awareness. Absence of required brake coordination during towbar reconfiguration.This created a momentary loss of situational awareness and removed an essential safety barrier during a critical ground operation; compounded by language limitations and non-standard local practices.Suggestions: Standardized tow communication protocols. Mandatory flight deck notification prior to towbar disconnect/reconnect. Brake status confirmation prior to any tow configuration change.Departure clearance timing. Departure clearance issued prior to completion of the PREFLIGHT CHECKLIST.At RAK; departure clearance was issued after pushback but prior to taxi. This deviates from SOP flow and introduces task interruption during checklist execution.Disruption of normal checklist sequence. Increased workload and distraction during a high-risk phase.This practice increases the likelihood of missed items; degraded task prioritization; and reduced margin during taxi and departure preparation.Suggestions: Procedural review of clearance delivery timing. Crew guidance emphasizing checklist completion discipline prior to clearance acceptance when feasible.SID / fix nomenclature confusion. Similar-sounding SIDs and fixes. The expected clearance was MAGAV3D; however; the initial clearance issued was MABAP3D. After departure; ATC issued a right turn direct MAGAV.Similarity in fix and SID naming increases the potential for clearance misinterpretation; especially in high workload or non-native English environments.Suggestions: Improved differentiation of fix and SID nomenclature. Enhanced chart depiction or procedural notes to highlight common confusion points.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.