LIVE · BRIEFING WIRE
FlightLogic Brief Daily aviation wire
← Reddit
● RDT COMM ·-SQB- ·August 13, 2026 ·13:06Z

Was power cycling an A350 an error?

An aircraft engineer was fired after power cycling an Airbus A350, an action that caused a delay and prompted complaint from Singapore Airlines. An initial safety manager assessment found no wrongdoing and determined the incident was a "no blame error," meeting industry standards for actions another technician would likely have taken in similar circumstances. Subsequent pressure from Singapore Airlines led to a reassessment that resulted in the technician's termination.
Detailed analysis

An aircraft maintenance engineer in Brisbane was dismissed by his employer after performing a power cycle—a routine reboot—on a Singapore Airlines Airbus A350 during troubleshooting, an action that led to an extended ground delay while various onboard systems required realignment and reinitialization. A safety manager's initial investigation cleared the engineer of wrongdoing, applying the industry-standard "substitution test": would another reasonably competent engineer, facing the same fault indication under the same time pressure, have made the same decision? The manager concluded yes, characterizing the event as a "no blame error" consistent with Just Culture principles that most aviation safety management systems are built around. Despite that finding, commercial pressure from Singapore Airlines over the cost and disruption of the delay reportedly drove the employer to reopen the case and terminate the technician—a decision an employment tribunal later found to be unfair dismissal.

The case sits squarely at the intersection of two competing forces in modern aviation maintenance: technical complexity and commercial accountability. Modern fly-by-wire widebodies like the A350 are deeply integrated systems of systems—flight controls, navigation, cabin management, and network server architecture are all interlinked, and a full power cycle can trigger cascading realignment sequences (IRS alignment, database reloads, avionics handshakes) that take far longer to complete than the reboot itself. Airbus has previously issued guidance and airworthiness directives around A350 power management, including a well-publicized requirement that operators power-cycle the aircraft within specific intervals to avoid a software fault that could degrade multiple systems simultaneously. Engineers troubleshooting an in-service fault must often choose between a power cycle that resolves the immediate issue but risks a lengthy downstream delay, or a more conservative path that may leave the original fault unresolved. Neither choice is obviously "wrong" in isolation, which is precisely why the substitution test exists—to separate genuine negligence from a defensible judgment call made under real-world constraints.

For working pilots, dispatchers, and maintenance controllers, this case is a pointed reminder of how fragile Just Culture protections can be when an operator's commercial customer applies pressure. Just Culture frameworks—embedded in SMS programs across ICAO member states—are premised on the idea that honest, reasonable errors made in good faith should not be punished, because punishing them discourages the transparent reporting that safety systems depend on. When a carrier or MRO reverses a documented no-blame finding because a customer is unhappy about delay costs, it sends a chilling signal to the entire maintenance and flight-crew workforce: safety judgment can be overridden by commercial optics after the fact. That has direct relevance for flight crews too, who make analogous real-time trade-offs constantly—diverting, holding, declining a marginal MEL item, or requesting additional troubleshooting time before departure. If maintenance technicians learn that a defensible, standard-procedure decision can still get them fired when it costs an airline money, the rational response is to become more risk-averse in ways that may not actually improve safety, or alternatively to under-report problems to avoid triggering a costly cascade.

More broadly, the episode reflects an ongoing tension across commercial aviation as carriers face intensifying pressure on turnaround times, on-time performance metrics, and cost control post-pandemic, while simultaneously professing commitment to non-punitive safety reporting. Regulators and unions have flagged similar friction in pilot fatigue calls, technical write-ups, and go-around decisions, where economic incentives can subtly erode the willingness of frontline personnel to make conservative safety calls. The tribunal's finding of unfair dismissal in this case reinforces that employment law, at least in some jurisdictions, will still back up documented Just Culture assessments even when a major airline customer disagrees—but the fact that it took litigation to restore that protection underscores how easily commercial leverage can bypass safety governance in practice. Operators, MROs, and airlines relying on third-party maintenance providers would do well to treat this as a case study in keeping safety investigations insulated from commercial fallout, since the alternative risks quietly undermining the reporting culture the entire industry depends on.

Read original article