<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Alaska Airlines Sucks!</title>
	<atom:link href="http://alaskaairlinessucks.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://alaskaairlinessucks.com</link>
	<description></description>
	<lastBuildDate>Thu, 04 Feb 2010 00:25:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>&#8220;Kind of a bang&#8221; &#8212; American still in the flying casket business</title>
		<link>http://alaskaairlinessucks.com/2010/02/kind-of-a-bang-american-still-in-the-flying-casket-business/</link>
		<comments>http://alaskaairlinessucks.com/2010/02/kind-of-a-bang-american-still-in-the-flying-casket-business/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 21:40:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Rants]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=65</guid>
		<description><![CDATA[&#8220;American Airlines still loves its MD-80s, an excellent reason to never fly American.&#8221;
I posted that just two days ago. And as if on cue, another American Airlines Flying Casket MD-80 pulled up lame today. Worse, it exhibited the exact symptoms that both Alaska 261 and my January 2000 flight experienced.
&#8220;&#8230;Passengers and crew heard &#8220;kind of [...]]]></description>
			<content:encoded><![CDATA[<p><em><strong>&#8220;American Airlines still loves its MD-80s, an excellent reason to never fly American.&#8221;</strong></em></p>
<p>I posted that just two days ago. And as if on cue, another American Airlines Flying Casket MD-80 pulled up lame today. Worse, it exhibited the exact symptoms that both Alaska 261 and my January 2000 flight experienced.</p>
<p><strong><em>&#8220;&#8230;Passengers and crew heard &#8220;kind of a bang&#8221; and the plane lost cabin pressure.&#8221;</em></strong></p>
<p><a href="http://seattletimes.nwsource.com/html/localnews/2010974307_apokplanediverted2ndldwritethru.html">Click on this for the AP feed.</a></p>
<p>Eight of American&#8217;s nine daily flights from Dallas to Seattle and SFO are MD-83s. And these weasels charge you extra for baggage, too.</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2010/02/kind-of-a-bang-american-still-in-the-flying-casket-business/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>10th anniversary of Alaska Flight 261</title>
		<link>http://alaskaairlinessucks.com/2010/02/10th-anniversary-of-alaska-flight-261/</link>
		<comments>http://alaskaairlinessucks.com/2010/02/10th-anniversary-of-alaska-flight-261/#comments</comments>
		<pubDate>Mon, 01 Feb 2010 18:30:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Rants]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/2010/02/10th-anniversary-of-alaska-flight-261/</guid>
		<description><![CDATA[A personal word from your Webmaster:
Like thousands of others, 10 years ago today I was horrified to learn of the crash of Alaska Flight 261.
The plane left from Puerto Vallarta, the same day my parents flew home from there on Alaska. It is sheer luck they weren&#8217;t on that plane. Other people I knew weren&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>A personal word from your Webmaster:</p>
<p>Like thousands of others, 10 years ago today I was horrified to learn of the crash of Alaska Flight 261.</p>
<p>The plane left from Puerto Vallarta, the same day my parents flew home from there on Alaska. It is sheer luck they weren&#8217;t on that plane. Other people I knew weren&#8217;t so lucky.</p>
<p>I was in Mexico myself at the time. I almost didn&#8217;t get there, thanks again to Alaska and their POS MD-80s. My flight from Seattle 11 days earlier experienced a problem so severe on take-off that we were forced to make an immediate emergency landing. Something literally blew at the back of the plane. We heard several loud bangs, like minor explosions, and the plane lurched to the right. We all thought we were going to be tarmac dust. Even the stews were fighting back tears, while trying to reassure the passengers. I&#8217;d already written my family a good-bye note with a Sharpie on the drop-down tray. One of the stews asked me to come with her to the back of the plane, just in case they needed help forcing the rear door open. She was crying about her two young children she feared would soon be motherless.</p>
<p>Nothing like looking out the window and seeing the runway lined with fire engines and emergency vehicles. We were all lucky to make it off that plane in one piece, and at least Alaska gave me free drinks on the replacement flight.</p>
<p>But 11 days later, another piece-of-crap Alaska MD-80 flipped upside down and killed 88 people. I  tried to get some answers. Ten years later I&#8217;m still waiting for them. </p>
<p>1. The FAA told me that Alaska filed a &#8220;minor&#8221; incident report on my plane&#8217;s problem. They never went into specifics.</p>
<p>2. After Flight 261 crashed, CBS News reported that &#8220;several loud bangs were heard coming from the back of the plane&#8221; before the crash. That&#8217;s EXACTLY the sound we heard on my plane. </p>
<p>3. For ten years I&#8217;ve been trying to find out if my plane was the same as the one used for Flight 261. Nobody&#8217;s talking.</p>
<p>4. Ten years ago I wrote everyone I knew in the Seattle media, asking them to chase this info down. I gave them plenty of specifics. Not a single one of them ever answered me.</p>
<p>5. Alaska made a big deal in August 2008 when they &#8220;retired&#8221; their last MD-80. That would be about 8 years too late for the victims of Flight 261. Those death traps should have been permanently grounded at least ten years earlier, but Alaska kept flying them long after it was clear they had recurring problems. In the few days and weeks after Flight 261 crashed, an MD-80 pulled into SFO with an engine on fire. In Dallas, another MD-80 full of people nearly plowed up a field. (And btw, American Airlines still loves its MD-80s, an excellent reason to never fly American.) </p>
<p>I&#8217;ve saved all my e-mails and letters regarding Flight 261. I will try to post them here.</p>
<p>Meanwhile, here&#8217;s a <a href="http://seattletimes.nwsource.com/html/localnews/2010922467_alaska29m.html">ten year anniversary story from the Seattle Times</a>. Please take some time to read how the surviving friends and families have had to deal with their loss.</p>
<p>Only a brief passing mention is made of Tom and Peggy Stockley, who were killed on 261. Tom had been the wine writer at the Times for years, an exceedingly credible journalist whose reviews and opinions were highly regarded by consumers and wine industry people alike. There is a memorial bench dedicated to the Stockleys at the foot of East Lynn Street in Seattle, looking out over Lake Union. It&#8217;s right across the street from Pete&#8217;s Market, one of Seattle&#8217;s better known wine outlets.</p>
<p>The tag at the end of the Times article says, <em>&#8220;Seattle Times staff reporter Steve Miletich contributed to this report&#8230;&#8221; </em>Miletich and I worked together at the Bellevue Journal-American 30 years ago. He was one of the first media people I contacted about 261. He was also one of those who didn&#8217;t respond.</p>
<p>>>></p>
<p>For the record, I did not start this web site because of Flight 261. That tragedy was only one in the ongoing saga of Alaska&#8217;s poor service, cheap shortcuts, shoddy maintenance and insults ranging from outrageous baggage fees to &#8220;random&#8221; personal searches and &#8212; this really happened &#8212; being told that I could not have a seat on a plane because I would &#8220;imbalance the load.&#8221; I weigh 170 lbs and had one 30-lb. bag. </p>
<p>There are many good people who work for this airline, and they try hard to make things right. Sometimes they succeed, despite all odds. But there are also unmitigated, greedy, bean-counting assholes who run this airline, and gate agents in Puerto Vallarta, Manzanillo and Burbank (among others) who are either ragingly incompetent or criminally insane. You can be the nicest, most accomodating passenger in the world (which is me 99.9% of the time) and still have some pre-menstrual, man-hating, honeybunch on a bender glare at you and sneer, &#8220;Sir, if you&#8217;re going to be argumentative I&#8217;m going to have to call security!&#8221;</p>
<p>Yeah, well, F you, too, bizzatch! Next time go ahead and call. Let&#8217;s see what they say when I tell them YOU&#8217;RE the one with the attitude problem. </p>
<p>I&#8217;ve had it with Alaska&#8217;s abusive control freaks, fools and idiots who&#8217;ve risen to the level of their own incompetence. (Which, in some cases, doesn&#8217;t take much effort.) And I&#8217;ll bet lots of you have, too.</p>
<p>Admin </p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2010/02/10th-anniversary-of-alaska-flight-261/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Suit filed over fumes from Alaska Airlines plane</title>
		<link>http://alaskaairlinessucks.com/2009/01/suit-filed-over-fumes-from-alaska-airlines-plane/</link>
		<comments>http://alaskaairlinessucks.com/2009/01/suit-filed-over-fumes-from-alaska-airlines-plane/#comments</comments>
		<pubDate>Tue, 13 Jan 2009 01:57:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[In The News]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=51</guid>
		<description><![CDATA[THE ASSOCIATED PRESS
SEATTLE &#8212; An Alaska Airlines passenger is suing the airline over injuries she says she suffered when deicer fumes entered an aircraft at Seattle-Tacoma International Airport on Christmas Eve.
Paramedics treated 25 people who were on an Alaska Airlines plane. Deicer fumes made their way onto the plane and irritated the eyes of passengers [...]]]></description>
			<content:encoded><![CDATA[<p>THE ASSOCIATED PRESS</p>
<p>SEATTLE &#8212; An Alaska Airlines passenger is suing the airline over injuries she says she suffered when deicer fumes entered an aircraft at Seattle-Tacoma International Airport on Christmas Eve.</p>
<p>Paramedics treated 25 people who were on an Alaska Airlines plane. Deicer fumes made their way onto the plane and irritated the eyes of passengers and the crew.</p>
<p>An attorney for passenger Arianna Morgan says she still feels the effects of that exposure and suffers numbness in her hands and fatigue.</p>
<p>The lawyer says the airline had a duty to ensure ventilation systems were closed during deicing.</p>
<p>The lawsuit was filed Monday in federal court in Seattle.</p>
<p>Airline spokeswoman Caroline Boren says the company is concerned about passenger welfare and is reviewing the complaint.</p>
<p>All 143 passengers boarded another plane and continued to Burbank, Calif.</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2009/01/suit-filed-over-fumes-from-alaska-airlines-plane/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Investigators: Gang graffiti exposed in Alaska Air jet cargo holds</title>
		<link>http://alaskaairlinessucks.com/2006/02/investigators-gang-graffiti-exposed-in-alaska-air-jet-cargo-holds/</link>
		<comments>http://alaskaairlinessucks.com/2006/02/investigators-gang-graffiti-exposed-in-alaska-air-jet-cargo-holds/#comments</comments>
		<pubDate>Fri, 17 Feb 2006 05:48:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[In The News]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=3</guid>
		<description><![CDATA[By SUSANNAH FRAME / KING 5 News
Sparkling blue and white airplanes with the well-known Alaska Airlines logo painted on the side of the jets. This is the company image Alaska Airlines wants you to see.
But the KING 5 Investigators have obtained photos of the inside of some of their planes that the company would never [...]]]></description>
			<content:encoded><![CDATA[<p><strong>By SUSANNAH FRAME / KING 5 News</strong></p>
<p>Sparkling blue and white airplanes with the well-known Alaska Airlines logo painted on the side of the jets. This is the company image Alaska Airlines wants you to see.</p>
<p>But the KING 5 Investigators have obtained photos of the inside of some of their planes that the company would never want you to see: image after image of graffiti buried in the bellies of a number of planes where luggage, cargo and animals are loaded.</p>
<p>The pictures show area codes, scratched out symbols, and words that look like they could be related to gangs.<br />
<img class="alignleft" src="http://www.king5.com/topstories/stories/M_IMAGE.10941787f49.93.88.fa.d0.34124322.jpg" border="0" alt="" width="225" height="169" />  <br />
Is this harmless scribbling or really gang graffiti?  We showed our photos to five highly respected gang experts in Arizona, New York, California, and two in the Seattle area.  They all came to the same, disturbing conclusion.</p>
<p>&#8220;It&#8217;s definitely gang, and some major gangs are represented there, with some very violent rivalries.  No doubt about it,&#8221; said Richard Valdemar, who started the Los Angeles County Sheriff&#8217;s Department gang unit 33 years ago. He&#8217;s one of the top gang experts in the country.</p>
<p>&#8220;There is some real rivalry going on,” he said.</p>
<p>We asked him to analyze 62 images, all taken from Alaska cargo bins.  Like the other four experts, he said the graffiti shows gang members are working there, with full access to the airplanes.</p>
<p> <br />
<img class="alignright" style="border: 0px initial initial;" src="http://www.king5.com/topstories/stories/M_IMAGE.10941787f49.93.88.fa.d0.34327fcd.jpg" border="0" alt="" width="225" height="163" />  <br />
&#8220;By definition, they are gang members, which means they are outlaws. They&#8217;re outside of our system of law. They answer to their own system of law, which is a criminal culture,&#8221; he said.</p>
<p>Experts say the word &#8220;norte&#8221; appears many times in the images, as does “XIV”, the Roman numeral 14. Together, they refer to the violent Norte 14 gang.  Members identify themselves with locations like Oakland , and area code 510.</p>
<p>Their number one rival – the Surenos &#8212; is represented as well, primarily from further south, like Orange County and Santa Ana and area code 714.</p>
<p>Experts say this gang answers to the Mexican mafia, or EME, which you can faintly see spelled out in one of the images.</p>
<p>Throughout the bins, the monikers are crossed out, which means a serious challenge by a rival gang.</p>
<p>&#8220;It&#8217;s not just &#8216;I&#8217;m claiming this territory&#8217; it&#8217;s also an act of defiance and it demands retaliation,” said Valdemar.<br />
<img class="alignleft" style="border: 0px initial initial;" src="http://www.king5.com/topstories/stories/M_IMAGE.10941787f49.93.88.fa.d0.3433a16d.jpg" border="0" alt="" width="225" height="168" />  <br />
There other references to “Tookie,” likely the Crips gang founder Tookie Williams executed in California last month.</p>
<p>What&#8217;s more, there are many references to smoking drugs on the job.</p>
<p>One picture shows a marijuana joint with the Seattle area code 206 reference nearby. Underneath the joint, a line reads: “reason for delays.”</p>
<p>And a dollar sign written on top of a person smoking pot means something else in the gang world.</p>
<p>&#8220;So, they&#8217;re saying they sling dope … sell dope,&#8221; said Valdemar.</p>
<p>Pilots tell their union they saw a dramatic increase in this kind of graffiti last May, after Alaska fired its ramp workers and hired a cheaper outside contractor, Menzies Aviation, to load the bags on planes at Sea-Tac.</p>
<p>The union says whoever&#8217;s to blame, they want something done.</p>
<p>&#8220;Where is their limit?  What else are they going to do or what are they capable of?  It&#8217;s against the law and they should be prosecuted, and not out there on our ramp,&#8221; said Capt. Paul Emmert of the Seattle Pilot’s union.</p>
<p>Asked by Alaska Airlines months ago to look into complaints about graffiti, the Port of Seattle Police concluded that gang graffiti does not always equal gang activity.</p>
<p>&#8220;It just doesn&#8217;t amount to anything that raises to that level of concern that we&#8217;d want to take any other overt action in dealing with it,&#8221; said Port of Seattle Police Chief Tim Kimsey.</p>
<p>Alaska&#8217;s director of security says the company&#8217;s satisfied with the Port police investigation.</p>
<p>“They have told us it is not an indication of gang activity,&#8221; Holly Geiger Zimmerman said.</p>
<p>&#8220;I think we have to go with the jurisdiction. The people with jurisdiction is the airport police unit. We know they are good at their job,&#8221; she said.</p>
<p>Port police say they even went outside their department and showed similar images to their own gang experts.</p>
<p>&#8220;A few of them in there may raise some concern, based on that input that we got back, but again, not enough that it tells us that we have an issue or problem here at Sea-Tac Airport,&#8221; according to Kimsey.</p>
<p>But the KING 5 Investigators learned Wednesday night that the port was warned. A local gang task force looked at some photos last summer and told the officer assigned to the case this looked like a serious problem. </p>
<p>And that’s exactly what all the experts told us in our investigation.</p>
<p>And the people writing the graffiti don’t belong anywhere near an aircraft, said Valdemar.</p>
<p>&#8220;That is a criminal element, active in the bellies of the planes, with rivals also in the same proximity.”</p>
<p>Why did the port ignore the advice of experts?</p>
<p>When we confronted them with that question Thursday, they said they didn&#8217;t think the group had enough experience to draw any conclusions.</p>
<p>That doesn&#8217;t explain why they sought their advice in the first place.</p>
<p>The experts tell us the graffiti suggests strong connections to California and Seattle.</p>
<p>Alaska Airlines told us repeatedly it&#8217;s depending on the Port of Seattle to investigate.</p>
<p>To this date the Port has not interviewed one employee or done any surveillance, something our experts all say would be a very good idea.</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2006/02/investigators-gang-graffiti-exposed-in-alaska-air-jet-cargo-holds/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Letter to Alaska Airlines</title>
		<link>http://alaskaairlinessucks.com/2004/03/letter-to-alaska-airlines/</link>
		<comments>http://alaskaairlinessucks.com/2004/03/letter-to-alaska-airlines/#comments</comments>
		<pubDate>Mon, 01 Mar 2004 20:00:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Well-Deserved Cranky Letters]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=17</guid>
		<description><![CDATA[Mr. Bill Ayers
President and CEO
Alaska Airlines
19300 International Boulevard
Seattle, WA 98188 
Dear Mr. Ayers:
On Saturday, February 21, 2004, I flew on your airline from Burbank to Seattle, Flight #561. I am a professional musician of over 40 years standing, and a professional photographer of nearly 30 years. Thus, I often fly with my equipment. Sometimes I [...]]]></description>
			<content:encoded><![CDATA[<p>Mr. Bill Ayers<br />
President and CEO<br />
Alaska Airlines<br />
19300 International Boulevard<br />
Seattle, WA 98188 </p>
<p>Dear Mr. Ayers:</p>
<p>On Saturday, February 21, 2004, I flew on your airline from Burbank to Seattle, Flight #561. I am a professional musician of over 40 years standing, and a professional photographer of nearly 30 years. Thus, I often fly with my equipment. Sometimes I carry a guitar, sometimes I have photo gear, sometimes I have both. </p>
<p>On the day of my flight, I arrived at Bob Hope Airport/Burbank and checked in at 11:30am for a 2:00pm flight. I was the only person in line. I had in my possession one large soft case travel bag, a collapsible nylon mesh bag, a box of fragile glassware, a camera bag which doubled as my personal bag and a standard sized acoustic guitar in a hard shell case. It was my intention to check the large travel bag, and insert the box of glassware into the nylon mesh bag for carry-on. It was also my intention, as it has been for years, to carry my camera/personal bag and instrument on the plane with me.  </p>
<p>Your counter attendant, however, saw it differently. She insisted that regardless of how I combined or configured my items, I would still be one item over the limit for carry-on. She insisted that I would have to check either the box of fragile glassware or the guitar.  </p>
<p>At the time of my check-in I had in my possession a photocopy of a letter from Mr. Thomas R. Blank, Assistant Administrator for Security Regulation and Policy for the U.S. Department of Transportation’s Transportation Security Administration. I have attached a copy of Mr. Blank’s letter herein. In his letter, dated January 17, 2003, to Mr. Thomas Lee of the American Federation of Musicians, Mr. Blank states: </p>
<p><em>“On December 20, 2002, TSA instructed aircraft operators that effective immediately, they are to allow musical instruments as carry-on baggage in addition to the limit of one bag and one personal item per person as carry-on baggage on an aircraft.”</em></p>
<p>I tried to present this letter and information to your attendant. She had no interest in reading it, and inferred that I was being argumentative. This surprised me, since at no time did I do or say anything that should have brought about such a response. In fact, I was doing my best to comply with her requirements.</p>
<p>In addition to the letter from Mr. Blank at TSA, I was in possession of an advisory notice from Mr. Eugene Mopsik, Executive Director of the American Society of Media Photographers, Inc. The advisory, dated November 20, 2003, states the following:</p>
<p><em>“Thanks to the effort of ASMP and the cooperation and understanding of the Transportation Security Administration (TSA), working photographers and other members of the traveling public may now take on board an additional piece of carry-on baggage containing photographic equipment. This means you are allowed to carry on two bags – when at least one is photographic equipment – along with a personal item. …The TSA has said to go ahead at this time and take advantage of the new policy.”</em></p>
<p>I had no opportunity to present this information, either. </p>
<p>If I may,  I would like to call your attention to your own <a href="http://www.alaskaair.com/www2/company/tariff/domestic/tariff_domestic_section5.asp">website</a>, regarding Alaska’s baggage policies. Under Section V, Baggage, Rule 190AS, Paragraph E, Item 6 Fragile Items, it states:  </p>
<ul>
<li>c.  The classes of items listed below are deemed to be too fragile or perishable or  otherwise unsuitable as checked baggage and are subject to the conditions of acceptance set fort in paragraphs a) and b) above:</li>
<li>v.  Glass (see also chinaware/ceramics/pottery): Glassware, crystal, lamps, mirrors, bottles, and other glass containers and any liquids contained therein, telescopes, binoculars, barometers and eyeglasses and contact lenses that are not in their hard cases.</li>
<li>ix. Musical Instruments and Equipment: Guitars, violins and other stringed instruments, organs, horns, percussion, wind and brass instruments, amplifiers or speakers in conjunction with electronic instruments.</li>
<li>xi. Photographic/Cinematographic and Precision Equipment: Cameras, disposable cameras, photoflash equipment, photometers, spectroscopes, phototubes or other devices using sensitive tubes or plates, projectors, lenses, film, flash bulbs…</li>
</ul>
<p>One thing seems quite clear: Under any of several scenarios, I should have been allowed to carry on the camera/personal bag, the glassware box and the guitar, without question. The TSA has adopted these policies and instructed the airlines accordingly. The policy regarding musical instruments is well over a year old; the policy regarding photographic equipment dates back three full months. And your own website acknowledges that these items are fragile and unsuitable to be checked as baggage. </p>
<p>Instead, I was forced to gate-check my guitar. When I picked it up in Seattle, the guitar felt nearly frozen. It should go without saying that subjecting an expensive professional instrument to the temperature extremes found in an unheated space at 31,000 feet is detrimental to the instrument. In some cases it can result in permanent damage. I would prefer to not run that risk on an irreplaceable instrument. I would prefer to not have my livelihood risked because my means of making it has been compromised by an airline attendant’s unwillingness to comply with, or even be informed of, standing TSA and airline policy. And I should think Alaska Airlines would not be enthused about the prospect of replacing a valuable instrument, let alone the inconvenience to one of its long-standing patrons.</p>
<p>The following information is also relevant: </p>
<ul>
<li>My guitar easily fits into the overhead compartments of the 737’s and MD-80’s Alaska uses on the Burbank/Seattle route.</li>
<li>The glassware box and camera bag in question were both substantially smaller than most carry-on luggage. The camera/personal bag measures 16Lx10Wx7.5H inches, the glassware box 9&#215;13x7.5 inches. Combined they are still smaller than many carry-ons. Either one fits under the seat in front of me, leaving the other for the overhead bin.</li>
<li>On all three other legs of my Alaska round trip, which took me to and from Manzanillo, Mexico, taking my guitar on the plane was never an issue. I had the identical carry-ons in Manzanillo as I did in Burbank.</li>
</ul>
<p>Given the foregoing, can you please resolve these issues for me? </p>
<p>Is there any reason at all that your employees in Burbank would not be fully aware of  TSA or Alaska Airlines policies?</p>
<p>Why would your Burbank counter attendant be unwilling to at least review the TSA and ASMP letters?</p>
<p>Why would your Burbank counter attendant be unaware of Alaska’s policy regarding fragile items?</p>
<p>What kind of response should I expect from your attendants the next time I fly Alaska Airlines with my professional equipment and/or instruments?</p>
<p>I very much look forward to your early response. Thank you very much. </p>
<p>Sincerely yours, </p>
<p>Jef Jaisun </p>
<p>CC:<br />
Mr. Thomas R. Blank, TSA<br />
Mr. Eugene Mopsik, ASMP<br />
Mr. Thomas F. Lee, President, AFM New York<br />
Mr. Hal Ponder, Legislative Director, AFM Washington, D.C.<br />
Mr. John McCutcheon, President, AFM Local 1000</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2004/03/letter-to-alaska-airlines/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Letter to the FAA</title>
		<link>http://alaskaairlinessucks.com/2003/01/letter-to-the-faa/</link>
		<comments>http://alaskaairlinessucks.com/2003/01/letter-to-the-faa/#comments</comments>
		<pubDate>Fri, 24 Jan 2003 00:23:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Well-Deserved Cranky Letters]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=49</guid>
		<description><![CDATA[Dear FAA,
I recently read the NTSB&#8217;s report and findings on Alaska Air flight 261. One of my neighbors was killed on the flight.  I was in Puerto Vallarta on the day of the crash.  I had flown into Puerto Vallarta on an Alaska flight.
One of the recommendations in the NTSB report was that [...]]]></description>
			<content:encoded><![CDATA[<p>Dear FAA,</p>
<p>I recently read the NTSB&#8217;s report and findings on Alaska Air flight 261. One of my neighbors was killed on the flight.  I was in Puerto Vallarta on the day of the crash.  I had flown into Puerto Vallarta on an Alaska flight.</p>
<p>One of the recommendations in the NTSB report was that the FAA should follow up on it&#8217;s oversight of maintenance at Alaska Air.  The report stated that the FAA made a review of Alaska Air&#8217;s maintenance program and found several deficiencies.  A follow up review revealed that several problems still existed at Alaska.  The NTSB report suggested that further oversight of Alaska Air by the FAA is still needed.</p>
<p>I would like to know what steps the FAA has taken to ensure that maintenance at Alaska Air is being done correctly.  If there is something wrong at Alaska Air, why is the airline allowed to operate?</p>
<p>I am expressly concerned, not only since my neighbor needlessly died in what the NTSB termed a maintenance accident, but because I intend to fly with my family on Alaska Air next month.  We had heard about the FAA oversight of the Alaska Maintenance program and believed that the problems at Alaska had been corrected. It has been three years since flight 261 crashed into the Pacific killing all 88 aboard. That would be ample time in my mind for the FAA to have acted in a diligent manner to correct deficiencies at Alaska. Now with the recent NTSB report we see that further follow-up oversight at Alaska is needed and recommended.</p>
<p>This is very unsettling since we are booked on an Alaska flight less than 30 days from now.  Can you assure me that the FAA has done everything that needs to be done at Alaska Air?  Would you characterize Alaska Air&#8217;s fleet as well maintained and now meets the scrutiny of the FAA?</p>
<p>I need to know what the FAA knows about Alaska Air, and I need to know soon. Please respond to my questions about Alaska Air as soon as possible.</p>
<p>Sincerely Yours,</p>
<p>Grant A. Silvey, PE</p>
<hr />
<p>Dear Mr. Silvey:</p>
<p>We have been asked to respond to your recent e-mail regarding the National Transportation Safety Board&#8217;s (NTSB&#8217;s) recent findings on Alaska Airlines flight 261.  Please accept our sincere condolences for the loss of your neighbor in that tragic accident.</p>
<p>As you indicated, the NTSB was critical of the Federal Aviation Administration&#8217;s (FAA&#8217;s) oversight of the company at the time of the accident.  Both before and after the accident we have taken actions to strengthen the FAA&#8217;s surveillance of the carrier.  Staffing at the Alaska Airlines Certificate Management Office (ASAA CMO), the FAA organization responsible for oversight of the airline has increased from 15 to 37 since the accident. In addition, 10 remotely sited inspectors assist in conducting surveillance of the carrier in Anchorage, Oakland and Los Angeles.</p>
<p>We also conducted a special national safety inspection (NSI) of the airline following the accident.  In response to the FAA&#8217;s proposal to suspend the carrier&#8217;s heavy maintenance authorization following the NSI, Alaska Airlines proposed an action plan that implemented significant changes in maintenance, operations and management.  A FAA safety panel that included inspectors from the local, regional and national levels monitored performance of this action plan to completion.  Top level management at the airline continues to meet with the CMO manager and supervisory inspectors on a quarterly basis to provide updates.</p>
<p>FAA regulations mandate that airlines serving the general public maintain the highest level of safety.  Alaska Airlines has made significant changes since the accident in order to maintain that standard.  We believe the current structure of the Alaska CMO is sufficient to allow the FAA to provide the oversight necessary to make sure the airline maintains the highest level of safety and we are confident that standard is currently being met.</p>
<p>On a personal note, since the accident I have bought several tickets for my wife and myself to go on vacation on Alaska Airlines.  Those trips included like yours, a trip to Mexico and as recent as November to Phoenix.  I can assure you that I feel comfortable with the service and reliability of Alaska Airlines aircraft.</p>
<p>Sincerely,</p>
<p>Timothy L. Miller<br />
Alaska Airlines Principal Maintenance Inspector</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2003/01/letter-to-the-faa/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Flight 222</title>
		<link>http://alaskaairlinessucks.com/2002/08/flight-222/</link>
		<comments>http://alaskaairlinessucks.com/2002/08/flight-222/#comments</comments>
		<pubDate>Wed, 21 Aug 2002 21:37:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Well-Deserved Cranky Letters]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=45</guid>
		<description><![CDATA[Holy shit! What a horrifying experience! So what did the air crew do after you safely landed &#8211; I understand they didn&#8217;t give any explanation- but what did they tell the passengers at the time, how did they respond to your shall we say inconvenience?
Each airline has a process by which every incident is reviewed, [...]]]></description>
			<content:encoded><![CDATA[<p>Holy shit! What a horrifying experience! So what did the air crew do after you safely landed &#8211; I understand they didn&#8217;t give any explanation- but what did they tell the passengers at the time, how did they respond to your shall we say inconvenience?</p>
<p>Each airline has a process by which every incident is reviewed, the crew interviewed &#8211; faa and I forget who else are involved. Usually the crew is videotaped. These are used as learning experiences and each incident has value in that something can be learned to prevent further occurances, or techniques to respond to incidents are derived. The results are not shared with the public, but some response is definitely in order.<br />
Keep plugging away &#8211; try the interstate commerce commission or whatever it&#8217;s called. They may be more forthcoming than the faa, who are notoriously tightlipped.</p>
<p>We&#8217;re trained to assess passengers as they board, pick out who we would ask for assistance in the event of an emergency. We look for people who seem calm under pressure, capable, strong enough to open the door if necessary. There are specific words we use in evacuation. Did the flight attendant say &#8220;you &#8211; come with me&#8221; ? Do this, do that. &#8220;Get the people out.&#8221;</p>
<p>Sometimes I dream the phrases.</p>
<p>Anyway, good luck in your search for answers. There must be a local weekly alternative newspaper in Seattle, enlist their help. (was the aircraft a Boeing??)</p>
<p>ciao<br />
Judy</p>
<hr />
<p>Hey Judy,</p>
<blockquote><p>Holy shit! What a horrifying experience! So what did the air crew do after you safely landed &#8211; I understand they didn&#8217;t give any explanation- but what did they tell the passengers at the time, how did they respond to your shall we say inconvenience?</p></blockquote>
<p>Mostly, they hustled us onto another plane. There were two other planes from Seattle that had to connect with 222 in LA, combining for the one flight to Mexico. They gave me free cognacs on the flight to LA. I needed them.</p>
<blockquote><p>Each airline has a process by which every incident is reviewed, the crew interviewed &#8211; faa and I forget who else are involved. Usually the crew is videotaped. These are used as learning experiences and each incident has value in that something can be learned to prevent further occurances, or techniques to respond to incidents are derived. The results are not shared with the public, but some response is definitely in order.</p></blockquote>
<p>You tell them that, wouldja? They obviously don&#8217;t care what I have to say.</p>
<blockquote><p>We&#8217;re trained to assess passengers as they board, pick out who we would ask for assistance in the event of an emergency. We look for people who seem calm under pressure, capable, strong enough to open the door if necessary. There are specific words we use in evacuation. Did the flight attendant say &#8220;you &#8211; come with me&#8221; ? Do this, do that. &#8220;Get the people out.&#8221;</p></blockquote>
<p>I was minding my own business, sitting at a window seat forward of the wing, trying to come to terms with what I expected was going to be an untimely and ignominious demise. I really didn&#8217;t want to talk to anybody at that moment. Then a stew sticks her head into the row and says, &#8220;Sir, would you please come with me?&#8221;  </p>
<p>&#8220;Why?&#8221;</p>
<p>&#8220;We may need your help at the back of the plane, in case the rear emergency exit doesn&#8217;t open.&#8221;</p>
<p>Oh, that&#8217;s fucking GREAT! I don&#8217;t want to be at the back of the plane to begin with, which is why I always sit forward of the wing. Now she&#8217;s filling my head with visions of wings and engines digging into the tarmac, sending huge chunks of metal and flaming jet fuel right into my face. Like I needed that. </p>
<p>Yeah, I went back there, but I wasn&#8217;t the least bit happy about it. Further, the stew herself was practically in tears, trying to keep it together. Afterwards, she told me it&#8217;s the first time anything like that had ever happened to her, and all she could think of (beyond the immediate situation) was her two small kids at home.</p>
<p>We landed without incident, and I didn&#8217;t have to pop open the rear door. That didn&#8217;t make the ride any less scary.</p>
<p>The plane? Funny you should ask. It was an MD-80, piece of shit inherited from Boeing&#8217;s takeover of Lockheed and subject to the exceptional Alaska &#8220;maintenance&#8221; program. In the next few weeks there was a spate of MD-80 incidents, including Flight 261 and a plane that came into SFO with an engine on fire. The FAA should have grounded all of them IMMEDIATELY, but that would have meant putting people&#8217;s safety above airline profits. And boy howdy, we sure can&#8217;t do that. So when all this shit started to be uncovered about Alaska and their maintenance falsifications, I was way ahead of the curve. Alaska should have had its license to fly revoked on the spot.</p>
<p>I haven&#8217;t flown Alaska since, except to get home from Mexico two years ago. And those assholes made it just about as incovenient as they could. I used some Continental miles for the ticket, after Alaska and Continental made their co-share deal. I flew into Manzanillo, 15 minutes from my hotel. When I wanted to come home several weeks later, Alaska told me there were no seats available on the Manzanillo planes, and that I had to come back via Puerto Vallarta. PV is a four hour Mexican bus ride and a major hassle away. I went to the ZLO airport to talk with a super, and she told me the only person who could help me was at a counter in PV. So, either way I was being sent back on the long bus. Meanwhile, I&#8217;m watching all my other buddies getting stand-by seats on the same planes I&#8217;m being told are sold out!</p>
<p>The real story? Because I used my Continental miles instead of my Alaska miles, they dropped me to the bottom of the food chain. They wouldn&#8217;t admit this to my face, of course, but I had a mole in the agency who copped to it. The next morning I dialed Alaska&#8217;s stateside 800 number and chewed out one of their supervisors. I told him, &#8220;After what I&#8217;ve been through with you guys, and after you just killed some people I know!, you&#8217;re lucky I&#8217;m flying with you at all. The least you can do is get me on a freakin&#8217; local plane!&#8221; Long silent pause on the other end of the line, followed by, &#8220;Would you like a window or aisle seat, sir?&#8221; Sheesh. </p>
<p>With all this in the hopper, I find it astounding that not one single media person in this market has seen fit to follow up on my letters. And believe me, I started e-mailing them from Mexico two-and-a-half years ago.</p>
<p>Jef</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2002/08/flight-222/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Alaska 261/222 &#8211; Two years later, still no answers</title>
		<link>http://alaskaairlinessucks.com/2002/01/alaska-261222-two-years-later-still-no-answers/</link>
		<comments>http://alaskaairlinessucks.com/2002/01/alaska-261222-two-years-later-still-no-answers/#comments</comments>
		<pubDate>Sun, 27 Jan 2002 03:21:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Well-Deserved Cranky Letters]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=42</guid>
		<description><![CDATA[Dear Mr. Fancher and the editorial staff of the Times:
Two years ago this week I was involved in an emergency situation involving an Alaska Airlines MD-80 at Sea-Tac Airport. I wrote you and other members of the media about it extensively. Yet, a full two years later, and on the anniversary of the Flight 261 [...]]]></description>
			<content:encoded><![CDATA[<p>Dear Mr. Fancher and the editorial staff of the Times:</p>
<p>Two years ago this week I was involved in an emergency situation involving an Alaska Airlines MD-80 at Sea-Tac Airport. I wrote you and other members of the media about it extensively. Yet, a full two years later, and on the anniversary of the Flight 261 tragedy, not a one of you has seen fit to follow up on my letter and the terrifying moments experienced by the passengers on my flight.</p>
<p>In fact, despite all your coverage of Alaska Airlines and its problems, the incident on Flight 222 has gone wholly unreported. Why is that?</p>
<p>To recap:</p>
<p>On January 20th, eleven days prior to the Flight 261 disaster, a plane load of Alaska passengers, which included me, thought we were due to be tarmac cinders. Our flight, Alaska 222, bound for Manzanillo via Los Angeles, blew something on take-off from Sea-Tac Airport. We heard several loud bangs from the back of the aircraft. A few seconds later there were two more, and the plane lurched to the right. One woman passenger screamed in obvious apprehension, &#8220;Oh no!&#8221;</p>
<p>A minute passed before the pilot finally announced there was a problem, and we&#8217;d have to turn around and make an immediate emergency landing. An extremely distressed flight attendant gave us instructions for assuming the crash position. One passenger took out a marking pen and wrote a farewell message to his girlfriend on a drop-down tray. We all thought our lives were over, especially me, when I was asked to come to the rear of the plane to assist the attendants in case the rear emergency door didn&#8217;t open during the landing procedure.</p>
<p>At no time during the emergency, nor any time since, has Alaska Airlines informed us what happened on that flight. No apologies, no explanations, no nothing! I received no communication from the airline whatsoever, despite five months of trying to get answers. The FAA was &#8220;unable&#8221; to provide information because Alaska hadn&#8217;t filed any!</p>
<p>What continues to tear at me is the possibility that my plane&#8217;s malfunction could have been identical to Flight 261&#8217;s. When the FAA later reported hearing &#8220;two loud bangs from the back of the aircraft&#8221; on 261&#8217;s cockpit voice recorder, I immediately thought about what happened on Flight 222. Perhaps the tragedy of 261 could have been averted if someone at Alaska had been paying attention. Was it the same plane? Was it the same problem? Nobody knows because Alaska has never told us anything! I was scheduled to fly back from Puerto Vallarta on Alaska. I could have been on Flight 261. As it turns out, my parents were returning from Puerto Vallarta on an Alaska flight at the same time 261 went down. It&#8217;s only by chance they were not obliterated on Flight 261.</p>
<p>My opinion, which I have stated repeatedly since February 1, 2000, is that Alaska Airlines deserves to be ripped open and examined from the bottom up. Even more so than has already occurred. In the three years prior to the 261 and 222 incidents, I watched the airline steadily deteriorate as bean counters made the calls and cut corners. We have all now seen the results. I applauded the FAA&#8217;s decision to hold Alaska accountable, and shut them down if the situation warrants, but I have not been impressed with the results so far.</p>
<p>As Alaska CEO John Kelly and his spin doctors continue their damage control press conferences, which we will no doubt be treated to again this coming Thursday, I still wonder why I should ever get on another Alaska plane. I haven&#8217;t done so since my return from Mexico two years ago, and I see no reason to change my mind any time soon.</p>
<p>I want some answers! I want to know what happened on my flight. I want to know why it&#8217;s being hushed up. I want to know if the failures on Flights 222 and 261 were related. And I&#8217;d really like to know why nobody in the massive Seattle media market thinks the Flight 222 incident is important enough to expose and thoroughly investigate.</p>
<p>Yes, just as you did, I knew people on Flight 261. Yes, I continue to mourn their loss. It should never have happened. And maybe  &#8212; just maybe &#8212; it wouldn&#8217;t have if someone had been paying attention on January 20, 2000, eleven days earlier.</p>
<p>Sincerely yours,</p>
<p>Jef Jaisun<br />
Seattle</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2002/01/alaska-261222-two-years-later-still-no-answers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Alaska 261: first there was Flight 222</title>
		<link>http://alaskaairlinessucks.com/2001/01/alaska-261-first-there-was-flight-222/</link>
		<comments>http://alaskaairlinessucks.com/2001/01/alaska-261-first-there-was-flight-222/#comments</comments>
		<pubDate>Thu, 01 Feb 2001 02:00:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Well-Deserved Cranky Letters]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=40</guid>
		<description><![CDATA[Hey Jef,
Thanks for copying me on the flight incident. Did you hear back this time? And do I understand that the FAA DID acknowledge that Alaska reported SOME problem on board?
Mike Webb
KIRO Radio

Mike,
Nope, I ain&#8217;t heard shit. My pal Casey Corr, a Times editorialist (and striker who has yet to be called back) has passed [...]]]></description>
			<content:encoded><![CDATA[<p>Hey Jef,</p>
<p>Thanks for copying me on the flight incident. Did you hear back this time? And do I understand that the FAA DID acknowledge that Alaska reported SOME problem on board?</p>
<p>Mike Webb<br />
KIRO Radio</p>
<hr />
<p>Mike,</p>
<p>Nope, I ain&#8217;t heard shit. My pal Casey Corr, a Times editorialist (and striker who has yet to be called back) has passed it on to Chuck Taylor, a Times aerospace reporter and former editor in chief of the Union Record. Maybe Chuck will get interested.</p>
<p>Re the FAA: When I contacted them initially (I think it was in June), their response was something to the effect of, &#8220;Alaska filed the bare minimum required, acknowledging there was an incident. No details. That&#8217;s all we have, so we really can&#8217;t tell you anything more than you already know.&#8221; When I pressed for more info, I was essentially blown off, being advised to file a FOIA request &#8220;to get more details&#8230;that way they have to respond.&#8221; The FAA guy also allowed as to how Alaska had a full year to file any additional information. Now that it&#8217;s been a full year, I should probably go back and ask what&#8217;s in the FAA file. But at this point I would just as soon it were done by a reporter, talk show host or NTSB investigator. Obviously, passengers like me don&#8217;t count much at the local FAA or Alaska.</p>
<p>Jef</p>
<hr />
<em><br />
December 26, 2000</p>
<p>Dear Mr. Wallace</p>
<p>Thank you for you excellent coverage of the NTSB&#8217;s Flight 261 hearings. I hope you will find the following of interest, as well.</p>
<p>Coverage of Alaska Airlines&#8217; problems has omitted at least one other recent critical incident that has so far gone unreported.</p>
<p>On January 20th, 2000, 11 days before the Flight 261 disaster, a plane load of Alaska passengers departing Sea-Tac airport thought we were due to be tarmac cinders. Our flight, Alaska 222, was an MD-80 bound for Manzanillo via Los Angeles. As we began to climb during take-off, something literally blew up. We heard several loud bangs from the back of the aircraft, then a few seconds later there were two more, and the plane lurched to the right. One woman passenger screamed in obvious fright, &#8220;Oh no!&#8221;</p>
<p>A minute passed before the pilot finally announced there was a problem, and we&#8217;d have to turn around and make an immediate emergency landing. An extremely distressed flight attendant gave us instructions for assuming the crash position. One passenger took out a marking pen and wrote a farewell message to his girlfriend on a drop-down tray. We all thought we were toast, especially me, when I was asked to come to the rear of the plane to assist the attendants in case the rear emergency door didn&#8217;t deploy during the landing procedure.</p>
<p>At no time during the emergency, or any time since, has Alaska Airlines informed us what happened on that flight. No apologies, no explanations, no nothing! I have received no communication from the airline whatsoever, despite 11 months of trying to get answers. The FAA was unable to provide information because (they said) Alaska hadn&#8217;t filed any!</p>
<p>What also tears at me is the possibility, however remote, that what happened to my flight could have been related &#8211;or, in fact, identical&#8211; to Flight 261. When the FAA later reported hearing &#8220;two loud bangs from the back of the aircraft&#8221; on 261&#8217;s cockpit voice recorder, a cold chill went through me. I immediately thought about what happened on Flight 222. Perhaps the tragedy of 261 could have been averted had someone at Alaska been paying attention. Was it the same plane? Was it the same problem? Nobody knows because Alaska hasn&#8217;t told us anything! I was scheduled to fly back from Puerto Vallarta. I could have been on Flight 261. As it turns out, my parents *were* flying back from Puerto Vallarta on an Alaska flight at the same time 261 went down. That&#8217;s a little too close for my comfort. Worse, I knew people on Flight 261.</p>
<p>Here is my list of unanswered questions for John Kelly and the rest of his pals at Alaska Airlines.</p>
<p>1. What happened to Alaska Flight 222 from SeaTac on the morning of<br />
January 20, 2000?<br />
2. I want a copy of the incident report. Where do I get it?<br />
3. What happened to the &#8220;engine&#8221; we supposedly blew on take-off?<br />
4. Where is that &#8220;engine&#8221; now?<br />
5. What Alaska PLANE number was Flight 222 on Jan 20th?<br />
6. Was it the same plane number as Flight 261?<br />
7. If not, did the 261 plane receive 222&#8217;s &#8220;engine?&#8221;<br />
8. I want a copy of the passenger list, complete with addresses and phone numbers of everyone on Flight 222/ Jan 20, 2000. How do I get it?</p>
<p>As the evidence from the NTSB hearings continue to point at lax maintenance by Alaska, I sit here wondering why I should ever get on another Alaska plane. Maybe the problem on 261 was indeed related to the jack screw assembly, but that doesn&#8217;t begin to answer what happened on Flight 222. Perhaps you can help me find those answers.</p>
<p>Thank you very much</p>
<p>Sincerely yours,</p>
<p>Jef Jaisun</em></p>
<hr />
<p>Dear James,</p>
<p>I haven&#8217;t received a response from you since I e-mailed you the letter below over a month ago. So I guess the possibility that the Flight 261 disaster may have been preventable as late as 11 days prior is not an issue with you. However, I note with extreme distress in your P-I article today that not only was there a suspect arrangement between Alaska Airlines and the local FAA office, but that FAA officials conspired to exclude the Flight 261 investigation from the Freedom of Information Act. It was these same local FAA officials whom I contacted last spring regarding my experience on Flight 222. And you know what they told me? &#8220;Alaska didn&#8217;t tell us much about the emergency on your flight. You should file a Freedom of Information Act request.&#8221;</p>
<p>Now I know what they were really telling me: &#8220;Get lost!&#8221;</p>
<p>I may never find out what happened to Flight 222. You won&#8217;t, either. It&#8217;s just too bad nobody around here apparently has the guts, the curiosity or the dedication to the truth to find out if the Flight 222 emergency could have been related to Flight 261&#8217;s subsequent fatal plunge.</p>
<p>Sincerely yours,</p>
<p>Jef Jaisun</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2001/01/alaska-261-first-there-was-flight-222/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PV Memorial for Flight #261</title>
		<link>http://alaskaairlinessucks.com/2001/01/pv-memorial-for-flight-261/</link>
		<comments>http://alaskaairlinessucks.com/2001/01/pv-memorial-for-flight-261/#comments</comments>
		<pubDate>Mon, 29 Jan 2001 03:31:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Well-Deserved Cranky Letters]]></category>

		<guid isPermaLink="false">http://alaskaairlinessucks.com/?p=38</guid>
		<description><![CDATA[Hola amigos,
Wednesday will be the anniversary of the crash of Alaska Flight 261. There are numerous memorials planned for the day. On February 15 there will be a dedication ceremony in Puerto Vallarta, in case any of you are there and feel like attending. Here&#8217;s the info from today&#8217;s Seattle Times, which has several very [...]]]></description>
			<content:encoded><![CDATA[<p>Hola amigos,</p>
<p>Wednesday will be the anniversary of the crash of Alaska Flight 261. There are numerous memorials planned for the day. On February 15 there will be a dedication ceremony in Puerto Vallarta, in case any of you are there and feel like attending. Here&#8217;s the info from today&#8217;s Seattle Times, which has several very fine stories on the people who perished on the flight, in case anyone wants to read them.<br />
http://seattletimes.nwsource.com/cgi-bin/WebObjects/SeattleTimes.woa/wa/</p>
<p>&#8220;A memorial in Puerto Vallarta, Mexico, to Joe and Linda Knight, co-pastors of The Rock Church of Monroe, WA, who were in Mexico to work with children living in a city dump, is in the final stages of construction. The memorial &#8212; a community shower, medical clinic and dining area for the children of about 200 families who live in filth and poverty in shanties and lean-tos at the dump &#8212; will be dedicated Feb. 15.</p>
<p>&#8220;Seattle Times readers donated $24,000 to the project. The Puerto Vallarta City Council donated the land for the center. &#8230; Americans who live on yachts in the resort&#8217;s harbor have assisted in the project. In addition, several churches in the Seattle area have been working with the congregation at Perdon y Amistad, a non-denominational church in Puerto Vallarta, to provide regular meals to the children. Tax-deductible donations to the combined ministries  may be sent to Feed the Children in Puerto Vallarta, 718 Griffin Ave, PMB 207, Enumclaw, WA.&#8221;</p>
<p>El Jefe</p>
]]></content:encoded>
			<wfw:commentRss>http://alaskaairlinessucks.com/2001/01/pv-memorial-for-flight-261/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
