Chapter 6
Flight preparation

6.1 Minimum flight altitudes

6.1.1 Definitions

Minimum Flight Altitude (MFA) is the generic term for the minimum altitude at which it is safe for an aircraft to fly.

When operating on a defined route segment, national authorities may have published the Minimum Enroute IFR Altitude (MEA) for that segment. This altitude (or flight level) ensures obstacle clearance and navaid reception. When available, MEA is published in black on the LIDO en-route charts below the airway designator. Alongside, in red, LIDO publishes Minimum Terrain Clearance Altitude (MTCA). This is a LIDO derived value, based on rounding up the elevation of the highest obstruction within 10nm of the airway to the nearest 100ft, then adding 1000ft tor terrain below 6000ft or 2000ft for terrain above. MTCA is always available.

LIDO OFPs present Route Minimum Off Route Altitude (Route MORA). This is a LIDO derived value based on the highest terrain within 20nm of a given route segment. For terrain up to 5000ft Route MORA provides 1000ft clearance; for higher elevations it provides 2000ft clearance.

When not operating on a defined route segment, LIDO presents area obstacle clearance data in the form of a Minimum Grid Altitude (MGA). MGA is calculated by rounding up the highest obstruction within the respective grid area to the next 100ft then adding either 1000ft for obstructions up to 6000ft or 2000ft if they are higher. The lowest indicated MGA on LIDO charts is 2000ft. MGA is shown in purple if it is less than 10000ft and in red if it is greater.

Minimum Sector Altitude (MSA) is the minimum altitude that provides 1000ft of obstacle clearance within 25nm (unless otherwise specified) of a specified navigation facility. It is published as a segmented circle on LIDO plates. It is for emergency use only, and does not necessarily guarantee navaid reception.

Additionally, various instrument flight procedure altitudes are calculated by national authorities when designing instrument procedures, and these are published on LIDO instrument plates. In particular Minimum Radar Vectoring Altitudes (MRVA) are provided to ATC and may be flown when the aircraft is under positive radar control. The LIDO MRC chart shows MRVAs to allow cross checking of ATC instructions.

[ eom-a 8.1.1, eoma 8.1.1.4, lido route manual ]

6.1.2 Corrections

With the exception of DA, which must be corrected if OAT is less than -10°C, baro VNAV approaches with a promulgated minimum temperature below OAT do not need to be corrected for temperature. For all other approach types, whenever OAT is less than -10°C, the Final Approach Fix altitude, platform altitude, NPA equivalent glide altitudes, DA/MDA and any other minimum altitudes on the approach must be corrected for temperature. This is most easily done using LIDO functionality; Table 6.1 may also be used. ATC must be informed of the corrected FAF altitude for traffic separation purposes.

To correct higher altitudes for temperatures below ISA, a conservative rule of thumb is to add 1% of the altitude for every 2° that the actual temperature is below ISA, e.g for a 20,000ft MEA with ISA-20° add 200x20/2=2000ft.

When operating in low atmospheric pressure conditions with an altimeter setting of 1013, the aircraft will be ∼30ft below the indicated altitude for every millibar that the QNH is below 1013. This can be applied as a positive increment to a published minimum altitude to calculate a minimum flight level.

A combination of high winds and high terrain can result in localised variations in atmospheric pressure; consideration should be given to increasing MFA under these conditions.

Note that the Route MORAs presented on the LIDO OFPs do not have any of these corrections applied.

[ eom-a 8.1.1.3 ]

6.1.3 Operational requirements

Obstacle clearance for take-off and initial climb phase is provided by a combination of LPC performance calculation and SID and EOSID design.

Engine failure or loss of pressurisation may lead to a requirement for en-route descent. Currently, the highest obstacle affecting easyJet routes is Mont Blanc at 15,771ft. This is at least 2000ft below the A319 green dot one engine ceiling assuming MTOW and ISA+20. Thus, there are currently no special drift down diversion procedures in place. In the case of emergency descent following loss of pressurisation, all obstacles must be cleared by at least 2000ft. It is worth noting that the time of useful consciousness without supplementary oxygen is 30 minutes at 18,000ft.

