Flight Planning Documentation and Operational Requirements
Core concepts
Operational flight planning is governed by a documented chain: the operational flight plan (OFP), the load sheet, the fuel log, the ATS flight plan, and the navigation/performance logs. The OFS must be signed by the commander (or an authorised delegate) and retained. Candidates must know the content of the OFP: route, levels, alternates (take-off, en-route, destination), fuel figures with the breakdown, mass and balance summary, and the MEL/CDL status.
You must understand operational approval concepts: ETOPS, low-visibility operations, RVSM, and the requirement to carry specific documents (certificate of registration, airworthiness, crew licences, operations manual, noise certificate, insurance). The journey log and technical log are distinct: the tech log records defects and servicing, while the journey log records flight details.
Traps
Questions often test the difference between take-off alternate (required when destination weather is below specified minima or the destination is isolated), en-route alternate (needed for ETOPS or for reduced contingency), and destination alternate (required unless the destination has an approach and weather at or above the specified planning minima). Another trap: planning minima are stricter than operating minima - you add a margin to the forecast. Also, the OFP fuel figures must match the actual uplift; a discrepancy is a documentation error, not a rounding issue.
Rule of thumb
If the destination forecast is at or above the planning minima and an approach is available, a destination alternate may not be required; if either condition fails, nominate one and add its fuel. Always verify that the alternate's planning minima are met for the expected arrival period, plus the applicable time window.