Whoops! No Double Standard Policy and US Embassy Bogota’s Threat Info Dissemination

The State Department has what is called the “no double standard” policy  in its travel information program. 7 FAM dictates that if State shares important security threat information including criminal information with the official U.S. community, such information should also be made available to the non-official U.S. community.  Selective notification is against the law.  The regs also says that “If a post issues information to its employees about potentially dangerous situations, it should evaluate whether the potential danger could also affect private U.S. citizens/U.S. non-citizen nationals living in or traveling through the affected area.”

The origin of the no double standard policy came from the Lockerbie bombing of 1988. Below is an excerpt from Jim Arkedis of ppi:

In the days before the holiday, the U.S. consulate in Frankfurt received vague threat information about a potential terrorist attack targeting American citizens.  The information didn’t state much, other than that the strike would emanate from Germany or possibly London.  The Regional Security Officer posted the threat information on a public bulletin board in the consulate, and many American government workers changed their Christmas travel plans.

As you’ve probably figured out by now, the travel warning turned out to be credible – the Lockerbie bombing of December 21, 1988 killed 190 American citizens, 270 total, traveling from London to JFK airport.  The flight had originated in Frankfurt, where the bomb was originally smuggled aboard.

While it was of course good that certain American government employees had avoided the catastrophe, a policy problem arose.  In short, there was a double standard in place:  Americans (and their families) who happened to work for the government in Frankfurt as everything from intelligence officers to economic advisors to custodians avoided the tragedy due only to their preferential position.  Americans elsewhere in Europe, whether in government or not, weren’t warned.

The Foreign Affairs Manual avoided mention of Lockerbie in its explanation of this policy:

In 1990, Congress passed the Aviation Security Improvement Act, which, in Section 109, added to the Federal Aviation Act a requirement that the President “develop guidelines for ensuring notification to the public of threats to civil aviation in appropriate cases”. The Act requires that the guidelines identify the officials responsible for deciding whether public notification of a threat is in the best interests of the United States and the traveling public, based on a consideration of among things, the specificity of the threat, the credibility of the information, and the ability to counter the threat. The guidelines were to be distributed to appropriate officials in the Departments of Transportation, State, and Justice, as well as to air carriers. The law prohibits selective notification of a threat to civil aviation to only selective potential travelers unless the threat applies only to them. These and other related provisions are now codified in 49 U.S.C. 44905. After enactment of these provisions, the Department decided to follow similar policies in non-civil aviation contexts.

The Office of the Inspector General questions the embassy’s threat information dissemination in light of the no double standard policy.  Here is the US Embassy in Bogota, a 15% danger post: 

No Double Standard

The dissemination of threat information at this danger pay post may violate the Department’s “no double standard” policy. Some areas of Bogotá are off limits to U.S. Government employees because they are considered too dangerous. However, these areas are not identified as such in either the Colombia country-specific information sheet or the travel warning.

In addition, the embassy controls travel of its own employees throughout most of the country by delineating two safe areas (the north coast between Cartagena and Santa Marta) and the area around Bogotá (corresponding roughly to the Sabana de Bogotá plateau). The RSO approves visits to the rest of the country on a case-by-case basis after reviewing the security situation. Neither the Colombia country-specific information nor the travel warning mentions these two safe areas.

A third, lesser concern is the embassy’s use of hotels that are approved in advance by the RSO. Although vetting hotels is commonplace for official travel, requiring embassy employees to use the hotels while on personal travel again raises questions about possible double standard issues.

Fourth, the RSO issues email alerts to embassy staff about demonstrations or other disruptions in traffic that might impede embassy employees and make them vulnerable to criminal acts. The RSO does not send these alerts to a public Web site for the American traveling public.

The Department’s guidance on no double standard in Foreign Affairs Manual guideline 7 FAM 052.1 a. (1) applies to important security threat information, including criminal information. It states that “[s]uch information, if shared by the Department with the official U.S. community, generally should be made available to the non-official U.S. community if the underlying threat applies to both official and non-official Americans.”

There is no evidence that the travel restrictions for embassy employees for personal travel are based on threats that would not also apply to private U.S. citizens in Colombia. Therefore, the OIG team believes that the present system may violate the Department’s “no double standard” policy.

Recommendation 12: Embassy Bogotá should request from the Department of State by record communication a clarification of whether its dissemination of threat-related information is consistent with the Department of State’s “no double standard” policy and alter any procedures that do not comply with this policy. (Action: Embassy Bogotá)

Let’s add 7 FAM 053.2-2 (e) below which has very clear reminders:

Remember that if you conclude you should warn your personnel or any U.S. Government employees, whether permanently stationed or on temporary duty abroad, about a security threat, your request for Department approval to warn post personnel should also include a request to share that same information with the non-official U.S. community under the “no double standard” policy (see 7 FAM 052). The policy applies whether the information is shared with U.S. Government employees in town meetings, in post newsletters, by e-mail, or on the telephone. The threat or warning information might include information about locations within the host country including hotels, restaurants, entertainment spots, places of worship, tourist sites, etc. Unless the threat is specific to a particular institution for reasons peculiar to that institution, you should not list names of specific locations, including names of hotels or restaurants, for which threat or warning information is available. You should also refrain from developing lists of “approved” hotels. In providing such lists to the community, you may actually increase the risk that perpetrators could change the target, thus increasing the risk to U.S. citizens/nationals who may be relying on such lists. (underlined for emphasis).






US Congress on Super Stoopid Ride: Saving $16 Million at a Cost of $364 Million

As if the debt ceiling theater was not badly scripted and terribly acted enough. 

Congress went on vacay even as the partial shutdown of the Federal Aviation Administration deactivated some 74,000 employees (FAA, construction workers, etc) and resulted in a loss to the U.S. Treasury of some $30 million a day.

The CSMonitor reports on the newly announced deal that is good until next month when Congress returns to do a cha-cha:

Funding for the FAA expired on July 23, following nearly four years of short-term extensions. Both the House and the Senate have passed long-term FAA funding bills that clashed on partisan and parochial issues, such as rules that make it tougher to organize unions and subsidies to rural airports.

Since members of the House have already left town, the deal involves the Senate’s passing of a House measure extending funding for the FAA through Sept. 16, in a vote expected on Friday. The agreement also frees up $2.5 billion in federal grants for delayed construction projects. Congress will return to the outstanding issues in September.

Well, that’s dumb, okay, but here is what’s even more stupid, as stupid does it in Washington, D.C. Congress was trying to save money by defunding rural airports at the tune of $16 million. Funding for FAA expired on July 23, at a cost of some $30 million a day in lost revenue to the U.S. Treasury. So our elected representatives in Congress, so wise and smart managed to saved $16 million at a cost of $364 million in lost fees in the last couple of weeks.

In what other universe is this type of stupidity acceptable?

Dear U.S. Congress, the Chinese are falling off their chairs laughing at all of us, and why not?!  With this kind of elected representatives, what else can possibly go wrong?