For the approach phase, unless in visual contact with the ground with flight visibility sufficient to identify all relevant obstacles, flight below MSA should only be conducted on promulgated routes or instrument approach procedures or when being vectored at levels not less than MVA.

[ eom-a 8.1.1.4 ]

6.2 Usability of airports

easyJet is responsible for ensuring that all airports selected as destinations or alternates are adequate in all respects, including runway dimensions, obstacles, ATS, lighting, approach procedures, weather reporting and emergency services.

Rescue and Fire Fighting Service (RFFS) category 7 for A321 and 6 for A320/A319 are the normal minimum acceptable levels of cover. For some destinations, category 5 is considered acceptable; this will be notified on the OFP. Temporary reductions of up to two categories is permitted at departure and destination for a period of time not exceeding 72 hours. Downgrade to category 5 at UK alternates and category 4 at non-UK alternates is acceptable. If a downgrade occurs during flight, the Commander may elect to land at an aerodrome regardless of RFSS category if it is considered safer than diverting.

easyJet will categorise aerodromes from A to C in order of increasing difficulty. The category of an aerodrome is promulgated on its LIDO CCI page. Operation to a category B aerodrome requires self-briefing. Signing the OFP confirms that this has been done. Operation to a category C requires specific crew qualification.

[ eom-a 8.1.2.1, eoma 8.1.2.5 ]

6.3 Aerodrome Operating Minima

All easyJet aircraft are Category C for the purpose of calculating operating minima.

Aerodrome specific take-off minima are presented on LIDO AOI charts. Pilot assessment of RVR for the initial part of the take-off run is permissable, but reported RVR must be considered for all other relevant reporting points.

Minima for instrument approaches (including circling) are presented on the relevant LIDO approach plates. Where decision height is listed as “Company”, NO DH should be used for CAT3B and 50RA should be used for CAT3A. easyJet is not certified to use “Localiser Perfomance with Vertical guidance” (LPV) minimas. Only RVRs applicable to relevant segments of the runway need to be considered for landing. Required stop end RVR is always 75m and required mid-point RVR is always 125m unless ROLLOUT mode is used, in which case it is also 75m.

When RVR is not reported, and provided that required RVR > 800m (after conversion), Table 6.2 may be used to convert Met Visibility to RVR for the purposes of complying with landing minima.

Circling minima should be used unmodified. It is permissible to descend prior to the final turn. However, descent below circling minima should only occur once the landing threshold has been identified and all surrounding terrain is in sight.

If standby ILS transmitters, markers, meteorological measuring equipment or lighting systems are downgraded, approach minima may need to be modified. A table is presented at EOM-A 8.1.3.5 for this purpose. If a downgrade occurs below 1000ft on the approach, the approach may be completed at the Commander’s discretion.

A visual approach requires Met Visibility > 5km and cloud base > 2,500ft. Visual approaches at night are authorised unless prohibited in the relevant CCI. Visual circuits must be flown at a height greater than 1500ft that ensures at least 500ft separation from obstacles.

MDA and DA must always be above OCA and must therefore be adjusted if OCA is increased by NOTAM.

[ eom-a 8.1.3, eom-a 8.1.5, eom-a 8.4.2.1 ]

6.4 Selection of alternates

Figure 6.1 shows a flow chart for determining required minimas for take-off and destination alternates. A table for interpretation of TAFs with regards these requirements can be found at EOM-A 8.1.2.4.

Dispatch with no destination alternate should only be considered when payload or performance is limiting. Runways may be considered independent if each runway has a separate approach procedure based on a separate approach aid and no conceivable blockage of one runway would render the other unusable.

Two destination alternates are also required when landing performance cannot be assured due to wind or runway state or when no meteorological information is available for the destination.

In the case of an engine failure at any point along the planned route an adequate aerodrome must be available within 60 minutes single engine flying time. Table 6.3 shows the equivalent distances for the easyJet fleet.

[ eom-b 5.1 ]

6.5 Pre-flight fuel planning

The OFP presents the following values for use in pre-flight fuel planning:

