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

**URL:** <https://forum.navigraph.com/t/incorrect-initial-cruise-altitude-fl160-on-muvin-departures-out-of-ojai/24129>\
**Category:** Dispatch\
**Created:** [August 20, 2026, 12:45pm UTC](https://forum.navigraph.com/t/incorrect-initial-cruise-altitude-fl160-on-muvin-departures-out-of-ojai/24129 "2026-08-20T12:45:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![khalilxdweik](https://avatars.discourse-cdn.com/v4/letter/k/e19b73/32.png) [@khalilxdweik](https://forum.navigraph.com/u/khalilxdweik)\
**Post date:** [August 20, 2026, 12:45pm UTC](https://forum.navigraph.com/t/incorrect-initial-cruise-altitude-fl160-on-muvin-departures-out-of-ojai/24129/1 "2026-08-20T12:45:21Z")

</div>

**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

---

<div class="post-metadata">

**Author:** ![Rodeo314](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/rodeo314/32/103_2.png) [@Rodeo314](https://forum.navigraph.com/u/Rodeo314)\
**Post date:** [August 20, 2026, 1:05pm UTC](https://forum.navigraph.com/t/incorrect-initial-cruise-altitude-fl160-on-muvin-departures-out-of-ojai/24129/2 "2026-08-20T13:05:24Z")

</div>

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

 ![ifps](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/c/9/c90fa12f4dd6949f4b22d16e9d2f0276618cf8c2.jpeg)

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:

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/499962)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/497331)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/496454)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/493095)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/493065)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/492311)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/492306)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

> **[Login | EDI-GLA Real World Flightplan Database | Since 2005](https://www.edi-gla.co.uk/flightplan/489097)**
>
> An extensive database of real world flightplans, current and historical. Intended for flight simulation purposes only.

---

<div class="post-metadata">

**Author:** ![khalilxdweik](https://avatars.discourse-cdn.com/v4/letter/k/e19b73/32.png) [@khalilxdweik](https://forum.navigraph.com/u/khalilxdweik)\
**Post date:** [August 20, 2026, 1:48pm UTC](https://forum.navigraph.com/t/incorrect-initial-cruise-altitude-fl160-on-muvin-departures-out-of-ojai/24129/3 "2026-08-20T13:48:12Z")

</div>

**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.