Background
Prior to departure, a series of standard checks were performed at the stand-off bay. The verbal exchange between the captain and the engineer was part of the Stand‑Off Bay Despatch Using Intercom procedure, which relies on a challenge-and-response checklist. This checklist is designed to ensure that critical items, such as the removal of ground support equipment, are properly verified before the aircraft begins to taxi.
Incident Details
During the pre-departure checks, the verbal exchange between the captain and engineer did not adhere to the prescribed challenge-and-response format. The deviation may have occurred because the task was routinely performed, reducing vigilance. As a result, the checklist did not function as intended as a risk control measure. This lapse represented a missed opportunity to detect that the tail strut remained attached to the aircraft prior to the commencement of taxi.
Communication Challenges
Once the aircraft began taxiing, the engineer faced a significant obstacle: no effective means or procedure existed for him to contact the aircraft. Despite this limitation, the engineer attempted multiple methods to reach the flight crew. However, none of these attempts succeeded in alerting the pilots that the tail strut was still connected. Consequently, the aircraft proceeded toward take-off with the tail strut still attached.
The incident underscores the importance of adhering to checklist procedures and the necessity of reliable communication channels between ground personnel and the flight deck, particularly during critical phases of ground operations.