<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Breaking: Link Derailment @ O&amp;M</title>
	<atom:link href="http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/feed/" rel="self" type="application/rss+xml" />
	<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/</link>
	<description>Transit in the Greater Seattle Area</description>
	<lastBuildDate>Fri, 12 Mar 2010 17:54:04 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Light Rail Derailment Blamed on Operator Error - Seattle Transit Blog</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-91571</link>
		<dc:creator>Light Rail Derailment Blamed on Operator Error - Seattle Transit Blog</dc:creator>
		<pubDate>Tue, 22 Dec 2009 23:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-91571</guid>
		<description>[...] Transit&#8217;s preliminary report on last month&#8217;s Link derailment is complete.  The train derailed while leaving the O&amp;M facility, blocking one track and thus [...]</description>
		<content:encoded><![CDATA[<p>[...] Transit&#8217;s preliminary report on last month&#8217;s Link derailment is complete.  The train derailed while leaving the O&amp;M facility, blocking one track and thus [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MetroJD</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-83932</link>
		<dc:creator>MetroJD</dc:creator>
		<pubDate>Sun, 22 Nov 2009 04:38:40 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-83932</guid>
		<description>We don&#039;t have that many supervisors... yet! : )</description>
		<content:encoded><![CDATA[<p>We don&#8217;t have that many supervisors&#8230; yet! : )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MetroJD</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-83931</link>
		<dc:creator>MetroJD</dc:creator>
		<pubDate>Sun, 22 Nov 2009 04:31:02 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-83931</guid>
		<description>Auxilliary track and crossover speed is not to exceed 10mph.</description>
		<content:encoded><![CDATA[<p>Auxilliary track and crossover speed is not to exceed 10mph.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-83763</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sat, 21 Nov 2009 09:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-83763</guid>
		<description>New system, new problems. Bugs to work out. In the case where Gary called his wife to have her check the news, he probably ended up knowing more about the derailed train than the operator did at that point. The control center does not always explain why we&#039;re doing something, they just give us instructions and we follow them.
I was nearly mobbed by angry passengers at Beacon Hill and Mt. Baker Stations wanting to know what was going on. I had no information to give them because I had just come on shift. I was thrown into the thick of things without knowing what was going on. I requested that the control center make a station PA announcement if possible to let people know what was going on.
I know my PA announcements are heard because when I get on the mic at Tukwila to tell someone that &quot;the doors are enabled for their use, push the red button on the door to open it&quot;, they go right for it... but I think they believe it&#039;s going to bite them or something, because the first push or two is usually too light, and the doors don&#039;t respond! : ) Look for the green LED lights lit up around the red button... that means the doors are enabled. We don&#039;t leave the doors wide open at the terminals during bad weather because it&#039;s cold outside.
A tip on &quot;canned&quot; announcements: When the announcement is that a train is being held &quot;due to traffic ahead&quot;, if it&#039;s in the Downtown Transit Tunnel it means there is a bus at the platform ahead, and the train is waiting for the bus to leave. Out on MLK it&#039;s usually to keep interval spacing between trains. SDOT has complained to Sound Transit that trains mess up the traffic signals when they bunch up on MLK... so the control center tries to keep trains at least 7 minutes apart, especially during rush hour.
&quot;We are experiencing a service delay&quot; is a more general announcement, just meaning that the trip is going to take a little longer than anticipated.
Please note that the intercom to the operator is for emergencies only. If you have an emergency and don&#039;t get a response right away, re-push the button and speak to the operator, stating the nature of your emergency.
Operators are becoming apathetic to the emergency intercom calls because 99.9% of the time people are pushing that red button on the bottom of the spring-loaded seat thinking it&#039;s the seat release. Operators generally just cancel the calls, because they&#039;ve answered so many calls that have turned out to be mistakes.</description>
		<content:encoded><![CDATA[<p>New system, new problems. Bugs to work out. In the case where Gary called his wife to have her check the news, he probably ended up knowing more about the derailed train than the operator did at that point. The control center does not always explain why we&#8217;re doing something, they just give us instructions and we follow them.<br />
I was nearly mobbed by angry passengers at Beacon Hill and Mt. Baker Stations wanting to know what was going on. I had no information to give them because I had just come on shift. I was thrown into the thick of things without knowing what was going on. I requested that the control center make a station PA announcement if possible to let people know what was going on.<br />
I know my PA announcements are heard because when I get on the mic at Tukwila to tell someone that &#8220;the doors are enabled for their use, push the red button on the door to open it&#8221;, they go right for it&#8230; but I think they believe it&#8217;s going to bite them or something, because the first push or two is usually too light, and the doors don&#8217;t respond! : ) Look for the green LED lights lit up around the red button&#8230; that means the doors are enabled. We don&#8217;t leave the doors wide open at the terminals during bad weather because it&#8217;s cold outside.<br />
A tip on &#8220;canned&#8221; announcements: When the announcement is that a train is being held &#8220;due to traffic ahead&#8221;, if it&#8217;s in the Downtown Transit Tunnel it means there is a bus at the platform ahead, and the train is waiting for the bus to leave. Out on MLK it&#8217;s usually to keep interval spacing between trains. SDOT has complained to Sound Transit that trains mess up the traffic signals when they bunch up on MLK&#8230; so the control center tries to keep trains at least 7 minutes apart, especially during rush hour.<br />
&#8220;We are experiencing a service delay&#8221; is a more general announcement, just meaning that the trip is going to take a little longer than anticipated.<br />
Please note that the intercom to the operator is for emergencies only. If you have an emergency and don&#8217;t get a response right away, re-push the button and speak to the operator, stating the nature of your emergency.<br />
Operators are becoming apathetic to the emergency intercom calls because 99.9% of the time people are pushing that red button on the bottom of the spring-loaded seat thinking it&#8217;s the seat release. Operators generally just cancel the calls, because they&#8217;ve answered so many calls that have turned out to be mistakes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael Nerode</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-83359</link>
		<dc:creator>Nathanael Nerode</dc:creator>
		<pubDate>Fri, 20 Nov 2009 03:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-83359</guid>
		<description>The Chicago els were in ungodly awful shape for a very long time -- and are very different construction from the Seattle elevated.  Actually flying off an elevated line is very different from a derailment on an El with escape walkways and guardrails.

I certainly think they need to find the source of the problem, but I am pretty sure they are going to -- protocol requires a full investigation for *every* incident, unlike with cars.</description>
		<content:encoded><![CDATA[<p>The Chicago els were in ungodly awful shape for a very long time &#8212; and are very different construction from the Seattle elevated.  Actually flying off an elevated line is very different from a derailment on an El with escape walkways and guardrails.</p>
<p>I certainly think they need to find the source of the problem, but I am pretty sure they are going to &#8212; protocol requires a full investigation for *every* incident, unlike with cars.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael Nerode</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-83358</link>
		<dc:creator>Nathanael Nerode</dc:creator>
		<pubDate>Fri, 20 Nov 2009 03:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-83358</guid>
		<description>I would be shocked if the turnout wasn&#039;t properly interlocked.  That&#039;s really rather cheap to fix, however, so although it would be a terrible design error, it wouldn&#039;t be a hard one to fix.

I&#039;d bet on a mechanical defect in the switch machine instead.</description>
		<content:encoded><![CDATA[<p>I would be shocked if the turnout wasn&#8217;t properly interlocked.  That&#8217;s really rather cheap to fix, however, so although it would be a terrible design error, it wouldn&#8217;t be a hard one to fix.</p>
<p>I&#8217;d bet on a mechanical defect in the switch machine instead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82961</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 18 Nov 2009 23:25:24 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82961</guid>
		<description>Are you certain your PA announcements can be heard? My operator clearly wasn&#039;t – we&#039;d hear the chime, then some mubles and scratching sounds. They should have an automated message before an operator announcement that asks for complete silence, and the HVAC system should shut off so we can hear. Or the volume could be higher!</description>
		<content:encoded><![CDATA[<p>Are you certain your PA announcements can be heard? My operator clearly wasn&#8217;t – we&#8217;d hear the chime, then some mubles and scratching sounds. They should have an automated message before an operator announcement that asks for complete silence, and the HVAC system should shut off so we can hear. Or the volume could be higher!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82960</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 18 Nov 2009 23:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82960</guid>
		<description>Sounds like you were in the dark, too – the higher-ups could have done a better job communicating with operators, too, it sounds like.</description>
		<content:encoded><![CDATA[<p>Sounds like you were in the dark, too – the higher-ups could have done a better job communicating with operators, too, it sounds like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82884</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82884</guid>
		<description>I agree that Sound Transit did a poor job of getting information to passengers. You obviously weren&#039;t riding my train, or you would have heard PA announcements in addition to the &#039;canned&#039; variety.
Everyone seems to be under the impression that the operators know everything that&#039;s going on all the time... that&#039;s not the case. At one point we were instructed to not use the radio unless we had an emergency or the train breaks down. 
My PA announcements were that service delays were being caused by single track operation between Mt. Baker and SODO stations, that is both northbound and southbound trains taking turns using the northbound track, usually two trains in one direction at a time. I couldn&#039;t give time estimates of the delays involved because we had to wait like everyone else until the control center gave us clearance to proceed.
I didn&#039;t withhold that a train had derailed causing a blockage, I didn&#039;t know... at the time all I knew was that there was a blockage on the southbound track at OMF and that we were doing a single track operation in the affected area.</description>
		<content:encoded><![CDATA[<p>I agree that Sound Transit did a poor job of getting information to passengers. You obviously weren&#8217;t riding my train, or you would have heard PA announcements in addition to the &#8216;canned&#8217; variety.<br />
Everyone seems to be under the impression that the operators know everything that&#8217;s going on all the time&#8230; that&#8217;s not the case. At one point we were instructed to not use the radio unless we had an emergency or the train breaks down.<br />
My PA announcements were that service delays were being caused by single track operation between Mt. Baker and SODO stations, that is both northbound and southbound trains taking turns using the northbound track, usually two trains in one direction at a time. I couldn&#8217;t give time estimates of the delays involved because we had to wait like everyone else until the control center gave us clearance to proceed.<br />
I didn&#8217;t withhold that a train had derailed causing a blockage, I didn&#8217;t know&#8230; at the time all I knew was that there was a blockage on the southbound track at OMF and that we were doing a single track operation in the affected area.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82877</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82877</guid>
		<description>&quot;Amateur&quot; would not be the most accurate word. Inexperienced, yes. It&#039;s a new system, and it&#039;s a new experience for just about everyone from operations staff to passengers. I will not speculate about the cause of this particular failure, because I don&#039;t know, I wasn&#039;t there.
I will say that it&#039;s my personal opinion that the &#039;weak link&#039; is not with the operator or the training we receive. Our training is very comprehensive, and operators are proficient in their job, otherwise they wouldn&#039;t still be there.
The fact that all light rail operators were chosen from the ranks of bus drivers means that their situational awareness skills are more finely tuned than those of the average person on the street. This gives me much greater peace of mind when I&#039;m off duty and riding light rail as a passenger.</description>
		<content:encoded><![CDATA[<p>&#8220;Amateur&#8221; would not be the most accurate word. Inexperienced, yes. It&#8217;s a new system, and it&#8217;s a new experience for just about everyone from operations staff to passengers. I will not speculate about the cause of this particular failure, because I don&#8217;t know, I wasn&#8217;t there.<br />
I will say that it&#8217;s my personal opinion that the &#8216;weak link&#8217; is not with the operator or the training we receive. Our training is very comprehensive, and operators are proficient in their job, otherwise they wouldn&#8217;t still be there.<br />
The fact that all light rail operators were chosen from the ranks of bus drivers means that their situational awareness skills are more finely tuned than those of the average person on the street. This gives me much greater peace of mind when I&#8217;m off duty and riding light rail as a passenger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82870</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82870</guid>
		<description>Matt, that&#039;s something you need to take up with Sound Transit. Let them know you were displeased with the lack of accuracy in their delay estimates. They&#039;ve already acknowledged that they could have done a better job in getting information to the people waiting at the station platforms.
I had just come on duty for a southbound trip, not too long after the accident, and I was practically mobbed by people on the platforms from the Beacon Hill and Mt. Baker Stations, wanting to know what was going on. Yes, mobbed, even though I was in a sealed cab! 
They were angry not only about the delay, but because I couldn&#039;t &quot;take two minutes to explain to them what was going on&quot;. 
First off, I just came on duty and didn&#039;t know what happened other than we were running single track operations... I was thrown into the thick of things without really knowing what was going on.
I couldn&#039;t take two minutes because it&#039;s my job to keep the train moving along, not be public relations for Sound Transit. I immediately contacted the control center and informed them of the angry crowds and asked for them to make a station public address announcement, so people would know what was going on. Whether they did or not I have no way of knowing.
I also informed my passengers via PA that service delays were caused by single-track operations between Mt. Baker and SODO stations, and while I didn&#039;t know how long the delays would be, I did know that the train would be continuing as soon as clearance from Link Control was received. We couldn&#039;t give time estimates to passengers because we didn&#039;t know. All the operators could do was wait like everyone else, until they were told they could proceed.
When the control center allowed communications other than emergency transmission or breakdowns, I was in constant contact with them, asking questions like, &quot;is there a bus bridge in place between the stations?&quot;. I wanted to inform my passengers about all their possible travel alternatives.</description>
		<content:encoded><![CDATA[<p>Matt, that&#8217;s something you need to take up with Sound Transit. Let them know you were displeased with the lack of accuracy in their delay estimates. They&#8217;ve already acknowledged that they could have done a better job in getting information to the people waiting at the station platforms.<br />
I had just come on duty for a southbound trip, not too long after the accident, and I was practically mobbed by people on the platforms from the Beacon Hill and Mt. Baker Stations, wanting to know what was going on. Yes, mobbed, even though I was in a sealed cab!<br />
They were angry not only about the delay, but because I couldn&#8217;t &#8220;take two minutes to explain to them what was going on&#8221;.<br />
First off, I just came on duty and didn&#8217;t know what happened other than we were running single track operations&#8230; I was thrown into the thick of things without really knowing what was going on.<br />
I couldn&#8217;t take two minutes because it&#8217;s my job to keep the train moving along, not be public relations for Sound Transit. I immediately contacted the control center and informed them of the angry crowds and asked for them to make a station public address announcement, so people would know what was going on. Whether they did or not I have no way of knowing.<br />
I also informed my passengers via PA that service delays were caused by single-track operations between Mt. Baker and SODO stations, and while I didn&#8217;t know how long the delays would be, I did know that the train would be continuing as soon as clearance from Link Control was received. We couldn&#8217;t give time estimates to passengers because we didn&#8217;t know. All the operators could do was wait like everyone else, until they were told they could proceed.<br />
When the control center allowed communications other than emergency transmission or breakdowns, I was in constant contact with them, asking questions like, &#8220;is there a bus bridge in place between the stations?&#8221;. I wanted to inform my passengers about all their possible travel alternatives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin H. Duke</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82826</link>
		<dc:creator>Martin H. Duke</dc:creator>
		<pubDate>Wed, 18 Nov 2009 14:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82826</guid>
		<description>Yeah, we hated it so much we made it &quot;comment of the day&quot;.</description>
		<content:encoded><![CDATA[<p>Yeah, we hated it so much we made it &#8220;comment of the day&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Comment of the Day - Seattle Transit Blog</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82633</link>
		<dc:creator>Comment of the Day - Seattle Transit Blog</dc:creator>
		<pubDate>Wed, 18 Nov 2009 01:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82633</guid>
		<description>[...] for those elsewhere on the line, communication with at least some riders as pretty abysmal: Comment by Gary &#8212; 2009-11-17 &#8212; 16:31:13 I flew back into Sea-Tac last night and took the light rail [...]</description>
		<content:encoded><![CDATA[<p>[...] for those elsewhere on the line, communication with at least some riders as pretty abysmal: Comment by Gary &#8212; 2009-11-17 &#8212; 16:31:13 I flew back into Sea-Tac last night and took the light rail [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82625</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Wed, 18 Nov 2009 01:28:40 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82625</guid>
		<description>Great comment, Gary.  You left the Link fanatics speechless.</description>
		<content:encoded><![CDATA[<p>Great comment, Gary.  You left the Link fanatics speechless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: L. Smith</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82610</link>
		<dc:creator>L. Smith</dc:creator>
		<pubDate>Wed, 18 Nov 2009 00:44:41 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82610</guid>
		<description>Unfortunately, the &quot;mobile version&quot; of the update (which I had sent to my non-browser dumbphone) cut off the part of the message that told how long delays would be and to bar at NB platforms.</description>
		<content:encoded><![CDATA[<p>Unfortunately, the &#8220;mobile version&#8221; of the update (which I had sent to my non-browser dumbphone) cut off the part of the message that told how long delays would be and to bar at NB platforms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82603</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Wed, 18 Nov 2009 00:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82603</guid>
		<description>I flew back into Sea-Tac last night and took the light rail from Tukwila to the International District, boarding at 9:45 pm. Let me share my own experience. It was not a &quot;minor delay of 10-20 minutes.&quot; The trip to the International District took 1 hour and 20 minutes rather than the usual 30 minutes. The train would just stop for extended periods without moving in the Rainier Valley. There were no announcements of what was going on. I only found out what was going on by calling my wife on my cell phone and asking her to check the news. I pressed the intercom button on the train to call the operator and ask what was going on, and no one responded. There was no alternate bus made available, we were just stuck on the train. While I understand this was an accident, Sound Transit really needs to do a much, much better job of communicating with its ridership and reacting to a contingency next time if it wants to attract and retain riders.</description>
		<content:encoded><![CDATA[<p>I flew back into Sea-Tac last night and took the light rail from Tukwila to the International District, boarding at 9:45 pm. Let me share my own experience. It was not a &#8220;minor delay of 10-20 minutes.&#8221; The trip to the International District took 1 hour and 20 minutes rather than the usual 30 minutes. The train would just stop for extended periods without moving in the Rainier Valley. There were no announcements of what was going on. I only found out what was going on by calling my wife on my cell phone and asking her to check the news. I pressed the intercom button on the train to call the operator and ask what was going on, and no one responded. There was no alternate bus made available, we were just stuck on the train. While I understand this was an accident, Sound Transit really needs to do a much, much better job of communicating with its ridership and reacting to a contingency next time if it wants to attract and retain riders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik G.</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82601</link>
		<dc:creator>Erik G.</dc:creator>
		<pubDate>Wed, 18 Nov 2009 00:25:31 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82601</guid>
		<description>Was it a derail of just a split-the-switch?</description>
		<content:encoded><![CDATA[<p>Was it a derail of just a split-the-switch?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82583</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 17 Nov 2009 23:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82583</guid>
		<description>I think a stock yard is for livestock.</description>
		<content:encoded><![CDATA[<p>I think a stock yard is for livestock.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82582</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 17 Nov 2009 23:43:21 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82582</guid>
		<description>I expect the disrupted service to be similar to what they tell me the disrupted service will be like – 20-minute frequency – and it was not.</description>
		<content:encoded><![CDATA[<p>I expect the disrupted service to be similar to what they tell me the disrupted service will be like – 20-minute frequency – and it was not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://seattletransitblog.com/2009/11/16/breaking-link-derailment-om/#comment-82549</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 17 Nov 2009 23:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://seattletransitblog.com/?p=9797#comment-82549</guid>
		<description>How did you read the operator&#039;s mind?</description>
		<content:encoded><![CDATA[<p>How did you read the operator&#8217;s mind?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
