Recently I videotaped a simulated flight from Troutdale, OR [KTTD] to Aurora, OR [KUAO]. The aircraft was the default Cessna 172 with the Reality Expansion Pack installed.
This was on my home flight simulator, which runs X-Plane 11.25 on a Windows 10 machine with an i7 processor (4.2 GHz overclocked to 4.6 GHz), 32 GB RAM, and a GTX 1080i video card. I was getting an average of 31 frames per second during the flight. I use three 32″ flat panel monitors, Saitek FIP gauges, yoke, throttle quadrant, and rudder pedals. I also use Saitek radio, switch, and multi-function devices.
Back in 2012 I took a solo motorcycle trip from Oregon to Colorado that spanned 10 different states in 16 days (Oregon, California, Nevada, Arizona, Colorado, Wyoming, South Dakota, Wyoming (again), Montana, Idaho, and back to Oregon). One of my goals after setting up my flight simulator was to take that same trip virtually in a Cessna 172.
I began that virtual trip a few weeks ago and am currently parked at an airstrip in Durango, Colorado. I have mapped the trip to include takeoffs and landings at the same towns where I had overnight stays on my original motorcycle trip, and I even have landings and takeoffs in towns where I stopped for lunch. I’m trying to mimic the same route as realistically as possible, just in the transportation medium of flight.
One of the aspects of this trip I have implemented is detailed flight logs. I started by making notes in a spiral notebook as I flew, writing down flight date, departure airport, destination airport, and a few minor details along the way such as waypoints and altitude. I refined those notes to include more detail, then decided to use a formal flight log form that I fill out for each flight.
I used a spreadsheet to create a printable form that I put on a clipboard and fill out as I fly. I make notes every time I change course or altitude, with timestamps. About the only thing I don’t write down is my airspeed.
So far the logs have worked great, and I have really enjoyed the detail-oriented aspect of the process. Flying, once you’re at cruising altitude, can be somewhat boring, especially if you use autopilot. Making notes as you fly keeps your brain occupied, and gives you a reason to pay attention to your gauges and the other aspects of the flight, rather than just zoning out and getting bored.
You may download a printable PDF version of the logbook here.
The original Excel spreadsheet is available here [XLSX].
The Delta column is for denoting changes in altitude or bearing. I often use < or > to show changes in course for left or right, respectively, and up or down arrows with X fps or -X fps to show changes in altitude. For Altitude, I write the altitude I was at when I began the delta.