Runway and SID assignment SBGL

SimBrief Dispatch
1

Hello,

Thank you for your support, which is always so quick and accurate. I come here with another request that will help a lot.

RUNWAY ASSIGNMENT --------------------------------------------------------------------

Normal real runway operation at SBGL is as follows (preferably):

Departures: RWY 10 and 33
Landings: RWY 15 and 28

Sometimes Simbrief suggests takeoff from RWY 15 and landing on RWY 10, which is not impossible to happen, but it is an exception when one of the runways is undergoing maintenance. Takeoff from RWY 15, if not done at the correct time and in coordination, could lead to a serious conflict with aircraft approaching SBRJ, just 6nm away. Likewise, the approach and landing on RWY 33 can also cause serious conflict. Landing at RWY 10 and taking off at RWY 28 are also avoided in normal operations due to taxi time.

Therefore, I suggest setting the runway operation as default as mentioned above to make things easier for pilots if there is no ATC online.

SID ASSIGNMENT --------------------------------------------------------------------------

1- If possible, give priority to PCX1B SID over PCX3A SID. This will ensure that traffic is free from unnecessary altitude restrictions during the departure procedure.

2- When the first fix on the route is SIDUR, give priority to UGROK1A SID instead of EVRAD1A SID. UGROK1A is a smaller departure and saves time en route.

3- I don’t know if this is possible: some real flight plans (Gol Airlines) for SBBR, SBGO, SBEG and other locations start with the EDNAM fix (EDNAM UM409 ISIPI / EDNAM UM409 MIMIP UZ8 DEXED DCT SIRUL, etc). However, there is no SID with this transition, so the Simbrief indicates that there is no available SID and many people choose to make the OMNI dep. But, the EDNAM fix is ​​on the same airway and only a few miles ahead of the ENSOD fix and, in real life, the SID that ATC authorizes in these cases is EVRAD1A with ENSOD transition. Is it possible to create a logic where when the first fix on the route is EDNAM, the SID is EVRAD1A.ENSOD?

Before:

{7EC9C95D-A1BA-46B6-9A2E-2E2D0AF8E7AF}
{7EC9C95D-A1BA-46B6-9A2E-2E2D0AF8E7AF}1640Ă—690 225 KB

After:

{B86E8703-78D2-4470-B601-63082E9821A2}
{B86E8703-78D2-4470-B601-63082E9821A2}1632Ă—822 303 KB

NOTE: Speaking of SBGL, it would be great if you could add the ILS Z of runway 15 to the database (in the aircraft FMC). This is the main procedure of the whole airport. I know that the go-around starts before the start of the runway, but there are other procedures with the same circumstance that exist in the database, such as RNP Z.

Thank you for your support!

2

Hello, I have let the team know, thanks.

1 Like
3

There is the ALMOS 2A and 2B for runways 28 and 33. It’s only for runways 10/15 that there is no SID connecting directly to EDNAM.

Based on somewhat similar requests I made some time ago, I don’t think that’s possible at the moment.

However, there is a different solution: multiple preferred routes. Currently, EDNAM UM409 ISIPI is the only preferred route from SBGL to SBBR. But you can add e.g. ENSOD UM409 ISIPI as another preferred route.

Simbrief will automatically prioritize preferred routes which connect to a SID over preferred routes that don’t, based on the selected runway.

That won’t solve the issue of people manually entering the route via EDNAM, but at least most users who just go with whichever route Simbrief provides by default will get one connecting with a SID for their runway.

Regards,

Tim

1 Like
4

Thanks, Tim!

Takeoffs are most often made from runway 10, so there is no SID for EDNAM, generating this “problem”. I imagined it would be difficult to create something for this, but if we can configure the rest of the suggestions I would be very grateful, it would improve a lot.

Thanks

5

Runway 10:

Screenshot 2025-06-10 at 19.29.43
Screenshot 2025-06-10 at 19.29.432648Ă—1568 602 KB

Runway 33:

Screenshot 2025-06-10 at 19.30.54
Screenshot 2025-06-10 at 19.30.542648Ă—1568 600 KB

When creating a new flight, Simbrief will automatically pick the route for which there is a SID connecting to the first waypoint (based on the runway it auto-selected for departure).

If you then change the departure runway runway on that page, say Yes to “Do you want to select new SIDs/STARs for these runways?” and when choose Find New Route when it asks “The first waypoint in your route does not connect with any SIDs. Would you like to search for a different route, or keep your current route?”, then Simbrief will automatically pick whichever of the two preferred routes connects with a SID.

This (in addition to picking the referred departure runways only – has to be done by the main Simbrief developer when he has time) will address the SID problem in a reasonable way, IMO.

Regards,

Tim

6

Hi Tim,

Thanks a lot. You are absolutely right.

The most important adjustment would actually be the runway logic (takeoff at 10 and 33, landing at 15 and 28), if that can be done and set as default.

Regards

7

Hi, I have applied the runway logic and avoided PCX3A/EVRAD1A SIDs.

Best regards,

1 Like
8

Thanks a lot my friend Derek!