Difference between revisions of "2010-04-09 60 36"

From Geohashing
imported>Danatar
(Report 3!)
 
imported>Danatar
(double time-traveller airhash ;-))
Line 42: Line 42:
 
File:2010-04-09_60_36_neva.jpg|Lake Ladoga and Neva River east of Saint Petersburg
 
File:2010-04-09_60_36_neva.jpg|Lake Ladoga and Neva River east of Saint Petersburg
 
</gallery>
 
</gallery>
 +
 +
 +
==Tracklog==
 +
The logger was on Central European Time (UTC+1). Log will follow once I find out how to upload it.
 +
 +
 +
==64 105==
 +
When looking at the tracklog, I found out that the one mentioned above was the second hashpoint I had passed on that day. At 9:23 CET (my tracklogger) / 17:23 Japanese time (my internal clock) / 16:23 local time the plane passed within 80 metres of the 64 105 hashpoint, in a probably uninhabited part of the Krasnoyarsk region in Siberia. The 60 36 hashpoint I passed at 13:20 CET / 21:20 Japanese time / 16:20 local time. Thaaaat means: I visited the second hashpoint, 69 degrees or 3435 km distant, three minutes before the first one, i.e. almost as a [[Time-Traveller Geohash]]. Or the plane was flying >1000 km backwards per minute. LOL
 +
  
 
[[Category:Expeditions]]
 
[[Category:Expeditions]]

Revision as of 20:02, 13 April 2010

Fri 9 Apr 2010 in Zubovo, Russia:
60.2350413, 36.3068176
geohashing.info google osm bing/os kml crox

Location

Today's location is near the towns(?) Markovo and Kiyno (sorry, no Cyrillic letters available).

Country: Russia; Federal district: Northwestern; Federal subject: Vologda Oblast (RU-VLG)


Expedition

Danatar

At the end of my trip to Japan, it was finally time to go home. I flew from Nagoya to Tokyo, changed the plane and started towards Europe. During the trip, I had my new GPS logger active and every few minutes I looked at it to make sure it still had reception and to check if we were approaching any hashpoints.

We passed meridian after meridian without hitting a hashpoint. The longitude coordinates were counting down rapidly, latitude was creeping slowly as we had a mostly western route. While flying over Siberia, we came very close to at least two hashpoints, but passed them by. While flying through the 60 36 graticule and approaching the longitude of the hashpoint, the latitude offset was nearing the desired 14 minutes 6 seconds. But would I reach both at the same time? My heart was beating faster. As I came nearer and nearer to the hashpoint, I set my camera to rapid mode and held the release button down. Careful checking of the pictures afterwards told me that I had been near enough to the hashpoint. Hooray! Pictures out of the window and of my mad grin followed. The plane continued on its route, as if nothing had happened.


Template:Virgin graticule

Airgeohashballoon.png
Danatar earned the Air geohash achievement
by reaching the (60, 36) geohash on 2010-04-09 by Boeing 777-300ER.
2010-04-09 60 36 departure.jpg
EasyAsPi.PNG
Danatar has visited an Easy Geohash
by reaching the (60, 36) geohash on 2010-04-09 without really trying.
2010-04-09 60 36 neva.jpg

With me, there were lots of people (up to 292 passengers + crew, but I saw some spare seats; there were 71 in my group) at the hashpoint, but I guess they don't count as geohashers ;-) Also, the outside temperature at the hashpoint according to the plane's display was -51 °C.



Tracklog

The logger was on Central European Time (UTC+1). Log will follow once I find out how to upload it.


64 105

When looking at the tracklog, I found out that the one mentioned above was the second hashpoint I had passed on that day. At 9:23 CET (my tracklogger) / 17:23 Japanese time (my internal clock) / 16:23 local time the plane passed within 80 metres of the 64 105 hashpoint, in a probably uninhabited part of the Krasnoyarsk region in Siberia. The 60 36 hashpoint I passed at 13:20 CET / 21:20 Japanese time / 16:20 local time. Thaaaat means: I visited the second hashpoint, 69 degrees or 3435 km distant, three minutes before the first one, i.e. almost as a Time-Traveller Geohash. Or the plane was flying >1000 km backwards per minute. LOL