• TAXI
  Fuel expected to be used prior to takeoff, including engine start, taxi and APU consumption. This figure should be adjusted when significantly increased APU burn is likely (e.g. ATC slots) or when significantly increased taxi times may occur (e.g. remote de-icing).
• TRIP
  Fuel required for all phases from take-off at departure aerodrome to landing at destination aerodrome. The assumed runways and associated SIDs and STARs can be found on the OFP under “OFP ROUTE”. This figure will need to be increased by 5kg per nm that actual routings are potentially longer than these assumed routings. The OFP also provides trip fuel corrections for carriage of more than minimum fuel and flight at non optimal levels. Trip fuel does not include fuel for the point merge or trombone sections of STARs.
• CONT
  Fuel to allow an absolute minimum of 5 minutes holding over destination at 1500ft. If statistical contingency fuel (SCF) data is available, contingency fuel will also be at least the 95th centile SCF or 99th centile SCF, depending on city pair. If SCF data is not available, contingency fuel will be at least 5% of trip fuel.
• ALTN
  Fuel for all phases from a go-around at applicable MDA/DA at destination to a landing at first alternate. The assumed runways and routings can be found on the OFP below the Nav Log block. This figure will need to be increased by 5kg for each nm that actual routings are potentially longer than these assumed routings. Where two alternates are required (see Section 6.4), this figure should be increased to the greater of the two alternate fuel burns. Note that this does not allow for flight to a second alternate after arriving at the first alternate.
• FINRES
  Final reserve fuel. This is the amount of fuel required to hold at 1500ft for 30 minutes assuming the tanks will be dry at the end of this period.
• EXTRA
  Fuel added by ICC to account for “anticipated delays”. Usually zero.
• ADDNL
  Usually zero. This is mainly used to add 15 minutes holding time when operating without a destination alternate under the terms of Section 6.4. It may also be used on routes where there will be insufficient trip fuel available to divert to an adequate alternate in the event of engine failure or loss of pressurisation at the most critical point.

• DISC
  Fuel loaded at the discretion of the flight crew. There is not much official guidance as to amounts; my personal ballpark figures are:

  • 40kg per minute of potential extra holding
  • 500kg per potential extra approach
  • 30 minutes extra holding when LVPs are expected at destination
  • 3kg per minute of extra anticipated anti-ice usage
  • 2kg per minute of extra anticipated APU usage
• TANKER
  Extra fuel that may be carried due to fuel price differential between origin and destination. Note that take-off and landing performance is not considered, and the planned margins against structural limits can reflect over-confidence in predicted ZFW data.

[ eom-a 8.1.7, eom-b 5 ]

6.5.1 Reducing fuel loads to allow increased payload

Where payloads are such that the carriage of normal fuel loads results in exceedance of structural or performance limitations, eom-a 8.1.7.6 presents a number of methods of reducing fuel requirements below those that would normally apply.

The simplest method is to reduce the trip fuel requirement once it is certain that the SID and/or STAR that will be flown requires less track mileage than those anticipated in the OFP route. The adjustment is 4kg per nm.

More significant reductions can be achieved when the conditions for not requiring a destination alternate (see Section 6.4) are met. In this case, the alternate fuel can be replaced with 15 minutes of holding at destination.

Finally, it is possible to reduce contingency fuel by declaring an “en-route alternate”. This will, at most, allow contingency fuel to be reduced to 90th centile statistical contingency fuel (SCF), or, in the absence of SCF figures, 3% of trip fuel. The contingency can never be reduced below 5 minutes of holding at 1500ft at destination, and minimums of 200kg for A321, 170kg for A320 NEO, 204kg for A320 CEO or 190kg for A319 also apply. Details of the procedure, including the somewhat complex determination of where an en-route alternate must be situated, may be found in eom-a 8.1.7.6.4.

[ eom-a 8.1.7.6 ]

6.6 Weight and Balance

6.6.1 Structural weight limitations

The aircraft operating manual specifies maximum ramp, take-off, landing and zero fuel weights. The maximum take-off weight may also be reduced by easyJet to take advantage of reduced ATC charges; where this has been done, the new MTOW must be treated as a structural limit. These limitations are also presented in the weights block of the OFP.

