picrelated is the only screenshot I took on a 90 minute flight, and it was the key part of that entire journey. Here's an explanation:
Couple months ago I recreated the 1929 schedule of a BALAIR Fokker monoplane airliner from Frankfurt to Marseilles. The leg of the journey which gave me the most trouble was Basel to Geneva. Seeing large lakes and a big valley north of Geneva, my original plan was depart Basel and fly directly south following a road (the A2) through some (Jura) mountains, locate the valley and lakes (Biel and Neuchatel) then follow the valley (Swiss Plateau) to Geneva.
But I fucked up, I didn't measure the distance between Basel and the first lake, and so didn't know how long it would take to fly south across the mountains. I took off from Basel, turned south and followed the A2 through the Jura Mountains but my road disappeared, I was unsure of the correct valley, saw no lakes, and became immediately lost. The terrain was hospitable is as fuck with no emergency landing spots, and I zig zagged for 30 minutes until I found my lakes and valley, then continued on the land.
This time I tried it differently, I went out of my way a little while, following the A3 east (to Zurich) until it crossed the Aare river, then followed the river and Swiss Plateau along the eastern edge of the Jura mountains to Geneva. Very safe, very comfortable to navigate, and with very little lost time.
This image shows the intersection of the A3 roadway and the Aare River, just before I turned right. Finding this intersection was probably the hardest navigational challenge of the entire flight.
>>1510443You should get TA on the ground, but no RA. You didn't get any alerts with traffic right there? And the AI didn't go around? What the fuck.
