Mission: Thames Episode 8 FERRY SPECIAL: Every Crossing of the River Thames!

แชร์
ฝัง
  • เผยแพร่เมื่อ 13 ก.ย. 2024

ความคิดเห็น • 3

  • @harryelliott4310
    @harryelliott4310 หลายเดือนก่อน +1

    Mission Thames

  • @metrowake11
    @metrowake11 หลายเดือนก่อน

    Did you flag the 555 down clearly? If so, that’s unacceptable, I mean really someone could be visually impaired and can’t see bus coming, so if unsure a driver should stop just in case.
    There are TfL stops south of Chessington until edge of Dorking on 465, as well as to two stops before Redhill on 405

    • @ItsAllAboutTheJourney
      @ItsAllAboutTheJourney  หลายเดือนก่อน

      Ah interesting, I see both these places are in Surrey too!
      As for the incident with the 555, I flagged the bus down clearly as with any other bus in London. The thing that makes this worse is, If you watch the video closely in the section where the bus drives past, the driver looks round to see me for a good couple of seconds but still drives straight past.
      On a more worrying experience I had travelling on the 555 between Hatton Cross and Heathrow, there was a couple onboard headed for the airport with large suitcases who didn't speak great English. They were clearly flustered and in a rush to make their flight. A minute or so after arriving into Hatton Cross, the driver left the cab to have an unscheduled smoke break for almost five minutes. The couple understandably took offence to this and confronted the driver when he returned. From this conversation I learnt that the previous 555 service had not run without any explanation from the company or the driver, and were now over an hour later than they originally intended. The driver, who was absolutely fuming at this point, proceeded to dangerously drive the bus as quickly as he could to Heathrow, well over the speed limit. I never knew whether the couple made their flight or not but I have a feeling they may never use the 555 again - I likely never will.
      I've contacted Diamond Bus twice now to complain about these incidents. Beyond an automated SMTP acknowledgement from their mail server, I'm still yet to hear any response from the company.