Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Feb 13, 2014 21:56:41 GMT
It basically is used in this context to indicate that the buses will be driven by specific drivers, as they do not changeover en-route (such as Route 136). This means that there will effectively be two buses with the running number 211 - The first one will be a E40H, with one driver, the second one will be for the next drivers and will be a ALX400.
This means that only a small number of drivers need to be trained on the bus, and in the event of a mechanical problem, there is a readily available spare bus.
|
|
|
Post by M1104 on Feb 21, 2014 17:17:13 GMT
The provisional date for the extension to Elephant is Saturday, March 29th.
Source LOTS
|
|
|
Route 136
Feb 26, 2014 17:08:51 GMT
via mobile
Post by Mokujin on Feb 26, 2014 17:08:51 GMT
So now that the 136 is being extended, I wonder whether the N136 change to N436 will take place?
|
|
|
Post by snoggle on Feb 26, 2014 17:35:26 GMT
So now that the 136 is being extended, I wonder whether the N136 change to N436 will take place? LOTS say the renumbering happens the same day - 29 March 2014.
|
|
|
Post by rmz19 on Mar 19, 2014 0:25:12 GMT
Why is it that the current N136 is being renumbered to N436?, if this does go ahead then won't it cause confusion as the N436 will not reflect the 436?. Surely it's more logical to keep the number as N136, regardless of the 136 extension to Elephant & Castle....
|
|
|
Post by sid on Mar 19, 2014 11:15:08 GMT
Why is it that the current N136 is being renumbered to N436?, if this does go ahead then won't it cause confusion as the N436 will not reflect the 436?. Surely it's more logical to keep the number as N136, regardless of the 136 extension to Elephant & Castle.... I agree, either leave it as it is or give it a totally new route number that has no connection with any daytime route
|
|
|
Route 136
Mar 19, 2014 12:03:21 GMT
via mobile
Post by Nathan on Mar 19, 2014 12:03:21 GMT
Why is it that the current N136 is being renumbered to N436?, if this does go ahead then won't it cause confusion as the N436 will not reflect the 436?. Surely it's more logical to keep the number as N136, regardless of the 136 extension to Elephant & Castle.... I agree, either leave it as it is or give it a totally new route number that has no connection with any daytime route Well the 436 has more of a connection with the current N136 route. So it kind of makes sense to rename it in this manor.
|
|
|
Route 136
Mar 19, 2014 12:24:08 GMT
via mobile
Post by sid on Mar 19, 2014 12:24:08 GMT
I agree, either leave it as it is or give it a totally new route number that has no connection with any daytime route Well the 436 has more of a connection with the current N136 route. So it kind of makes sense to rename it in this manor. [/ quote] Why? Surely passengers will assume it follows the daytime route if they are (by TfL reckoning) likey to assume the N136 follows the daytime 136 route via Southampton Way althoughI I reckon the 'N' prefix might just give them a clue like it does with the N21 for example not going to Moorgate, Old Street and Newington Green.. Its another example of TfL wasting money trying to solve 'problems' that don't actually exist and causing uneccasary confusion into the bargain.
|
|
|
Post by rmz19 on Mar 21, 2014 0:08:08 GMT
I agree, either leave it as it is or give it a totally new route number that has no connection with any daytime route Well the 436 has more of a connection with the current N136 route. So it kind of makes sense to rename it in this manor. The 436 may have a connection with the N136 regarding their routings, but it also has total connection with the 136 for obvious reasons, despite the extension. Therefore it is more logical I think to just keep the current numbering system, avoiding any potential confusion.
|
|
|
Post by Nathan on Apr 11, 2014 14:58:39 GMT
Just got an email about the 136/N136 changes: "Dear Stakeholder We recently consulted on proposals to extend bus route 136 from Peckham to Elephant and Castle. Thank you to those who provided their views. Following the consultation, and the analysis of the responses, we can now confirm that we intend to proceed with the proposal. The planned introduction date is Saturday 10 May 2014. We also originally proposed re-numbering route N136 so it adopted the number N436. However we are no longer proposing to take this forward and the N136 number will be retained. A copy of the consultation reports and our response to issues raised can be found by using this link: consultations.tfl.gov.uk/buses/routes-136-and-343If you have any questions regarding the consultation please contact me. Yours sincerely"
|
|
|
Post by DT 11 on Apr 11, 2014 15:58:36 GMT
Excellent news about the N136 retaining it's number, this is great news.
|
|
|
Post by snoggle on Apr 11, 2014 22:16:16 GMT
Many of the Spider Maps have been updated to reflect the 136 extension from 10 May 2014. Elephant & Castle hasn't been done yet but I think all of the rest have been for Southwark and Lewisham Boroughs. They're on the old TfL "origin" website but linked through from the new one.
|
|
|
Route 136
Apr 13, 2014 17:59:54 GMT
via mobile
Post by rmz19 on Apr 13, 2014 17:59:54 GMT
That's good news, logic has prevailed!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 23, 2014 19:37:34 GMT
It has been reported elsewhere the reason N436 was dropped was because of the cost of fitting new blinds. Are new blinds not needed anyway for the 136 extension?
|
|
|
Post by DT 11 on Apr 23, 2014 19:49:27 GMT
It has been reported elsewhere the reason N436 was dropped was because of the cost of fitting new blinds. Are new blinds not needed anyway for the 136 extension? The New WOB blinds have 136/N136, Elephant & Castle, but not N436, apparently the idea to renumber it came afterwards. Doesn't surprise me that it was too costly, such a wasteful idea imo.
|
|