Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Changing the default squawk code and flight nr

Featured Replies

Is it possible to change the default squawk code (1200) and same question regarding the default flight nr (285) on the right hand side of the yoke? TIA,

Squawk code is probably the FSX code, so it might depend on the loaded flight...? Probably have a look in the .FLT file that you load. At least I can't see it in the panel state files, so it's probably FSX loaded flight fed. sig.gif

  • Author

It appears to revert back to 1200 even when loading a saved flight but I'll check again.Anyone knows if the flight nr can be changed?

Flight NR can be changed by changing it in the VC?

Marc M.
 

It appears to revert back to 1200 even when loading a saved flight but I'll check again. Anyone knows if the flight nr can be changed?
Well yeah, that's what I say... when you load a flight (that probably contains 1200 as XPDR code), it seems to load exactly that into the NGX. So you need to check the .FLT file and try to change it there. Go to the [Avionics.0] section and change the Transponder=1200 setting to something you like, maybe 2000 as that's a standard code many use. Yoke flight numbers can be changed in the panel state [FlightControls] section, but it seems a bit more complicated as they are probably not stored as a simple number (the one you can see in the VC) but rather an animation angle. Would have to tinker with it in order to know how it works exactly. A good start would be to set 123 on the left and maybe 789 on the right yoke, save that panel state and analyze the file. sig.gif
Is it possible to change the default squawk code (1200) and same question regarding the default flight nr (285) on the right hand side of the yoke? TIA,
I'm not sure whether this would be true in airline operations, but at the company I work for, ( a Part 135 charter operator), the SOP is for all flight crews to reset their transponders to 1200 before shutting the aircraft down at the end of a flight.The reason for this is to prevent inadvertently transmitting an IFR squawk code that might already be in use by another aircraft if the transponder accidentally gets taken out of "standby" mode at the beginning of the next flight.Anyway, on my NGX installation (HF4), the aircraft seems to always load whatever squawk code was saved in the panel state from the previous flight. But it does not save the settings of the VHF COM radios #1 and#2 for some reason. Strange thing is that it does save the COM 3 frequencies...

Jim Barrett

Licensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.

It appears to revert back to 1200 even when loading a saved flight but I'll check again. Anyone knows if the flight nr can be changed?
As far as the numbers on the yoke, sure.. You just click the numbers up or downwith the mouse. The flight number used by the airplane itself, or in the FMC willnot preset the yoke numbers. You have to dial them in.. Hope this is what you meananyway..

Mark Keith

  • Author
Squawk code is probably the FSX code, so it might depend on the loaded flight...? Probably have a look in the .FLT file that you load. At least I can't see it in the panel state files, so it's probably FSX loaded flight fed. sig.gif
Checked the saved .flt file and like you guessed I found the 1200 code in it but even when I changed it after completely shutting the NGX down when I turn the battery and standby power back ON there is that 1200 code again so I think I'll just have to learn live with it and the fact that both FSX and the NGX are both american products :( Like someone else said it might actually be a wise thing to make it a habit always leaving it at 1200 which makes sense. Reason I wanted to change the default code is I would prefer to have 7000 instead of 1200 since that is the equivalent to 1200 here in Europe where I do most of my flying. As for the flight nr that was easier to fix, just re-saved the panel state after I had put in the nr I want to use as a default. Thanks everyone who contributed!
Checked the saved .flt file and like you guessed I found the 1200 code in it but even when I changed it after completely shutting the NGX down when I turn the battery and standby power back ON there is that 1200 code again so I think I'll just have to learn live with it and the fact that both FSX and the NGX are both american products wink.png Like someone else said it might actually be a wise thing to make it a habit always leaving it at 1200 which makes sense. Reason I wanted to change the default code is I would prefer to have 7000 instead of 1200 since that is the equivalent to 1200 here in Europe where I do most of my flying. As for the flight nr that was easier to fix, just re-saved the panel state after I had put in the nr I want to use as a default. Thanks everyone who contributed!
Well I'm in EUR as well, but I have yet to see one airline that sets a different standard than 2000. 7000 is definitely VFR. Other than that, regarding the FLT file, it's cruical to edit the correct one, of course... (haha Big%20Grin.gif) maybe do the following to be on the safe side: Set up a flight in the free flight window (doesn't have to be NGX). Give it a unique name and check "make this the default flight". Edit that newly created FLT file. Then whenever you start FSX and edit your flight from the free flight screen (and not load another flight), you might have more success with the standard squawk. In fact I'll try it out later today and see if I have success there. sig.gif
  • Author
Well I'm in EUR as well, but I have yet to see one airline that sets a different standard than 2000. 7000 is definitely VFR. Other than that, regarding the FLT file, it's cruical to edit the correct one, of course... (haha Big%20Grin.gif) maybe do the following to be on the safe side: Set up a flight in the free flight window (doesn't have to be NGX). Give it a unique name and check "make this the default flight". Edit that newly created FLT file. Then whenever you start FSX and edit your flight from the free flight screen (and not load another flight), you might have more success with the standard squawk. In fact I'll try it out later today and see if I have success there. sig.gif
:( I'm positive I edited the correct .flt file and the new code (7000) did show up first when loading the NGX but like I said above once I had put the NGX back to cold & dark then when I switched the power on again I was back with 1200. As for 1200 vs 7000 I might be wrong but as I always understood it both these codes are considered VFR codes and the codes you will use if you haven't been assigned another code. The only difference between the codes is the 1200 one is mostly used in North America where the 7000 is used in Europe. Might have misunderstood this though, guess for anyone interested should be fairly easy to Google. Honestly it's not really a big deal so please don't vaste you time on this if you don't want to for your own needs.

Do you use LINDA or have FSUIPC registered Richard?

  • Author
Do you use LINDA or have FSUIPC registered Richard?
Yes, I'm using the registered version of FSUIPC.
Yes, I'm using the registered version of FSUIPC.
Do you you know how to setup an Auto script in FSUIPC?
ipc.writeUW(0x0354, "0x2000")

Squawk 1200 shows up in all my planes. That is normal. If you fly on VATSIM you would change it to 2200 if no ATC was around and 2000 for Oceanic. If ATC was on then they would tell you what Squawk to use. Just change it manually, everyone else does. It is very simple and fast.

Paul Deemer

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.