The basis for calculations to determine compliance with these structural limits is the Dry Operating Weight (DOW). The DOW is the total weight of the aircraft with no usable fuel or payload. It is available at the top of the OFP, but the canonical value is that contained in the EFB database unless otherwise notified by a flight brief notice. Other weights are calculated as follows:

• Zero Fuel Weight (ZFW) = DOW + payload
• Ramp weight (RW) = ZFW + total fuel
• Take-off weight (TOW) = RW - taxi fuel
• Landing weight (LW) = TOW - trip fuel

In addition to the main structural weights, load limits for individual cargo compartments may be found in fcom per.lod.cgo.

[ eom-a 8.1.8.1.1 ]

6.6.2 Payload calculation

Tables 6.4 to 6.7 give the standard weights that may be used when calculating payload.

easyJet generally uses standard weights for passengers and crew and actual weights for baggage. It is not permissible to use standard weights for baggage if this leads to a value less than known actual weights. Freight must always be weighed.

The standard crew weights include an allowance for hand baggage. Any additional baggage must be accounted for.

[ eom-a 8.1.8 ]

6.6.3 Balance calculation

Compliance with balance limitations is achieved using the EFB Weight and Balance modules with actual seating positions. A “free seating contingency” is available at EOMB 7.5 for exceptional circumstances precluding the use of allocated seating data.

[ eom-b 7.1.1 ]

6.6.4 Last minute changes

An LMC exceeding +10/-20 Passengers requires new paperwork and a new performance calculation. A change in CG greater than 2% in either direction or an increase of payload of more than 250kg require a new performance calculation. If payload change ≤ +250kg and the change in CG is 2% or less then the original performance calculation can be used.

[ eom-b 7.4 ]

6.7 Operational Flight Plans

Operational Flight Plans (OFP) are usually downloaded to the pilots’ iPads via the Smart Portal app. In the event that one pilot is unable to download OFPs, there is a facility to transfer OFPs between iPads via Bluetooth. Ensure that the status of all flights is “closed” at the end of the duty as this indicates that easyJet have received the completed OFPs.

If neither pilot is able to download OFPs, they may be downloaded as PDF files from the easyJet web portal and annotated using the Acrobat app. A final fallback is to have OCC email the PDF files. The annotated files must then be emailed to easyJet at the end of the duty.

[ eom-a 8.1.10 ]

6.8 Aircraft Technical Log

6.8.1 Standard of entries

All entries must be completed in block capitals.

Any signature must be accompanied by a printed surname, the date and any applicable authorisation or approval numbers.

If an entry is changed, the incorrect entry must have a single line drawn through it, the reason for the alteration entered next to the original text and a signature.

The Tech Log must be cross checked for errors after the final sector of a duty.

[ eom-a 8.1.11.2, eom-a 8.1.11.3, eom-a 8.1.11.5 ]

6.8.2 Layout and usage

The tech log is divided into prologue pages and a main section.

The prologue pages include the Certificate of Release to Service, records of Acceptable Deferred Defects (ADD), the Damage Register and “Briefing Notes to Crew”. These must all be checked prior to accepting an aircraft.

Each page in the main section is divided into a defect section and four tear-off sector record strips. Unused strips on the current page should be struck out if any entry has been made in the defect section or when a crew change occurs without a direct handover.

The top half of each sector record strip is for recording details of a sector after it has been completed. The “Log Time” and “Landings brought forward” boxes are no longer used and should be struck through. The “Full Rated Thrust T/O” and autoland reporting are only relevant to the 737 fleet. If the record of the previous sector is found to be incorrect or incomplete the duty pilot must be contacted for authorisation to continue.

The bottom half of the strip is used to record pre-departure data and acceptance of the aircraft. The “Oil Check” and APU oil level boxes are not relevant to flight crew and should be struck through. The ambient temperature fuel uplift should be recorded rather than the temperature corrected figure. To calculate approximate uplift in kg, multiply the uplift in litres by 0.8. If anti-icing has been carried out, the type of fluid, concentration and start and end times should be recorded. If anti-icing is carried out more than once it will be necessary to use multiple strips; each strip must have a copy of all the pre-departure data.

