Bomb threat probed on flight at Oakland airport
Authorities are investigating an apparent bomb threat Monday on an Alaska Airlines flight from Seattle to Oakland, Calif. that originated from a note discovered in a bookstore at the San Francisco airport.
No bomb was found onboard Flight 342 after the plane containing 126 passengers and six crew members landed safety shortly before 8 a.m., said Alaska Airlines spokeswoman Bobbie Egan.
The threat surfaced about an hour earlier after a clerk at a bookstore in the nearby San Francisco International Airport discovered a letter about a bomb threat involving, said Mike McCarron, a San Francisco airport spokesman.
The clerk called police and San Francisco officials quickly contacted Oakland International Airport officials, McCarron said.
The plane landed about 15 minutes ahead of its scheduled arrival and was met by members of Transportation Safety Administration and the Alameda County Sheriff’s department in a remote area of Oakland airport, Egan said.
Passengers were transported to a holding area and rescreened as bomb-sniffing dogs inspected luggage on the tarmac, Oakland airport spokeswoman Joanne Holloway said.
The aircraft and luggage were eventually cleared and the passengers were later released, Holloway said.
The incident remains under investigation, Egan said.
California Aviation Alliance: Airport News List E-mail
Sent by AviaEd@netscape.net – Lorena de Rodriguez on behalf of CAA subscribers. Add your comments to these stories realtime online at http://aviaed.wordpress.com/.
To subscribe or unsubscribe to the Airport News List, send an email, from the email account you wish to receive or discontinue CAA posts on, addressed to email@example.com and place only the following in the first line of the body of the message: Subscribe airport YourFirstName YourLastName YourJobTitle YourAirport/Company
Manage your CAA subscriptions with the user friendly Mail List Administration database. You’ll find it at: http://californiaaviation.org/cal/index.cfm
Contact firstname.lastname@example.org with problems with your subscription.