Filing a VFR Flight Plan through Eurocontrol: Step-by-Step Guide
- 6 days ago
- 9 min read
European flight planning involves two connected systems. A pure visual flight rules (VFR) flight plan normally goes to an air traffic services reporting office, known as an ARO, or through an approved filing method named in the relevant national Aeronautical Information Publication (AIP). The EUROCONTROL Network Manager receives plans for flights that will operate under instrument flight rules (IFR) for all or part of the route.
Acceptance still depends on delivery through the correct ATS channel. The correct route depends on the planned flight rules, the States crossed and the services required. This guide takes you from that first decision to closing the plan after landing.
Contents
The first decision: ARO or EUROCONTROL Network Manager?
Start by deciding whether the entire flight will remain VFR. Item 8 of the ICAO flight plan uses V for a wholly VFR flight. Under the Standardised European Rules of the Air (SERA), this type of plan is submitted to an ARO. Where an aerodrome has no ARO, the national AIP identifies the ATS unit or approved direct method that performs the same function.
A plan containing an IFR portion follows a different route. Item 8 uses Y when the flight begins under IFR and later changes to VFR. It uses Z when the flight begins under VFR and later changes to IFR. Plans containing an IFR portion in Single European Sky airspace go to the Network Manager directly or through an ARO or authorised flight-plan service.
EUROCONTROL's Integrated Initial Flight Plan Processing System (IFPS) fully processes the IFR portions of a mixed flight. The filer remains responsible for correct distribution and national compliance for each VFR portion. This is one reason why a local ARO or an established authorised provider can be valuable for a mixed flight.
Access to the protected Network Operations Portal also depends on role and permissions. Flight-plan submission is available to profiles with Flight Plan Management authority, including aircraft operators and AROs. Private pilots usually access filing through their ARO or an authorised provider.
When is a VFR flight plan required?
SERA requires a flight plan for several situations that are common in private flying. You need one for a flight or portion that will receive air traffic control service, for designated areas or routes where the authority requires a plan, and for an international border crossing unless the States concerned provide an exception. A VFR flight at night also requires a plan when it leaves the vicinity of an aerodrome.
National rules can add requirements for particular airspace, routes or services. A domestic day VFR flight in uncontrolled airspace may therefore have a different filing requirement from an international trip or a flight entering controlled airspace. Read ENR 1.10 in the AIP for every State involved and check relevant aerodrome entries and NOTAMs.
Timing also needs attention. For a cross-border flight or a flight receiving control or advisory service, SERA permits submission up to 120 hours before the estimated off-block time. A flight that may be subject to air traffic flow management measures needs at least three hours. Other covered flights need at least 60 minutes before departure. A competent authority may prescribe a shorter period for domestic VFR.
An airborne flight plan must reach the appropriate ATS unit at least ten minutes before the estimated entry into the relevant control or advisory area, or before crossing the relevant airway or advisory route. Pre-flight submission gives more time to correct errors and confirm acceptance.
Step 1: read the AIP and choose the filing channel
Open the current AIP for the departure State and find ENR 1.10, Flight Planning. Confirm the accepted filing method, the responsible ARO, service hours, contact details, submission window and any domestic VFR rules. Repeat the check for destination and crossed States where their requirements affect the route.
For a pure VFR plan, use the ARO or approved direct method stated in the AIP. This may be a State briefing portal, an authorised service connected to the ARO, telephone or another published method. A convenient planning application is suitable only when it sends the plan to the required ATS recipients and returns a clear acceptance status.
For a mixed Y or Z flight, ensure that the filing arrangement reaches IFPS for the IFR portion and the correct national recipients for every VFR portion. An authorised provider or ARO should explain how it handles those addresses. The Network Manager's route validation tools are designed around IFPS requirements for IFR segments.
Step 2: gather the information before opening the form
Prepare the operational details first. This reduces typing errors and makes the final plan consistent with your navigation log and aircraft documents.
Aircraft registration and the exact radiotelephony identification you will use
ICAO aircraft type designator and wake turbulence category
Communication, navigation and surveillance equipment fitted and serviceable
Departure, destination and alternate aerodromes or operating sites
Estimated off-block time in UTC
Planned speed, cruising level and route
Total estimated elapsed time
Fuel or energy endurance and total persons on board
Emergency and survival equipment actually carried
Contact details that ATS can use if supplementary information is required
Use the aircraft's current equipment record for Item 10. Copying a code from a similar aircraft can create a false capability declaration. Match the route and altitude to the airspace, weather, fuel, aircraft performance and any permit or equipment restrictions.
Step 3: complete the ICAO flight plan carefully
The ICAO model form uses Items 7 to 18 for the transmitted flight plan and Item 19 for supplementary information when required. All times use four figures in UTC. Estimated elapsed times use four figures representing hours and minutes. The full form below provides orientation; the enlarged crops that follow keep each group legible on a phone or tablet.
Source: European Union Aviation Safety Agency (EASA), Easy Access Rules for SERA, Appendix 6, August 2025. The crops below reproduce the corresponding areas of the same form.
Items 7 and 8: identification and flight rules
Item 7 contains a maximum of seven alphanumeric characters. A registration used as the call sign is entered without hyphens. For example, a registration displayed as S5-ABC becomes S5ABC.
In Item 8, select V for an entirely VFR flight and G for general aviation when that flight type applies. Select Y or Z only when the flight actually contains a planned change between IFR and VFR. The change point must also appear correctly in Item 15.
Items 9 and 10: aircraft and equipment
Item 9 combines the number of aircraft, ICAO type designator and wake turbulence category. Item 10 records equipment and capabilities. Verify each letter and indicator against the aircraft's installed and serviceable equipment. Include relevant surveillance capability in the correct subfield.
Items 13 and 15: departure, time and route
Item 13 contains the departure aerodrome and estimated off-block time. Use the four-letter ICAO designator when one exists. Follow Appendix 6 and the AIP when ZZZZ is required for an operating site without a designator, including the matching DEP information in Item 18.
Item 15 begins with cruising speed and level, followed by the route. Use recognised reporting points, coordinates or other formats permitted by Appendix 6 and the applicable AIPs. A mixed flight must show the significant point at which the rules change and the corresponding IFR or VFR indicator.
Items 16, 18 and 19: destination and supporting detail
Item 16 contains the destination, total estimated elapsed time and alternates where applicable. Item 18 carries coded supporting information such as the date of flight and details required when ZZZZ appears elsewhere. Apply the exact prefixes and formats from Appendix 6.
Item 19 supports alerting and rescue. Enter endurance, persons on board and emergency or survival equipment accurately. A change in endurance or persons on board before departure is a significant change and must be reported.
Step 4: submit and confirm acceptance
Submit through the channel identified in the AIP or through an authorised service that reaches the correct recipients. Check the plan once more against your navigation log before pressing Send. Pay particular attention to UTC, date of flight, aerodrome codes, speed, level, route, endurance and persons on board.
Wait for an explicit indication that the plan has been accepted. SERA assigns the Network Manager responsibility for acceptance of the IFR portion and the ARO responsibility for the other cases. A saved draft or an app confirmation that merely says sent provides limited evidence. Keep the acceptance response and read any conditions or corrections.
For a mixed plan in the protected Network Operations Portal, the structured editor can validate the data against IFPS, show errors and submit the plan when the account has the required role. Validation is a useful technical check. Operational acceptance and correct VFR distribution still need confirmation.
Step 5: confirm departure handling and manage changes
Ask how the departure message will be generated. At an aerodrome with ATS, departure may be observed and reported through local procedures. From an unattended aerodrome or operating site, the AIP or ARO may require a telephone call, radio action or another arrangement. Complete that action exactly as briefed so the flight plan becomes current in the intended system.
Report significant changes promptly. For a controlled VFR flight, changes go to the ARO before flight and to the appropriate ATS unit in flight. Other VFR flights also require significant changes to be reported as soon as practicable.
Delay thresholds depend on the operation. A controlled flight delayed by 30 minutes beyond EOBT needs an amendment or a new plan with the old plan cancelled, as applicable. The threshold is one hour for an uncontrolled flight with a submitted plan. A flight containing IFR has an additional Network Manager notification threshold when the delay exceeds 15 minutes.
If the route, destination, aircraft, equipment, endurance or persons on board changes, contact the filing service or ARO and use the correct delay, change or cancellation process. Avoid filing a second plan while the first remains active. The final accepted plan should describe the flight you intend to operate.
Step 6: close the flight plan after landing
An arrival report is required at the earliest possible moment after landing for a plan covering the whole flight or the remaining portion to destination. You can make it in person, by radio, by data link or by another method prescribed by the competent authority.
An arrival report can be unnecessary at an aerodrome where ATS is provided and radio communication or visual signals show that the landing was observed. Confirm the local procedure in advance. At an unattended destination, plan how you will contact the appropriate ATS unit and keep the number available outside the aircraft.
Where ground communications are known to be inadequate, SERA provides for an arrival-style message immediately before landing when practicable. The AIP and ARO can explain the applicable arrangement. Closing the plan promptly prevents unnecessary alerting and search-and-rescue action.
A simple cross-border VFR example
Consider a private pilot planning a daytime VFR flight from a Slovenian aerodrome to a Croatian aerodrome. The international border crossing triggers a flight-plan requirement unless the States have prescribed a specific exception. The whole flight will remain VFR, so Item 8 uses V and the plan goes through the ARO or an approved method identified in the departure AIP.
The pilot checks both AIPs, current NOTAMs, airspace availability, weather and aerodrome requirements. The aircraft registration is entered in Item 7 without its hyphen. Item 9 uses the correct aircraft designator and wake category, while Item 10 reflects the actual serviceable radio, navigation and transponder equipment.
The pilot enters EOBT in UTC, a route that matches the planned reporting points and airspace, destination, elapsed time, endurance and the true number of people on board. The plan is submitted at least 60 minutes before departure unless a different valid requirement applies. The pilot retains the acceptance response, follows the departure procedure and knows how the arrival report will be made in Croatia.
This example is a workflow illustration. The live route, addresses, customs arrangements, border rules and aerodrome procedures must come from current operational sources on the day.
Common filing mistakes to avoid
Sending a pure VFR plan only to IFPS and assuming national VFR recipients received it
Selecting Y or Z without a real IFR segment and a matching rule-change point in Item 15
Using local time in a field that requires UTC
Copying equipment codes from another aircraft
Treating a saved or transmitted status as acceptance
Forgetting to update EOBT, endurance or persons on board
Departing from an unattended site without completing the published departure action
Leaving the plan open after landing
Final pre-flight and post-flight checklist
Before departure, confirm that the accepted plan matches the aircraft, route, timing, people and endurance. Carry the ARO contact details, the plan reference, the method for reporting a delay and the destination closing procedure. Ensure the route remains suitable after the latest weather, NOTAM and airspace checks.
After landing, complete the arrival report where required and record that the plan is closed. If you divert, land elsewhere or lose access to the planned closing method, contact the appropriate ATS unit by the quickest available means.
Strengthen your flight-planning knowledge
Flight-plan forms become easier when the underlying air law, navigation, communications and operational procedures are familiar. Easy EASA's online theory resources provide clear explanations and practice questions for European PPL and LAPL students.
Comments