The main idea is how ARPA and radar work together on a ship. ARPA uses radar data to automatically track targets and calculate risk metrics like closest point of approach (CPA) and time to CPA. In practice, these functions are combined in a single system: an integral ARPA couples the ARPA processing with the radar sensor, giving you automatic plotting, tracking, and risk assessment within one unit. That’s why this statement is the best: an integral ARPA includes both ARPA and RADAR. It reflects how modern navigation gear is designed to operate as a unified system, where radar provides the data and ARPA provides the automatic tracking and threat calculations. The other options don’t fit because ARPA depends on radar data to function, ARPA isn’t a weather-monitoring tool, and radar can indeed be integrated with ARPA.

In an aircraft INS, two reference frames are used to describe motion: a navigation frame and a body frame. The navigation frame is a local tangent plane to the Earth at the current position, oriented with north, east, and down. It’s effectively a small, Earth-fixed frame that moves with your location but is aligned to the surface and gravity, so you can express position and velocity in meters north and meters east (with down for altitude). The body frame, on the other hand, is fixed to the aircraft itself. Its axes move and rotate with the airplane—typically forward along the fuselage, to the right wing, and downward (depending on convention). The INS uses attitude information to rotate between these frames, converting measurements from the moving, body-fixed perspectives to the Earth-referenced navigation frame (and vice versa). So the best description is that the navigation frame is a local tangent plane aligned with north/east/down, while the body frame is fixed to the aircraft.

In the navigation-frame formulation, the fundamental INS equations describe how orientation, velocity, and position evolve using gyros and accelerometers. The rate of change of attitude comes from the angular rates measured by the gyros, expressed in the body frame and mapped into the navigation frame by the current orientation. Once the attitude is known, the accelerometer output (specific force) is rotated into the navigation frame and, after subtracting gravity, gives the acceleration of the platform in the navigation frame. Integrating that acceleration updates velocity, and integrating velocity updates position in the navigation frame. This sequence—attitude change driven by body angular rates, velocity update from transformed specific force minus gravity, and position update by integrating velocity—is the standard set of INS navigation equations in the navigation frame. Other statements omit essential pieces (attitude can change with motion; velocity depends on gravity-corrected specific force, not inertial forces alone; and gravity-free models don’t describe real motion).

Timing alignment between INS and GNSS is crucial because the INS propagates the navigation solution by integrating IMU data in its own time frame, while GNSS provides position and velocity at its precise epoch. If the INS and GNSS clocks are not synchronized within sub-millisecond accuracy, the GNSS measurement effectively refers to a slightly different moment than the INS-predicted state. That small time mismatch translates into a mismatch in the measurement model that the fusion process must reconcile. The filter then introduces clock bias or timing error terms to absorb this mismatch, and these errors propagate into the estimated position and velocity. With ongoing dynamics, even a tiny time offset can accumulate and appear as non-negligible errors in the fused solution. Since the timing error affects both how fast you think you’re moving and where you think you are, it is not limited to altitude and it degrades the overall accuracy of the solution.