April 2017
  • Day15

    Weyman. Final numbers.

    April 15, 2017 in Canada ⋅ ⛅ 13 °C

    All the way home.

    Went out to check the runway condition and found it firm over almost the entire length and width... certainly enough for my light plane. Met Don M. there and he offered to drive me to Fredericton airport so I could retrieve my plane.

    Done. After landing I avoided turning on the pavement and just pushed it backwards to taxiway CB. Did not nee to use the bog boards under the wheels to cross the grass; saw no depressions in the turf.

    Final numbers for the trip:
    Countries visited: 3
    Total distance flown: 7140 km (3855 nm)
    Average ground speed: 195 km/hr (105 knots)
    Total flying time: 36.6 hours
    Longest day flying: 7.5 hours
    Fuel consumed: 567 L
    Fuel economy: 12.5 km/L (29.5 mpgUS)
    Oil consumed: 300 mL
    Read more

  • Explore, what other travelers do in:
  • Day13

    (CYFC) Fredericton NB. Home...

    April 13, 2017 in Canada ⋅ ⛅ 7 °C

    Almost.
    This is where the skis-off trip started.

    Had to clear customs here. The process for pilots in Canada is that if no customs personnel is there at the appointed time, you get to go (you make a phone declaration before your last flight leg into Canada). So I taxied over to tie down at Capital Airways, Fredericton;s FBO.

    At 7.5 hours, this was the longest flying day of the trip.

    I have now uploaded the 906 photos and movies from the trip. Here is the latest one.
    Read more

  • Day13

    (58N) Reigle airport, Palmyra, PA

    April 13, 2017 in the United States ⋅ ☀️ 13 °C

    Mogas fuel stop.Now this airport is definitely within the community.

    Had an issue that nearly resulted in me landing back at Front Royal airport instead. About an hour into the flight, my tablet rebooted itself. That was not unusual and not alarming; consumer electronics is generally not as reliable as aviation gear. But when it rebooted, the GPS was unavailable. That WAS alarming. Since my primary panel was crippled because its unreadable memory card. It only showed were I was relative to the next waypoint on my route... no map data. If I could not easily locate myself on a map, I carried no paper charts, the method of continued safe progress was impacted. This was just as I was coming up on Washington and New York airspace.

    Over a 15 minute period I tried a few things and forced shutdowns of the tablet hoping it would recover. I called air traffic control telling them I was going to land at Front Royal airport instead. Since I had landed there on the way south, it was on the primary panel. So when i reached Front Royal, I told them I was arriving and begin descending from my 7500 ft cruise altitude. Around 4000 feet the GPS returned to the tablet.

    So I told Front Royal I would not be landing, got back on route, climbed back up, and called air traffic to get flight following again.

    After touchdown at Reigle I was assaulted by the stench of fresh pig manure from nearby fields. It was still better than gas fumes.
    Temperature cooler. Put on my sweater.
    Read more

    J B

    Did you ever figure out the nav issues?

    5/15/17Reply
    GUFY trips

    My android/tablet occasionally has lapses similar to this, bit this was bay far the longest. They are normally less of a concern since my aviation panel gps nav system continues to work, and that is much more reliable. But the map nav on that system was down because of its memory card issue.

    5/26/17Reply