Plane's air-conditioning unit malfunctions, causing smoke

Sunday, February 6, 2000

A malfunctioning air conditioner in a US Airways plane parked at a Port Columbus gate created a stir shortly after 8 a.m. yesterday.

No one was injured and an initial call to the Columbus Fire Division was canceled, airport officials said, after it was determined that the overheated air- conditioning unit created only some "light smoke,'' but no other damage to the plane. Some crew members, but no passengers, were on board, said David Whitaker, spokesman for the airport.

The cause of the malfunction, reported about 8:15 a.m., was not immediately determined.

Airport traffic was not interrupted. Link

http://www.dispatch.com/news/newsfea00/feb00/170198.html

-- Carl Jenkins (Somewherepress@aol.com), February 17, 2000

Answers

What type of aircraft?????

-- Duke1983 (Duke1983@aol.com), February 17, 2000.

Another malfunctioning air conditioning unit:

http://www.msnbc.com/l ocal/KHQ/29534.asp

Investigators find cause of emergency landing in Yakima YAKIMA, Washington, February 16 - An air conditioning problem is to blame for an emergency landing by a Horizon Air flight headed to Spokane from Portland.

The plane landed in Yakima Monday night when smoke filled the cabin.

The 60 passengers were all re-routed to Spokane. No one was hurt.

-- Homer Beanfang (Bats@inbellfry.com), February 17, 2000.

What type of air-craft!!!! One would think the point is newsworthy and hardly requires journalistic legderdemain to uncover, nor occupies much space tprint. One might also think that after the FAA has opened investigations into the MD-80, that US Airways would want to REASSURE their flying public that this mishap was unrelated IN EVERY WAY to the fatal crash of Flight 261 .......

Maybe.

-- Squirrel Hunter (nuts@upina.cellrelaytower), February 18, 2000.

Another one!! Man, now there is no doubt about it. The only thing that could cause all these air conditioners to go bezerk in the middle of winter is our good buddy, Mr. Y2K. Of course it isn't Mr. Y2K's fault, it is the corporations.

-- Hawk (flyin@high.again), February 18, 2000.