Brunei DCA CPL(A) Operational Procedures common mistakes
Brunei DCA CPL(A) Operational Procedures · Understand the traps and how to avoid them.
Computing trip fuel from the planned route distance and then treating that figure as the total fuel requirement, omitting taxi, contingency, alternate, final reserve and any extra fuel before comparing against the minimum.
Candidates memorise the fuel-planning formula as 'trip fuel plus reserve' and rush the arithmetic under time pressure, so intermediate line items are dropped and the final figure looks plausible enough not to be re-checked.
What to do instead
Build the fuel plan as an explicit vertical column in a fixed order (taxi, trip, contingency, alternate, final reserve, extra, total) and add the column twice, once forwards and once backwards, before answering; state each line item in the working so a marker can see it exists.
Using still-air or zero-wind figures for a leg where the forecast wind gives a significant headwind or tailwind component, or applying the wind to the wrong leg direction.
Wind triangles are perceived as slow and error-prone, so candidates substitute the simpler no-wind ground speed and then answer a time or fuel question with an optimistic figure.
What to do instead
For every leg, write the wind component (head or tail) next to the track before computing ground speed, and sanity-check the direction: a headwind must increase time and fuel, a tailwind must decrease them. If the sign of the effect is wrong, the calculation is wrong.
Reading a take-off or landing distance from the chart for the actual mass and conditions, then failing to apply the operational factor or the regulatory margin, and quoting the raw chart value as the required distance.
The chart output feels like the final answer, and the multiplier or percentage addition is a separate step that is easy to forget once the chart has been read.
What to do instead
Adopt a two-line habit: line one is 'chart distance', line two is 'required distance = chart distance x factor', and always compare the required distance against the available distance rather than the chart value.
Checking mass and balance only against maximum take-off mass and centre-of-gravity limits at take-off, ignoring the zero-fuel mass limit and the centre-of-gravity position at zero fuel and at landing.
The take-off case is the one most practised, so candidates stop once that envelope check passes and never plot the later mass states.
What to do instead
Plot three points on the envelope for every load sheet: zero fuel, take-off and landing, and check each against both mass limits and the fore and aft centre-of-gravity limits; state explicitly that all three lie inside the envelope.
Reading back a clearance by repeating only the parts that changed, such as the new level, without repeating the route, frequency, squawk or conditional instructions in full.
Pilots naturally echo the element they consider salient, and under workload the full readback feels redundant when the rest of the clearance was already acknowledged.
What to do instead
Read back the entire clearance in the order issued, including callsign, route or heading, level, speed, frequency and squawk; for conditional clearances repeat the condition verbatim before the instruction. If any element is missing from your readback, the clearance is not fully acknowledged.
Treating a clearance limit as an implicit clearance to descend or to enter controlled airspace, or beginning a descent on a 'descend when ready' instruction without first confirming the aircraft is within the cleared lateral boundaries.
Clearance limits and crossing restrictions are linguistically similar to descent clearances, and expectation bias fills the gap when the pilot is anticipating the descent.
What to do instead
Before every level change, state the three things you hold: lateral clearance, level clearance and any speed or time restriction. If any one is not held, request it. Never descend on a clearance limit alone.
On an abnormal or emergency checklist, jumping straight to the memory items and then omitting the subsequent written checklist, or skipping the 'consider' and 'if conditions permit' branches because they are not immediate actions.
Time pressure and the desire to resolve the problem quickly make the memory items feel sufficient, and the conditional branches read as optional commentary.
What to do instead
Treat memory items and the written checklist as two distinct phases with an explicit verbal handover between them ('memory items complete, now the checklist'), and read every branch aloud, deciding and stating whether the condition applies.
Declaring an emergency or diversion without stating the three essentials in a single transmission: intentions, the nature of the problem and the assistance required.
High workload fragments the transmission, and pilots transmit the problem first and then wait to be asked what they want to do.
What to do instead
Use a fixed frame for the first emergency call: 'Mayday, callsign, nature of problem, intentions, position and level, persons on board, assistance required.' Write the frame on the knee pad before keying the microphone.
On the icing question, deciding to continue based only on the absence of airframe ice accumulation, ignoring the temperature structure, freezing-rain risk and the performance penalty already present.
Visible ice is treated as the only trigger, so a clean airframe in forecast icing conditions is read as safe, and the degraded climb or increased stall speed is not factored in.
What to do instead
Base the decision on three inputs: forecast and observed conditions, the temperature profile including any warm layer above a sub-zero layer, and the aircraft's current performance margin. If any of the three is adverse, change level, route or destination rather than waiting for ice to appear.
Treating crew resource management as a topic to be recited rather than applied, so answers describe 'good communication' generically instead of identifying the specific barrier, assertion or briefing that failed in the scenario.
Human factors is studied as vocabulary, and candidates answer at the level of principle because they have not practised mapping a scenario to a named countermeasure.
What to do instead
For every human-factors question, name the specific failure (for example an unresolved ambiguity in the approach briefing, or a junior crew member's concern not being escalated) and then name the specific countermeasure that would have caught it, in operational terms rather than as an abstract virtue.