Missing Wrench in a Fuel-Tank Area Before Charter Release
A 7/16-inch combination wrench is missing from an open tool tray after an access panel was refitted on a fuel tank. Three engineers have worked in the area across two shifts. The tool tray has no shadow board, and one engineer borrowed the wrench from another set. The aircraft is fuelled, pressurised, and scheduled for a charter in 90 minutes. A search of the hangar floor finds nothing. The licensed engineer is under pressure from the operations controller, who says the aircraft 'has been fine for the last two flights'. The missing wrench is not listed on the tool inventory because it came from a personal set. The engineer is asked to certify the aircraft as fit for release.
1. What immediate actions should be taken before any release decision, and why?
Read the worked answer
The aircraft should be placed in a no-release state until the wrench is accounted for or a formal risk assessment shows it cannot be in a critical area. The AME should stop work in the area, preserve the tool tray and personal tool set for identification, and establish exactly which wrench is missing and where it was last used. The fuel-tank access area should be inspected with a borescope or other suitable means, including the tank interior if access was open. A tool count and signed search of the hangar, trays, clothing and nearby panels should be conducted. The 'two good flights' argument is irrelevant: a loose tool may migrate or cause damage later. The engineer should not sign a release on the basis of a verbal assurance. If the tool cannot be found, the maintenance organisation and operations should be informed, the aircraft kept grounded, and a formal FOD risk assessment completed before any further flight.
2. Analyse the tool-control failures using a human-factors model such as SHEL or the dirty dozen.
Read the worked answer
Using SHEL, the liveware-liveware interface failed at shift handover: three engineers worked the area and the borrowed wrench was not clearly transferred. The liveware-software interface failed because there was no shadow board, no tool sign-out and no requirement to list personal tools. The liveware-environment interface was poor because the tray was open and the area was shared. Pressure from the operations controller is a 'dirty dozen' factor that encourages the engineer to rationalise release. Complacency is present in the phrase 'has been fine for the last two flights'. Lack of assertiveness may push the engineer toward signing rather than challenging the controller. The personal-tool exception bypassed the organisation's tool-control barrier entirely. These are system weaknesses, not just one engineer's forgetfulness.
3. Recommend system changes to prevent recurrence, including documentation and shift handover.
Read the worked answer
The organisation should require a controlled tool inventory for every task, including shadow boards, tool tags and a signed issue/return record. Personal tools should be declared and included in the count, or prohibited in fuel-tank and engine areas. Shift handover should include a formal tool count and a written statement of any missing item, with both outgoing and incoming engineers signing. Access panels should not be refitted until the tool count is complete. A FOD inspection should be a hold point in the work pack, and any missing tool should trigger a stop-work and occurrence report. The organisation should also train controllers not to pressure engineers with 'it has been fine' arguments and should audit tool control regularly. The aim is to make the safe action the easy action, rather than relying on memory at the end of a shift.