COMPANY ROUTES AND INIT REQUEST: RECEPTION IS NOT REVIEW
A company-route selection and an uplink both reduce entry work, but they arrive with assumptions. The request identifies a sector and potentially a route record; the response may be associated with ACTIVE or SEC depending on state and implementation. Establish where the received plan actually went. Neither a successful request nor a company-route identifier substitutes for reviewing its route and dependent data. [66, PDF pp. 102-105,457-464,519-530] [109, Account setup and Generate OFP] [110, AOC SEC F-PLN UPLINK explanation and secondary-plan reception]
1. Prepare the source. Generate the intended current SimBrief OFP and confirm the EFB account setting and matching airframe/engine profile. Check EDDF/EGLL and MC2026 for the offline exercise. A previous generated OFP can be retrieved successfully, so the existence of a response does not identify the sector correctly. Reconcile the source before requesting aircraft initialization. [66, PDF pp. 102-105,457-464,519-530] [109, Account setup and Generate OFP] [110, AOC SEC F-PLN UPLINK explanation and secondary-plan reception]
2. Request and wait deliberately. Use the actual INIT REQUEST or relevant AOC integration function. Read request-processing and completion messages before introducing competing revisions. The cited Thales standard distinguishes data-link processing, completed uplink, invalid data and no response. Its historical timeout mechanics do not establish a universal current service deadline, but the distinction between pending, failed and completed remains important. [66, PDF pp. 102-105,457-464,519-530] [109, Account setup and Generate OFP] [110, AOC SEC F-PLN UPLINK explanation and secondary-plan reception]
3. Identify the receiving plan. Read the page title and the message, especially AOC SEC F-PLN UPLINK. The Fenix support explanation identifies secondary reception in a relevant post-start state. Inspect SEC rather than assuming ACTIVE changed. Do not activate a received spare simply to dismiss the message; first establish the intended active route, aircraft position, mass/performance consequences and clearance. [66, PDF pp. 102-105,457-464,519-530] [109, Account setup and Generate OFP] [110, AOC SEC F-PLN UPLINK explanation and secondary-plan reception]
4. Audit what arrived. Check flight identity, FROM/TO, route record, runways/procedures, complete leg order and gaps. Inspect the ND in PLAN mode at a useful scale. Review received mass/performance or wind data separately if present. A response can be usable while omitting or altering an individual element; a single acceptance message cannot demonstrate that every OFP field was inserted unchanged. [66, PDF pp. 102-105,457-464,519-530] [109, Account setup and Generate OFP] [110, AOC SEC F-PLN UPLINK explanation and secondary-plan reception]
5. Complete missing or changed work. Resolve database-related differences against the current route, then finish final loading and takeoff calculations from their own sources. Retain manual VIA/TO knowledge for local revisions. If a fresh reception is genuinely required, confirm the pending/active/secondary state before repeating requests so that an old response does not become confused with a new correction. [66, PDF pp. 102-105,457-464,519-530] [109, Account setup and Generate OFP] [110, AOC SEC F-PLN UPLINK explanation and secondary-plan reception]