From a0bf58a30e2ebdfc6b6cbbddc113b40a9e7e68bb Mon Sep 17 00:00:00 2001
From: Eurus <105340988+AkaiEurus@users.noreply.github.com>
Date: Sat, 30 May 2026 03:24:30 +0800
Subject: [PATCH] fix(mavlink): leave LOITER_TO_ALT yaw unspecified (#27510)

---
 src/modules/mavlink/mavlink_mission.cpp | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/modules/mavlink/mavlink_mission.cpp b/src/modules/mavlink/mavlink_mission.cpp
index 3a2cf35594d..5084d8042d3 100644
--- a/src/modules/mavlink/mavlink_mission.cpp
+++ b/src/modules/mavlink/mavlink_mission.cpp
@@ -1488,6 +1488,9 @@ MavlinkMissionManager::parse_mavlink_mission_item(const mavlink_mission_item_t *
 			mission_item->force_heading = (mavlink_mission_item->param1 > 0);
 			mission_item->loiter_radius = mavlink_mission_item->param2;
 			mission_item->loiter_exit_xtrack = (mavlink_mission_item->param4 > 0);
+			// MAV_CMD_NAV_LOITER_TO_ALT has no yaw field. Leave yaw unspecified so multicopters don't
+			// use the zero-initialized default as an unintended north-facing heading setpoint.
+			mission_item->yaw = NAN;
 			break;
 
 		case MAV_CMD_NAV_ROI: