# Dispatch Will Not Allow Altitude Entered **URL:** \ **Category:** Dispatch\ **Created:** [April 7, 2025, 6:01am UTC](https://forum.navigraph.com/t/dispatch-will-not-allow-altitude-entered/19262 "2025-04-07T06:01:07Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![markjpeterson](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@markjpeterson](https://forum.navigraph.com/u/markjpeterson)\ **Post date:** [April 7, 2025, 6:01am UTC](https://forum.navigraph.com/t/dispatch-will-not-allow-altitude-entered/19262/1 "2025-04-07T06:01:07Z")
Please review these two flights. Both are from KHAF (Half Moon Bay) to KRHV (Reid Hill View San Jose). As can be seen in attachment 1, I selected 7000 feet but the flight plan refuses to generate anything but F035 (attachment 2) . This seems to be a factor of the class B airspace floors, but makes no sense on an IFR flight. 3500 is dangerous for the terrain and ATC could certainly get you to 7000 altitude, or at least 5000 within the class B. I then added an additional waypoint (attachment 3), and it now allows F050 in the flight plan (attachment 4). Again it does not support 7000 requested. It presents no step levels. If I edit the selected route to try and add altitudes to waypoints it has no effect unless I deselect Detailed Navlog. Interestingly it does honor the 7000 altitude request if I do deselect Detailed Navlog, but I can’t use a flight plan without Detailed Navlog with Beyond ATC. Any help is appreciated. ![Altitude](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/7/6/767b8b8695b5eeff019d31212faff8f28b5343fe.jpeg) ![Altitude 2](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/0/6/06e779af4f382ec4012a3ab98b5d4a55522d4f53.jpeg) ![Altitude 3](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/6/d/6d73ad4a8762c64d18d60dcdb1d3ad357115ae49.jpeg) ![Altitude 4](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/5/b/5b894dfa3cccfa4b3cf1f11fadcd43943e5224d7.jpeg) ---
**Author:** ![markjpeterson](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@markjpeterson](https://forum.navigraph.com/u/markjpeterson)\ **Post date:** [April 23, 2025, 12:10am UTC](https://forum.navigraph.com/t/dispatch-will-not-allow-altitude-entered/19262/2 "2025-04-23T00:10:03Z")
I just wondered if there is any way to get an update on this issue. I rechecked the user guide for Simbrief but can’t find any reason this is happening. Any help is appreciated. ---
**Author:** ![SimBrief](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/simbrief/32/4850_2.png) [@SimBrief](https://forum.navigraph.com/u/SimBrief)\ **Post date:** [April 25, 2025, 5:12am UTC](https://forum.navigraph.com/t/dispatch-will-not-allow-altitude-entered/19262/3 "2025-04-25T05:12:20Z")
Hi Mark, sorry for the delay. Basically this boils down to the climb distance + descent distance requirements. SimBrief’s C182 profile currently uses high speed climbs and descents, requiring about 15nm to climb to 5,000 ft, and around 22 nm to descend from there. This route is only 35 nm, so it couldn’t quite reach 5,000 ft. In real life of course you could climb at max rate instead, but SimBrief doesn’t support those profiles for the C182 right now. That being said, I’ve done some tuning to reduce the cruise portion buffer, and also account for departure/arrival vectoring when restricting the cruise altitude. This should help slightly at least. Best regards, ---
**Author:** ![markjpeterson](https://avatars.discourse-cdn.com/v4/letter/m/e95f7d/32.png) [@markjpeterson](https://forum.navigraph.com/u/markjpeterson)\ **Post date:** [April 25, 2025, 8:03am UTC](https://forum.navigraph.com/t/dispatch-will-not-allow-altitude-entered/19262/4 "2025-04-25T08:03:25Z")
Thanks appreciate the help and explanation.