They are a bit different for sure but I’ve never been in an Airbus flightdeck while flying, so I can’t say if sounds are realistic or not. But maybe you were before?
I’m pleased with existing ones. Anyway they are different if you compare 319 320 and 321, obviously…
This happens to me. I’ve been flying with Realturb only though. Next flight will be without.
1 Like
I tend to use FR24 for the aircraft I am flying by downloading its data over a seven day period into an excel spreadsheet and then follow that schedule. If the aircraft doesn’t exist anymore (e.g. Northwest A319) I will try to closely match it.
N653AW
| DATE | FROM | TO | FLIGHT | FLIGHT TIME | STD | STA |
|---|---|---|---|---|---|---|
| 01-Aug-24 | Phoenix (PHX) | Las Vegas (LAS) | AA2053 | 00:41 | 10:04 | 11:17 |
| 01-Aug-24 | Las Vegas (LAS) | Phoenix (PHX) | AA1944 | 00:48 | 12:02 | 13:17 |
| 01-Aug-24 | Phoenix (PHX) | Portland (PDX) | AA2660 | 02:09 | 14:08 | 16:45 |
| 01-Aug-24 | Portland (PDX) | Phoenix (PHX) | AA2660 | 02:13 | 18:25 | 21:00 |
| 02-Aug-24 | Phoenix (PHX) | Cincinnati (CVG) | AA2990 | 03:42 | 09:51 | 16:28 |
| 02-Aug-24 | Cincinnati (CVG) | Phoenix (PHX) | AA2990 | 03:28 | 18:30 | 19:18 |
| 03-Aug-24 | Phoenix (PHX) | Nashville (BNA) | AA1216 | 02:57 | 08:30 | 13:58 |
| 03-Aug-24 | Nashville (BNA) | Phoenix (PHX) | AA1216 | 03:04 | 14:43 | 16:22 |
| 03-Aug-24 | Phoenix (PHX) | Monterey (MRY) | AA2476 | 01:19 | 16:52 | 18:35 |
| 03-Aug-24 | Monterey (MRY) | Phoenix (PHX) | AA2476 | 01:28 | 19:15 | 21:08 |
| 04-Aug-24 | Phoenix (PHX) | Omaha (OMA) | AA2190 | 02:09 | 08:51 | 13:34 |
| 04-Aug-24 | Omaha (OMA) | Phoenix (PHX) | AA2190 | 02:11 | 14:26 | 15:14 |
| 04-Aug-24 | Phoenix (PHX) | Madison (MSN) | AA1835 | 02:52 | 15:16 | 20:30 |
| 05-Aug-24 | Madison (MSN) | Dallas (DFW) | AA1538 | 01:40 | 06:45 | 09:10 |
| 05-Aug-24 | Dallas (DFW) | San Antonio (SAT) | AA460 | 00:42 | 12:50 | 14:00 |
| 05-Aug-24 | San Antonio (SAT) | Phoenix (PHX) | AA466 | 01:47 | 14:45 | 15:01 |
| 05-Aug-24 | Phoenix (PHX) | Columbus (CMH) | AA751 | 03:27 | 15:51 | 22:36 |
| 06-Aug-24 | Columbus (CMH) | Dallas (DFW) | AA2380 | 01:58 | 05:36 | 07:16 |
| 06-Aug-24 | Dallas (DFW) | St. Louis (STL) | AA2897 | 01:23 | 07:09 | 09:04 |
| 06-Aug-24 | St. Louis (STL) | Dallas (DFW) | AA2897 | 01:10 | 09:49 | 11:38 |
| 06-Aug-24 | Dallas (DFW) | Houston (IAH) | AA1873 | 00:40 | 12:39 | 14:03 |
| 06-Aug-24 | Houston (IAH) | Phoenix (PHX) | AA2983 | 02:07 | 14:48 | 15:39 |
| 06-Aug-24 | Phoenix (PHX) | El Paso (ELP) | AA365 | 00:58 | 16:29 | 18:41 |
| 07-Aug-24 | El Paso (ELP) | Phoenix (PHX) | AA642 | 00:53 | 06:02 | 06:21 |
| 07-Aug-24 | Phoenix (PHX) | San Diego (SAN) | AA2057 | 01:01 | 07:22 | 08:35 |
| 07-Aug-24 | San Diego (SAN) | Phoenix (PHX) | AA2006 | 00:57 | 09:23 | 10:47 |
| 07-Aug-24 | Phoenix (PHX) | Albuquerque (ABQ) | AA2180 | 00:50 | 12:21 | 14:36 |
| 07-Aug-24 | Albuquerque (ABQ) | Phoenix (PHX) | AA2180 | 00:52 | 15:29 | 15:49 |
| 07-Aug-24 | Phoenix (PHX) | Sacramento (SMF) | AA582 | 01:35 | 16:39 | 18:33 |
| 07-Aug-24 | Sacramento (SMF) | Phoenix (PHX) | AA2860 | 01:30 | 19:24 | 21:16 |
5 Likes
Anyone noticed the A319 or A320 speeding up uncontrollably on final when flying an ILS? 3 times now, once in the A320 and twice in the A319, i’m stable at 170kts, flaps 2, on the glide slope. I dial the speed down to Vapproach and drop the gear, and as it starts to slow I add in flaps 3, when suddenly the plane speeds up, the back of the aircraft balloons and the nose dives, but the plane refuses to descend despite showing a now -1500fpm descent rate to try and keep the GS and the plane speeds up to 190/200ish KTS, but the throttle remains idle on the engine displays.
This never used to happen, and now it does all the time. Its 100% a bug but I haven’t seen it mentioned anywhere else. Seems to be since the update to the A319 / A321 post-release.
1 Like
I haven’t seen this but I tend to switch the SPD mode from managed to manual when I dial the speed down, so what I dial in is what speed it heads to. I usually go for a couple of kts higher than the speed the descent/approach perf page spits out for approach speed. I’ve not tried doing it in managed mode, but it’s not happening in manual speed mode (for me) and I’ve flown the Fenix a lot lately. Are you leaving it in managed mode but with a speed override? Is that what isn’t working?
no I’m in manual speed mode, if Vref for landing is 133, I set the MCP speed to 143, then as it slows, add in flaps 3 and the issue occurs. I can’t get it to slow down to get to flaps 4. Its not my flying, this is a bug in the aircraft flight model. I have uninstalled and reinstalled and it still happens.
I have 3000+ hours in a 737, 1000+ in the airbus. I know what I’m doing and the fenix isn’t behaving right, its not every flight, but mostly the A319 and A320 and only since the last update.
Have never experienced any issues like that in the A320 (over a thousand hours as well).
Started flying the 319 and 321, no issues like that either.
Maybe post in their Discord support channel.
1 Like
I’ll keep an eye out for this, but I can’t say I’ve encountered it. I had one strange throttle event almost like you describe, but only after landing, and I have no idea what that was about.
Yes happened to me to in the a321. Nose down pitch but not actually descending, slightly before flare.
1 Like
I only have the A320 but it happens to me periodically. Stabilized approach, a few hundred feet over the ground and all of a sudden, the jet accelerates. By the time I’m over the threshold, I’m doing 160+.
1 Like
At what point of the descent do I engage “Approach Mode”. Did a search on this forum but didn’t find anything conclusive.
Once your 30 degrees off the LOC and within 5-10 miles of the IAF (10-15 NM from the actual runway) on the ILS. I usually wait until I can see both pink diamonds on the main display to engage APPRCH mode.
IRL (or vatsim) this is where ATC will normally vector you to and then clear you for the approach from, which is when you would actually engage APPRCH mode
Hey, it’s always different and can’t be tied to one region.
This happened a few A320 builds ago, back in Block 1, when it happened very often. This is probably supposed to simulate the loss of the GPS signal. When it starts oscillating, you look under GPS in the MCDU and you can see that several satellites show no reception.
I don’t know a solution, but I certainly haven’t had it for a year. Only now again for the first time, but only one flight.
1 Like
Just a tiny bit of coding required I’m sure 
2 Likes
Literally, the only reason why I got into planes was seeing those stairs fold up in the 737-200 and watching the wheels go up…
Those are literally the two things to why I am into planes…
2 Likes
I haven’t flown it since the update but I’m sure your supposed to leave the A320 in managed mode for the approach… Unlike the 737 where you have to wind down the speed manually…
I’ve read from the beginning when a few real world pilots were on here…
Their practice was to arm approach (especially when being vectored, and especially in busy airspace where there is high work load so they don’t forget, especially if “approach mode” doesn’t arm for some reason ) then select managed speed mode so they can keep the speed up, especially when asked to keep their speed up in busy airspace…
Then, when on ILS unless (once again) asked to keep speed up by atc, select manage speed mode (closed window) and the plane should slow down automatically to its landing speed especially since approach mode has already been activated…
That’s what I’ve always done with the A320…
So basically…
When I’m in the star…
- I select manual speed so it keeps a steady decent rate, especially if “arm appch mode” activation is comes up early in the star…
- arm approach mode
- then I can keep speed up to give me a steepish rate of decent… Basically keeping up with the vnav/lnav profile
- then I use the manual speed mode as is… I.E slowing down/speeding up the plane especially when instructed by atc
- Your usual, going through from 240 to 210 to 180 knots, for example, manually slowing the plane through to 210 then through to 180 when basically on the final leg to final approach
- as I’m slowing down, I can then use slats/flap 1 setting when at the appropriate flap speed as required (if you are in managed mode and still in a STAR especially if it’s a long arrival star… flaps often engages/triggers the approach mode, which ends up slowing the planes rate of decent as the plane slows down to final approach speed which can mess everything up… Queenstown RNP is one great example )
- Once set on the respective approach be it ILS or engaged on the RNP…
When I’m coming up to like 8nm from runway I engage manage speed mode, drop the landing gear (if you watch A320 vs 738 you’ll notice that the 73s usually deploy the landing gear quite late on in approach) and the plane will do all the rest as it slows down to landing speed and set flaps as required, using a bit of speed brake if your speed isn’t washing off and the plane, like i say, does all the rest… - disengage A/T when required…
I remember reading somewhere that pilots tend to keep A/T on for most of the approach in the A320 vs the A/T being disconnected much earlier on in the 737
2 Likes
Yes maybe a few Boeing habits bleeding through to Airbus for me. Trouble is that the aircraft is often not slowing down fast enough. The A319 is different than the A320 in this regard. So too fast for flaps 1, too fast for flaps 2 etc. It’s quite hard. Maybe like you say I try manually slowing the a/c down earlier before approach (I’m usually in managed mode then). I’ve not done a managed speed approach to land yet as I always think it leaves it too late to slow down so I don’t trust it. Maybe I’ll give it a go next flight and see what happens. Thanks for your thoughts.
Loaded up the sim, got a prompt to enter user name and P/W. Never happened before. Loaded the info, got a “failed to fetch” error. Went the “forgot password”
option, another failed to fetch notice. Any idea what the issue is?
Same as you, probably a Fenix server issue ?
1 Like
Anyone know if this has been resolved?