WARP DRIVE LUDICROUS / Article from The Hitchhiker's Guide to the Quantum World

last update: Feb 26 '17

by Erich Habich-Traut, Thursday, February 25., 2017

Hamilton Ventura WatchWARP DRIVE LUDICROUS (The infinite improbability drive)
In April 2016 I experienced a strange phenomenon.

On a boring long distance drive I wanted to see if time could be influenced by concentrating on some fixed star in the sky, whilst being in a moving vehicle.

The car did move at a fixed speed with cruise control, for the majority of the ride. I experienced that my subjective time appeared to slow down, and it took longer to reach my destination than expected.

But this may not have been just a subjective experience,
because electronics were affected.

(Or, because my car electronics were affected,
the impression that time was dilating arose?)

28th of April 2016
There were all sorts of complications with my Android based navigation car computer. It kept crashing, freezing, locking up, leading to complete temporal and spatial disorientation whilst driving through the Netherlands.

Tank emptySo whilst I was driving, I did not appear to be moving as I should have, inside the car (to an external stationary observer the kilometres DID however advance objectively, as the GPS record shows), my petrol gauge appeared to inch towards empty, faster than it should have.

Yet in the end, everything worked out all right.

I had lost all perception of time during the drive, a most terrifying experience, the drive appeared to take almost forever.

This is probably something many late night drivers can attest to,
whether they drive cars or trucks across continents.

Then the question of course must be, why do I talk of lost time when I actually gained it?

I certainly did not move at significant relativistic speeds in my vehicle (any speed is relativistic, only the effect varies).
Believe it or not, something fishy was going on.

Goes to VlissingenUsing GPS records and the video I have revised locations, speeds and times of the night time drive from the 27th to 28th of April 2016.

Before boring the reader with the details of the calculations, I will say that that the car appears to have travelled for a short time at a speed of 396 km/h (respectively 198km/h, which still exceeds the top speed of the vehicle by 20km/h).

The nitty gritty

Navi stateThe video shows that the in-car time was 1:22, when near the city of Goes in Zeeland, in the vicinity of the former Easter Island statue billboard and near Tramper Technologies NL.

Google maps confirms that it takes 20 minutes and 27 km from there to reach the destination.

The screenshot on the left shows an arrival time of 1:47am, but it was actually 1:42am.

Bergen Op Zoom to GoesFROM Bergen op Zoom to Tramper Technologies is a distance of 33 km, taking 17 minutes.

All those figures are close to the expected values.

It is a little unexpected that I arrived at the final destination 5 minutes earlier than Google maps predicted (1:42h instead of 1:47h), despite driving below the speed limit.

I drove by cruise control slower than the allowed speed of 130 km/h.
The video shows the cruise control set at 114km/h, which after substracting the inaccuracy of the odometer is actually only 110 km/h.

Bergen Op Zoom to Vlissingen The REAL DISCREPANCY is, that when I looked at my watch at the moment when the car computer crashed at Bergen op Zoom, it said 1:17h.

BUT, when I looked at the watch near Tramper Technologies, the watch said 1:22h.

I apparently covered the distance of 33 kilometers in 5 minutes
at a calculated speed of 396 km per hour (33km / 5 min x 60 min).

In the video I am heard as saying that the computer crashed 5-10 minutes ago.
With the benefit of hindsight, I am sure that it was 5 minutes.

Even at 10 minutes I would have been driving at almost twice the set cruise control speed.

I'm missing between 7 to 12 minutes, that I cannot account for
(17 min. objective time - (x) min. subjective time).

Possible explanation
If I had not immediately noticed the car computer stopping at Bergen op Zoom, then the remembered time of 1:17 would be wrong and could explain the rapid transit from there to Tramper Technologies (I'm not making these names up).

But, alas, I kept looking at the thing every few seconds.
It is unlikely I missed it crashing.

Occam's razor
What is more likely, that I travelled at 396 to 198 km/h, or that I snoozed?
I didn't snooze, because the following happened:

The experiment
StarsOn a boring long distance drive I wanted to see if time could be influenced by concentrating on some fixed star in the sky, whilst being in a moving vehicle.

This happened at Bergen op Zoom.

What went through my mind at the time was, that it might be possible by focussing on a destination to get there, faster. Really fast. (Wormhole, anyone? A wormhole is a hypothetical feature that would be a shortcut linking two separate points in spacetime.)

The drive started at 22:19h on 27th April and ended at 1:42am the following day.
The observed effect was recorded between 1:17 am and 1:22 am with a margin of error of 5 minutes.

The test result is inconclusive

Inconclusive was also a NASA test with a Warp field Alcubierre drive in 2013...
Ref.: https://en.wikipedia.org/wiki/Alcubierre_drive

Did I mention that it was a very clear night when I travelled and the night before too, apparently?
Someone had reported that the stars appeared to be changing colors although I saw nothing of the sort.

If car fuel consumption is affected just by the presence of car occupants, every other factor being the same, it would shed new light on lab results of fuel efficiency figures.

The car industry may not be entirely to blame for worse than expected mileage figures from any given vehicle, under the same conditions but with different drivers.

This effect may not be caused by Newtonian physics.


Let's file this under Science Fiction.

File retrieval

This is a DeLorean Motor Car I photographed and photoshopped in 1999.

It's an illustration from 'The Museum Of The Future", a website aptly named, online since 1998, now at http://startrek.ehabich.info.

Unfortunately my car, a Dacia Lodgy, did not have a flux converter.