Combined generator defects and MEL dispatch pressure on a freighter
An A330-300 freighter is scheduled to depart Hong Kong at 23:40 for Anchorage. At 18:00 the APU generator fails its built-in test and the maintenance control centre raises a deferral under the operator's MEL for an inoperative APU generator, ten-day limit. At 20:15, during the pre-departure check, the No.1 engine generator control unit drops offline twice and resets; fault finding points to an intermittent connector fault expected to recur. The MEL entry for an inoperative engine generator permits dispatch only if the APU generator is available and the APU is serviceable. A replacement GCU is in Singapore, 14 hours by courier plus three hours to fit and test. The cargo is 62 tonnes of temperature-sensitive pharmaceuticals, the crew is at five of fourteen duty hours, and the ramp closes at 02:00. Operations asks you to 'defer both items and let the crew monitor it in flight'.
1. State and justify the dispatch decision.
Read the worked answer
The aircraft is not dispatchable, and the MEL cannot be used twice to get there.
The reasoning chain is dependency, not arithmetic. The relief for an inoperative engine generator is conditional: it is granted because the APU generator provides redundancy. That condition is already false, because the APU generator is itself inoperative and deferred. Once one deferral invalidates the condition of a second entry, the two cannot be stacked. The MEL preamble on multiple and associated conditions exists precisely for this situation, and any assessment must consider the combined effect of all open items on the affected system, not each item in isolation.
Two further checks point the same way. First, electrical load: with one main generator lost, the remaining generator and battery must carry the essential and non-essential buses, and on a freighter that includes cargo fire suppression and compartment systems. Second, the route and any extended diversion time segment must be assessed against the operator's EDTO provisions, which typically require a serviceable APU and generator configuration. Even where EDTO does not bite, night operations over water with depleted electrical redundancy is not a marginal call.
'Monitor in flight' is not a dispatch basis. In-flight monitoring is a mitigation after a defect appears, not a substitute for the required redundancy at dispatch. Signing a certificate of release in these terms would misstate the airworthiness status.
The correct output is a clear no-go with the reason recorded, not a discussion about how likely the fault is to recur. If the fault had proved to be a wiring connector repairable under approved data, the situation would be different - which is the next question.
2. What lawful options exist, and on what approval basis? How would you sequence them against the ramp closure?
Read the worked answer
I would sequence by time to restore a compliant configuration, not by commercial priority.
Option 1 - Restore one of the two items properly. Fault isolation matters more than the MEL. If the intermittent fault is in the connector or the associated wiring rather than the GCU itself, a wiring repair under the standard wiring practices manual may be a short task and restores the No.1 generator to service; that alone makes the aircraft dispatchable with the APU generator still deferred. This is the fastest lawful route and should be worked first. In parallel, ask whether the APU generator fault is a similar connector issue - the two faults appearing in one shift may share a cause.
Option 2 - Fit a replacement unit. Courier the GCU, fit and test. This costs roughly 17 hours, which misses the 02:00 ramp and the slot. It is a schedule decision for the operator, not an airworthiness compromise.
Option 3 - Ferry or positioning flight. A non-revenue flight under an approved permit to fly, with approved flight conditions, is a possible route to a maintenance base. It is not available for the revenue cargo flight, and no MEL deviation can authorise it. An operator MEL may be more restrictive than the master MEL, never less. Any relaxation would need approval from the Civil Aviation Department as the state of registry and operator, in a defined emergency, and a delayed pharmaceutical cargo is not that.
Option 4 - Offload and reposition the aircraft later. Legitimate, and often correct, but it is an operations decision.
I would give operations the decision tree with times attached: wiring repair by 22:30, unit change by midday tomorrow, otherwise the flight does not go.
3. What would you record and communicate, and what changes if the aircraft has already departed with both defects?
Read the worked answer
Before departure. Record the fault, the troubleshooting steps, the deferral references and, critically, the fact that dispatch was refused because the conditions of the MEL entry were not met. Notify the crew and operations in writing with the reason and the option timescales. The technical record should show a deliberate engineering decision, not an unexplained delay.
If the aircraft has departed, the situation is different in kind. With one main generator failed and the APU generator unavailable, a second generating source loss leaves the aircraft on battery and emergency power, with a real risk to flight controls, navigation and cargo fire suppression. My actions would be: contact the crew through operations and the flight following function, direct an assessment of electrical configuration, and support a decision to divert to the nearest suitable aerodrome rather than continue. I would not attempt to manage this by message traffic alone.
Reporting. A maintenance error or configuration that could endanger the aircraft is normally reportable under the occurrence reporting scheme, and an in-flight loss of electrical generation certainly is. I would file through the organisation's mandatory occurrence reporting process to the Civil Aviation Department and cooperate with the operator's own report, keeping to a just-culture position: the report is about system failure, not blame.
Follow-up. Audit how the two deferrals were raised on the same aircraft without an integrated systems review, and whether the maintenance control centre had the engineering authority and the courage to refuse. That is the root cause; the connector is just the trigger.