Incorrect Initial Cruise Altitude (FL160) on MUVIN Departures out of OJAI

SimBrief Dispatch
1

Hello SimBrief Team,

I am writing to report an altitude profile issue regarding departures out of Queen Alia International Airport (OJAI) via the MUVIN SID.

Currently, whenever a flight plan is generated using the MUVIN departure, SimBrief automatically restricts the initial cruise altitude to FL160, followed by a step climb at the TAPUZ waypoint to reach the final requested cruise flight level.

As a result, many pilots end up filing FL160 as their main cruise altitude in their flight plans. As an Air Traffic Controller at OJAI, this creates significant coordination issues and unnecessary workload, as FL160 is unrealistically low for these routes.

Could you please review the altitude restrictions tied to the MUVIN SID and the segment leading to the TAPUZ waypoint in your routing database? Removing or correcting this FL160 restriction so that SimBrief assigns the proper cruise altitude from the beginning of the flight would be highly appreciated.

Thank you for your time and your continuous support for the flight simulation community

2

Without the restriction, the route does not pass IFPS validation:

ifps
ifps1600×3072 400 KB

Which is why it gets added in the first place.

Regards,

Tim

Edit: real-world flights adopt a similar (if even more conservative) profile for MUVIN departures, capping at FL140 and occasionally step climbing even later than TAPUZ:

3

Hi Tim,

Thanks for the explanation and the screenshot! That makes perfect sense regarding the routing.

However, the issue we are seeing happens during the export/pre-file process. When pilots send their flight plan to the network (e.g., VATSIM), SimBrief automatically populates the main “Cruise Altitude” field with FL160 instead of the flight’s final cruise level.