146 Professional

Hi. There are many different types of RNAV equipment available to 146 operators. The most worst to use was the Trimble system (know as the ‘tremble’ to long suffering crews). Operators later standardised on various versions of the GNS system. All were capable of BRNAV, but ISTR only the GNS-XLS Enhanced was capable of being approved for RNAV procedures. I not sure that the UNS version modelled for the JF146 was ever standard fit for the aircraft. I’ve used later version of the UNS (on corporate jets) that were capable of full RNAV including approach, but I don't think the early models were any more than BRNAV capable. From a ‘Simming’ viewpoint, if the required SID/STAR is in the database, I would use it - but check that the various waypoints are correct first. btw, when using using RNAV routes/approaches/departures, other than removal as part of a routing, it is not permitted to amend or extra insert waypoints.

To add to the discussions above. During a turnaround at an out station, if no APU or GPU available were available, the preference would be to leave engine #4 running. This is because pax entry/de-plane would normal be conducted through the left front and rear stairs. If fitted, his would be via the aircraft’s own steps. Great care and a full briefing to baggage loaders would be required, otherwise extra paperwork would follow. In circumstances were no APU/GPU and engine 1 or 4 is kept running, a x-start procedure can be used to start the other engines. Another reason that crews could find the APU not available on ground is airfield noise restrictions banning their use. btw, there is also the dreaded DC battery cart ‘dark start’ procedure. But such talk is best left until Halloween…

I believe the behaviour of the raindrops on the windows is connected to airspeed. So as airspeed increases, the rain drops will appear to flow rearwards over the windows and speed up. I suspect in this situation, when stationary after pushback, this would have been caused by the wind speed. Mark - Just Flight

We can reproduce the issue, but the difficulty comes with finding a specific set of steps to reliably reproduce it. it is something we have looked into and is something we would like to get fixed, but without a reliable way of reproducing it, it can quickly turn into a very time-consuming task with little rewards. Mark - Just Flight

Hi Xender. I can’t speak for Just Flight, but in practice it wasn’t possible to walk through the cabin when in the freight mode since there was always a freight net positioned just aft of the fwd vestibule preventing easy access aft. It could be moved aside (not easy), and while you could always look, you didn’t enter as to get down the side of the containers you would have to be very small indeed. When carrying horse boxes, pax seats would be positioned aft of the boxes for the grooms and veterinarians. Lots of extra fire containment and warning, plus the large rear freight door and the tail support required (NEVER forget the tail support if you want a quiet life!).

In service, very, very few pilots used the DSC mode for descent. It is far easier to descend in IAS/Mach with TMS N1 Sync (to achieve the required ROD) and to transit to V/S mode when required, while (of course) observing the minimum N2 limits.

FYI, for correct target: The 146-100 and -200 intermediate cruise speed is 0.65M. The 146-300 intermediate cruise speed is 0.67M. With AP engaged and ALT HOLD at FL280 and FL290 the total fuel burn would be about 2,000 kg/hr. TMS would normally be used in N1 sync mode during the cruise.

@knidarkness Unfortunately, we can’t give permission for the redistribution of our files, as that would be in breach of the licence and copyright terms we have agreed with other parties. You're more than welcome to distribute the mod with the instructions on how users can edit the panel.cfg file themselves, we are just unable to give permission for the original or edited panel.cfg file to be redistributed. Mark - Just Flight

I have been trying for several hours to make the thrustlevers work with these LVARs but although I do get some sort of movement the thrustlevers seem to jump straight back to the position I have put them at in the virtual cockpit with the mouse. I have made sure that there are no double axis assignments in MSFS2020 or SPAD.NEXT. I did notice that there are actually three LVAR variants available once MSFS2020 is running: e.g. PED_MID_ENG1_THROTTLE PED_MID_ENG1_THROTTLE_il PED_MID_ENG1_THROTTLE_SHAFT_VC Any more suggestions would be very much appreciated.

We would be happy to work together with FSDT on this if they decided it was something they would like to add to GSX. This would be a decision for FSDT to take though with GSX being their product. Mark - Just Flight

We currently have an update to the UNS-1 in development and we do have a fix for this procedure included in that. This update will be included in both the 146 and F28 once we have tested and approved it for release. Mark - Just Flight

Thanks for reporting this. We have replicated this and we'll pass this on to the UNS-1's development team to investigate further. Mark - Just Flight

Looking at our reference material for the UNS-1 I don't believe this would be possible on the PATH VNAV page. On the real unit, it looks like the VNAV page will only display "@" altitudes (i.e. a fixed altitude for each waypoint). I suspect this is so the UNS-1 can calculate a decent path more easily and doesn't have to factor in if an aircraft is going to be "at or above" or "at and below" a certain altitude at each waypoint. In our simulation of the UNS-1, the PATH VNAV is automatically populated with the waypoints and altitude restrictions on a STAR, and we did add up/down arrows to the altitudes as a quality-of-life addition so that users can more easily see any altitude restrictions without references charts. Mark - Just Flight

We chose to have the airstairs deployed when the "Start Boarding" option is triggered so that passengers would always be able to board the aircraft regardless of whether the gate has a jetway. However, we have logged this on our internal feature request tracker to see if there is a way that we can detect if a gate has a jetway, so that the airstairs only deploy if needed. Mark - Just Flight

Thank you for the feedback. We have logged this on our internal bugs/feature request tracker for our development team to look into. Mark - Just Flight

It likes to do pitch oscillations too, especially at lower speeds. I flew into EGLC now, and on the last legs of the approach as the plane slows down to 210 and then 185, it becomes a veritable lowrider. GS was completely useless so I had to hand-fly the whole thing. At higher speeds it was perfectly fine.

In the mean time if the issue is that you have too many company routes and it is hard to find them in the list, you could add a task in windows to clear out that folder once a day (or each time you log in / start your computer etc) so the folder won't fill up with old flight plans

The beacon lights that we have simulated in the 146 are asynchronous and are based on the type of lights shown in this video: https://youtu.be/WMDocoUILq8?si=WUAZloGVA3SHTpYF&t=187 I do seem to recall that when we researched this there were different flash sequences from aircraft to aircraft, so we just had to pick one of the sequences for our simulation (we have the type that flashes at different speeds so they go in/out of sync with each other). We will log a request to increase the brightness of the beacon lights on out internal feature request tracker. Mark - Just Flight

Yep, it works when i enter 07000, a bit strange and unnecessary complication, but it works.