403 Forbidden


nginx
403 Forbidden

403 Forbidden


nginx
Follow us:
403 Forbidden

403 Forbidden


nginx

Northwest Traveler

Travel news, consumer advice and trip reports for the Northwest and beyond.

October 15, 2014 at 9:29 AM

The official word on tracking passengers from Ebola-linked U.S. flight

 

U.S. Customs and Border Protection Officers conducting  Ebola screening at JFK International Airport, in New York. Four other U.S. airports begin Ebola screening Thursday. ( CBP / EPA photo)

U.S. Customs and Border Protection Officers conducting Ebola screening at JFK International Airport in New York. Four other U.S. airports begin Ebola screening Thursday of passengers arriving from Ebola-affected countries of West Africa.  (CBP / EPA photo)

A second Texas health-care worker was diagnosed with Ebola the day after she flew on a Frontier Airlines flight.  The U.S. Centers for Disease Control and Frontier are contacting passengers who were on the flight.  Here are statements from them:

CDC statement:

“On the morning of Oct. 14, the second healthcare worker reported to the hospital with a low-grade fever and was isolated. The Centers for Disease Control and Prevention confirms that the second healthcare worker who tested positive last night for Ebola traveled by air Oct. 13, the day before she reported symptoms.

Because of the proximity in time between the evening flight and first report of illness the following morning, CDC is reaching out to passengers who flew on Frontier Airlines flight 1143 Cleveland to Dallas/Fort Worth Oct. 13.

CDC is asking all 132 passengers on Frontier Airlines flight 1143 Cleveland to Dallas/Fort Worth on October 13 (the flight route was Cleveland to Dallas Fort Worth and landed at 8:16 p.m. CT) to call 1 800-CDC INFO (1 800 232-4636). After 1 p.m. ET, public health professionals will begin interviewing passengers about the flight, answering their questions, and arranging follow up. Individuals who are determined to be at any potetial risk will be actively monitored.

The healthcare worker exhibited no signs or symptoms of illness while on flight 1143, according to the crew. Frontier is working closely with CDC to identify and notify passengers who may have traveled on flight 1143 on Oct. 13.  Passengers who may have traveled on flight 1143 should contact CDC at 1 800-CDC INFO (1 800 232-4636). ”

Frontier Airlines statement:

 “At approximately 1:00 a.m. MT on October 15, Frontier was notified by the CDC that a customer traveling on Frontier Airlines flight 1143 Cleveland to Dallas/Fort Worth on Oct. 13 has since tested positive for the Ebola virus. The flight landed in Dallas/Fort Worth at 8:16 p.m. local and remained overnight at the airport having completed its flying for the day at which point the aircraft received a thorough cleaning per our normal procedures which is consistent with CDC guidelines prior to returning to service the next day. It was also cleaned again in Cleveland last night. Previously the customer had traveled from Dallas Fort Worth to Cleveland on Frontier flight 1142 on October 10.

Customer exhibited no symptoms or sign of illness while on flight 1143, according to the crew. Frontier responded immediately upon notification from the CDC by removing the aircraft from service and is working closely with CDC to identify and contact customers who may traveled on flight 1143.

Customers who may have traveled on either flight should contact CDC at 1 800 CDC-INFO.

The safety and security of our customers and employees is our primary concern. Frontier will continue to work closely with CDC and other governmental agencies to ensure proper protocols and procedures are being followed.”

Comments | More in airlines, Ebola | Topics: CDC, Frontier Airlines, Texas

COMMENTS

No personal attacks or insults, no hate speech, no profanity. Please keep the conversation civil and help us moderate this thread by reporting any abuse. See our Commenting FAQ.



The opinions expressed in reader comments are those of the author only, and do not reflect the opinions of The Seattle Times.


403 Forbidden

403 Forbidden


nginx
403 Forbidden

403 Forbidden


nginx