RJ Professional

Some of the early 146 aircraft, of which we operated a few, had separate high and low intensity nav lights installed, each powered by different electrical busses. The cockpit switch was 3-position: HIGH-OFF-LOW.

Thanks Mark... The panel lights assignment on my Bravo was the issue... All good now... Cheers! Rob

Unfortunately maps not working in the newly updated Warrior and Turbo Arrows either... at least for me... [image: 75365898-6bcd-4eab-bbec-2e24d8351532.jpg]

Glad I found this post. I have been banging my head on the table trying to understand what I am doing wrong. Please fix this ASAP, it's a really awful bug. It has been 6 months since it was reported.....

Thank you for the kind words! I'll be sure to pass these on to the rest of the team. Mark - Just Flight

Nothing new to report on this from our side at the moment. It remains on our internal feature request list as something we would like to add in the future, but we aren't able to provide any time scales for when that may be. Mark - Just Flight

Thanks, #1 is exactly what I asked for and it works.

happy to report all user error (my fault) had the ign selector on the TM Airbus Throttle set to Crank. but it in normal position andd EGT spooled up

General advice, landing and taxi in, typically achieves 450-550C. Brake fans running on chocks after shutdown and before engine start must be for a minimum of 15 minutes. Typically, if you start up and taxi after a minimum of 20 minutes and can start the takeoff with brake temps at a maximum of 200C, all OK. There are tables within the aircraft manuals for calculating the required cooling period if brake fans or BTI are unserviceable. In service, on a hot day with a 30 to 40 minutes turnaround after a max weight landing on a 6,000’ runway, the brakes would be usually be found cool enough to start up and taxi out.

Hi Mark, One of the routes I like to do is EGBB-EICK. Departing runway 15 the RJ picks up the Honiley (HON 113.65) VOR, then I retune to the Compton(CPT114.35) VOR, then I retune to Strumble(113.1) VOR. These I tune on Nav 2 and all work fine. I then tune Nav 2 to the Cork(CRK114.6) VOR but because of the distance away it doesn't tune straight away. I then set up the approach, with the ILS usually for runway 34 on Nav 1 (109.15) So all goes well until I tune the Cork VOR on Nav 2 and the ILS on Nav 1 which on this flight did not work. I have flown this route before and not had a problem. Sometimes I've had the same problem at other airports, Vigo in Spain, Stavanger in Norway. These airports I have flown into at other times with no problem. I always use RJ100 but can't see this being the problem, as no one else on the forum has reported any problems with tunning VOR's it must be something I am doing or not. Great plane by the way. Roger

We did test the RJ up to its maximum crosswind components of 35 knots, and sufficient yaw control was confirmed with the "Rudder Steering Axis" option enabled and disabled to maintain the runway centreline. That's not to say something in the sim, or other changes to the flight model may have changed that at some point post-release though, so we have made a note to double-check that ahead of the next update. The "quirky" nose wheel steering/rudder control that you mentioned is a known side effect of a fix that was created to prevent conflicts between the nose wheel steering axis and rudder axis control assignments. From our testing (as well as feedback we received since that fix was applied), the current method of nose wheel steering is the better logic and should match the behaviour seen in other aircraft that have the option to disable the nose wheel steering from the rudder axis. Mark - Just Flight

Thanks all for your response. I suspect that it may be a spoilers control assignment that may be the culprit. I will check that when I am next in the sim.

I do recall that in the 146 FCOM, there are warnings advising pilots not to change the set altitude or vertical mode during the ALT ACQ phase. So you would let the aircraft acquire the altitude before then making any further adjustments to the autopilot vertical modes. With the RJ sharing a lot of the philosophy from the 146, that is likely good practice to follow in the RJ too. Mark - Just Flight

For reports such as this, we kindly ask that you contact Just Flight Support via the following link: https://www.justflight.com/support Our support team will be able to assist with replicating the behavior and logging a bug on our internal trackers if required: Mark - Just Flight

This is expected behavior as the TOC calculations are essentially the predicated TOC calculated by the data entered in the FMS. Therefore, the TOC point calculations are only re-calculated once something has been executed in the FMS. Note that although these calculations will never be perfectly accurate due to external factors such as temperature and wind, etc, the TOC calculations are something we have logged internally as something to potentially look into improving in the future. Mark - Just Flight

This is expected behavior as the altitude fixes are fixed points derived from the navdata. It is something we have logged internally as something to potentially look into improving in the future. Mark - Just Flight