How do I fix Fenix A320 INIT REQUEST not working in MSFS?
If INIT REQUEST is not working in the Fenix A320 in Microsoft Flight Simulator, the usual causes are a missing flight-plan import login, the aircraft not being fully powered, no valid FROM/TO entry on the first INIT page, or a conflicting World Map route. Fix those first; most cases clear immediately.
What usually stops INIT REQUEST in the Fenix A320?
In MSFS, INIT REQUEST usually fails because the aircraft either has nothing valid to import or the MCDU is not in the right state to accept it.
| Symptom | Likely cause | What to do |
|---|---|---|
| The line key seems dead | No valid flight-plan import account, or no dispatch has been generated | Check the account in the Fenix tablet or ATSU and make sure there is a live plan to import |
| INIT REQUEST is not available or does nothing useful | No FROM/TO city pair, or you are on the wrong INIT page | Enter the departure and destination first on the initial INIT page |
| The MCDU is lit but unreliable | Partial electrical power or an avionics issue | Establish stable aircraft power before trying the request again |
| The route imports badly | MSFS World Map conflict or navdata mismatch | Clear the sim-planner route and review the imported legs manually |
How do I get INIT REQUEST working again?
Work through these in order. Usually the first missed item is the whole problem.
- Start with stable electrical power. Do not troubleshoot the MCDU in a half-powered cockpit. Give the aircraft proper external or APU power first.
- Use the first INIT page. The request belongs on the initial
INITpage, not the later page used for other entries. - Enter a valid city pair. Type the route as
ICAO/ICAO, for exampleEGLL/EDDF, and insert it atFROM/TO. Without that, INIT REQUEST has nothing sensible to work from. - Check the flight-plan import account. In the Fenix tablet or ATSU settings, the account used for OFP import must match the one that generated your dispatch. A blank, wrong or stale login is one of the most common causes when the button appears dead.
- Make sure a dispatch exists. If you have not generated a flight plan for that account, there is nothing for INIT REQUEST to pull.
- Keep the MSFS World Map simple. A full route loaded in the sim planner can clash with the Fenix FMS import. Start on stand with only the airports set, or no route at all, then build the plan inside the aircraft.
- Clear old route data. Saved states, airport changes and half-built routes can leave stale entries in the MCDU. Delete the partial plan and re-enter the city pair before trying again.
- Reload the aircraft if needed. If the page is still unresponsive after the checks above, reloading the Fenix or restarting the flight is faster than fighting a stuck panel state.
If you are unsure what the normal Airbus sequence should look like after that, our A320 MCDU/FMS programming guide is the quickest way to confirm you are using the correct INIT flow.
Does the aircraft need to be fully powered first?
Yes. A lit MCDU is not the same as a properly powered aircraft. People often try INIT REQUEST with only batteries on, or with a saved state that has left parts of the cockpit in an odd condition. If you need the exact order, follow our Fenix A320 cold-and-dark start-up sequence. If the cockpit screens are blank, flickering or ignoring inputs, use our blank avionics troubleshooting steps before blaming the MCDU.
Why does the route import but still look wrong?
That usually points to a route conflict or navdata mismatch, not a broken INIT page. If the import completes but you see discontinuities, missing waypoints or strange airways, clear any route loaded in the MSFS planner and review the F-PLN page leg by leg. When your dispatch source and the aircraft are using different navdata, some procedures or waypoints may need manual correction.
When is this a wider Fenix problem?
If the EFB, displays and MCDU are all misbehaving, the issue is probably broader than INIT REQUEST. In that case, treat it as an aircraft-wide fault and work through our Fenix A320 not working in MSFS checks.