Each main section page has three coloured carbon copy sheets. The pink page is used to comply with regulations requiring retention of documentation at departure station. The pink strip with the commander’s acceptance signature must always be left behind. The entire pink page should be left behind when there are no more usable strips, including when the strips have been struck out in accordance with the paragraph above. All other pages belong to engineering.

[ eom-a 8.1.11.5, eom-a 8.1.11.6 ]

6.8.3 Defect management

All defects should, with the following exceptions, be immediately entered into the tech log:

• Recording of ECAM maintenance status messages may be deferred until the aircraft is next at a “main base”. Consultation of the MEL is still required.
• Cabin defects must be immediately entered into the Cabin Defects Log. If the defect does not affect airworthiness (consult MOC if there is any doubt), then it does not need to be transferred to the tech log.

MOC must be contacted whenever a defect is entered in the tech log. Where possible MOC will arrange for engineering to rectify the defect or clear it to an ADD sheet in accordance with the MEL.

When no engineering support is available MOC may request that the flight crew clear a defect to the ADD pages. Deferral of defects by flight crew is only possible when the defect is assessed by MOC as having no effect on airworthiness or when the relevant MEL entry has no maintenance actions specified.

To clear a defect to the ADD pages the commander should obtain an ADD Level 1 AMOS workorder number from MOC and enter it in the “ACTION TAKEN” column along with the MEL reference and repair interval. The commander signs for this in the “ACTION TAKEN” column and crosses through the CRS section; authorisation by MOC for release to service is implicit in the creation of the workorder number. The relevant ADD entry should then be completed on the Aircraft Status Report sheet. The complete tech log defect description should be transferred, along with the tech log page reference and item number, any MEL/CDL reference number and limiting criteria (e.g. expiry date).

Successful computer resets should be recorded by making a suitable entry in the defect section, e.g.

CREW RESET: COM CIDS 1 + 2 FAULT ON THE GROUND, SUCCESSFUL RESET AS PER QRH

These entries do not count as open defects, so signatures should be placed below the entry and the associated “Action Taken” and CRS sections should be struck through.

Information that may be useful but which does not require immediate engineering action may, with MOC’s agreement, be recorded as a “FOR INFO” entry in a similar way, e.g.

FOR INFO: FMGC1 FAILED. RECOVERED WITH NO CREW INTERVENTION.

Signatures should be placed below the entry, and the phrase “Reviewed and nil defect confirmed” should be entered in the “Action Taken” column to indicate that MOC are aware.

Bird strikes that do not result in damage may be recorded as “For Info” entries, providing the restrictions in EOM-A 8.1.11.19 are observed.

[ eom-a 8.1.11, eom-b 2.3.25.2, eom-b 3.3, eom-a 8.1.11.19 ]

6.8.4 Recurrent engineering checks

The validity of recurrent engineering checks must be confirmed prior to accepting an aircraft. This is done for most checks by checking that the Certificate of Release to Service is valid. Completion of the daily check is recorded via an entry in the defect column; the earliest a daily inspection for a given calendar day may be certified is 18:00z on the previous day.

[ eom-a 8.1.11.4 ]

6.8.5 Cabin defect log

The SCCM enters details of cabin defects in the cabin defect log and presents it to the commander at the end of the flight. The commander must review the defects and transfer any airworthiness items to the technical log.

[ eom-a 8.1.11.17 ]

6.9 Documents to be carried

6.9.1 Certificates

• Certificate of Registration (original)
• Certificate of Airworthiness (original)
• Certificate of Airworthiness Review (original)
• Air Operator Certificate (electronic copy)
• Noise Certificate (electronic copy)
• Aircraft Radio Licence (electronic copy)
• Third Party Liability Insurance Certificate (electronic copy)
• Flight Crew Licences

6.9.2 Manuals and charts

All required manuals and charts are carried in electronic format on the EFB.

6.9.3 Flight Documentation

The following flight documentation must be carried in paper form:

• Load form
• Technical Log
• Forms to comply with reporting procedures
• Notification of special loads (if applicable)
• Notification of special passengers (e.g. deportees)
• Any other documentation required by states concerned with the flight
• Crew passports

[ eom-a 8.1.12 ]