DATA AND A/C STATUS: IDENTITY BEFORE COMPUTATION
A/C STATUS is the starting identity check, not simply a date display to pass on the way to INIT. Establish the loaded airframe, engine installation and available database information, then reconcile them with the planning profile. For EDDF-EGLL the teaching configuration remains the A320 CFM with wingtip fences. A route can be geographically correct while its mass limits, thrust reference or performance calculation belong to a different aircraft. [66, PDF pp. 101,451-465,665-674] [106, Official profile register; A320 CFM wingtip-fence configuration]
1. Inspect the actual configuration. Read the available aircraft/engine identity and check the chosen Fenix variant outside the MCDU where necessary. Compare the OFP profile with that configuration. Keep ceo versus neo separate from the presence of Sharklets. Do not infer the engine family from the shape of a performance page or a screenshot selected merely to explain a particular control. [66, PDF pp. 101,451-465,665-674] [106, Official profile register; A320 CFM wingtip-fence configuration]
2. Establish the mass/fuel units. The supplied standard supports thousands of kilograms or pounds through its configuration. The worked values in this guide are metric tonnes. Read the actual field units before entering 60.0 or 6.0. If a planning document uses a different convention, perform the proper conversion and document it; copying the same digits into another unit system does not preserve the mass. [66, PDF pp. 101,451-465,665-674] [106, Official profile register; A320 CFM wingtip-fence configuration]
3. Inspect ACTIVE database identity and dates. Compare them with the current OFP and charts. Then inspect the spare database separately. A second cycle present on the page is storage, not proof that it is the working cycle. Route construction uses the active database; the V3 update and activation workflow is addressed in the following topics. [66, PDF pp. 101,451-465,665-674] [106, Official profile register; A320 CFM wingtip-fence configuration]
4. Use DATA as a lookup tool. The source standard provides access to waypoint, navaid, runway and route definition pages as well as pilot-defined data. When an identifier is questionable, inspect its definition and coordinates instead of testing it repeatedly in the route. A data lookup answers what the system knows about an item; adding that item to a flight plan is a separate action. [66, PDF pp. 101,451-465,665-674] [106, Official profile register; A320 CFM wingtip-fence configuration]
5. Resolve mismatches before building dependencies. Correct the configuration or planning profile before final loading and takeoff calculation. Resolve the intended navigation cycle before programming the route. After an actual change, repeat the identity check and rebuild the dependent preparation as required. This avoids carrying an apparently complete flight into the next stage with one of its foundational assumptions still unsettled. [66, PDF pp. 101,451-465,665-674] [106, Official profile register; A320 CFM wingtip-fence configuration]