ADF Navigation A Practice Test

The key idea here is what information a simple nav log should capture for a leg when distance and airspeed are already known. You want to list the leg in order (leg number), the route (from-to), and the distance, plus the direction you plan to fly (true course). Crucially, you also compute and record the estimated time en route by dividing the distance by the airspeed, and you include both the planned departure time and the estimated arrival time. This combination gives you a complete snapshot of where you’re going, how to head there, and how long it should take to get there, starting from your departure time.

This approach is practical because it directly uses the given distance and airspeed to produce a timing estimate, and it specifies the direction with true course, which is the standard reference for planning legs in a simple nav log. The other items listed—magnetic course, bearing to the north, or wind direction alone—don’t provide the full, actionable timing and heading information needed for planning a leg with known distance and airspeed. Wind can affect actual travel time, but the essential log entry uses distance/airspeed for an initial ETA, with the departure and arrival times tied to that estimate.