Secret Law – Page 19 – Papers, Please!

Mar 02 2013

Travel blogger kicked off plane by pilot for taking photo of… seatback?

Frequent flyer and travel blogger Matthew Klint was recently kicked off a United Airlines flight from Newark to Istanbul after a flight attendant saw him take a picture of the back of the seat in front of him, and reported him to the pilot. The pilot told Mr. Klint, “You are not flying on this flight…. We’ll call the police if we have to.”

Perhaps unfortunately, Mr. Klint didn’t insist that the police be called, or call them himself, leaving him dealing with United Airlines’ public relations department rather than with legal authorities.

As a frequent flyer and blogger, Mr. Klint at least able to get the airline to talk to him, after the fact. But what can an ordinary traveler do in such a situation?

We talked about this last year in articles on Does an airline pilot have the right to refuse to let you fly? and What can you do if an airline pilot won’t let you fly? But it bears repeating:

Under Federal law, as common carriers, airlines must transport all would-be passengers willing to pay the applicable fare in their published tariff and comply with their published conditions of carriage. Not to do so is a serious violation of their duties.

If an airline refuses to allow you to fly, for any reason other than a violation of published laws, regulations, or conditions of carriage, you can and should make a formal complaint against the airline to the Department of Transportation.

A pilot can order you off the plane only if the pilot genuinely believes that you pose a hazard to the safe operation of the flight, in which case the pilot is required to log and report this safety incident.

If a pilot orders you off the flight for some other reason, or without logging and reporting his or her action as a safety incident, you can and should report the pilot to the FAA.

We’ve offered our support to Mr. Klint, should he wish to pursue a legal challenge to the actions of the airline and pilot against him.

Feb 15 2013

“Sentenced to life without air travel”

Last year, we reported on the case of Saadiq Long, an Oklahoma native and U.S. Air Force veteran who was stranded in Qatar for six monthes, unable to return home because for unknown reasons he had been placed on a “no-fly” list, and all airlines serving the U.S. had been forbidden to transport him, on the basis of some secret allegedly-derogatory information provided by some unknown government agency that had “nominated” him for this latest version of the U.S. government’s “enemies list”.

Eventually, in the face of public hue and cry, the FBI relented (temporarily, it turns out) and allowed Mr. Long to return to Oklahoma to spend Thanksgiving with his critically ill mother.

Happy ending to a sad story? No.

Mr. Long’s attorney, Gadeir Abbas of CAIR, who has led the legal fight against U.S. government “no-fly” orders, has an update this week in an op-ed article in the Oklahoman, the state’s newspaper of record:

Mr. Long has been living and working (for U.S. military contractors among other clients) in Qatar, where his wife and daughter remained while he went back to the U.S. for the holidays. But after letting him come home, the U.S. government has now put him back on the “no-fly” list, and won’t let him leave the country:

What’s most alarming about Saadiq’s ordeal is that the FBI will never have to explain its actions. When it comes to separating Saadiq — and many others — from family via its ever-growing and always secret watch lists, the FBI is judge, jury and executioner. Saadiq hasn’t been indicted, charged or convicted of any crime. And yet the FBI has claimed for itself the power to impose permanent punishment upon Saadiq: life without air travel. If FBI agents can impose this sentence on Saadiq, they can do the same to any of us.

Feb 04 2013

Update on Mocek v. Albuerque

On January 14, 2013, U.S. District Judge James O. Browning issued his first major ruling in Mocek v. Albuquerque, the Federal civil rights lawsuit brought for false arrest at a TSA checkpoint brought by Philip Mocek following his acquittal by a jury on trumped-up criminal charges.

Judge Browning dismissed Mr. Mocek’s complaints against the Federal (TSA) defendants. The reasoning of that ruling is in marked conflict with several findings on the same issues by the 4th Circuit Court of Appeals in Tobey v. Jones, although that decision isn’t binding on the District Court hearing Mr. Mocek’s case since it’s in a different Federal judicial circuit.

According to the Albuquerque Journal, “Mary Lou Boelcke, Mocek’s attorney, said she expects to appeal the ruling, either before trial or after Browning decides other issues regarding the city.”

On February 1, 2013, the remaining Albuquerque defendants (the city, airport, and individual police officers) filed their own motion to dismiss the complaints against them. That motion is now pending.

Jan 22 2013

TSA replaces “probable cause” with private profiling

The TSA has made explicit its intent to take the next logical but lawless step in the merger of (1) profiling of travelers and (2) privatization of judicial decision-making: outsourcing of decisions as to who should be subjected to what degree of intrusiveness of search to private contractors acting on the basis of commercial data.

The TSA already delegates on-the-spot “discretionary” decisions about searches (“screening”) to private contractors at airports like SFO, and relies for its profiling (“prescreening” and “no-fly”) decisions on commercial data contained in airline Passenger Name Records (PNRs).

Now a request for proposals quietly posted by the TSA early this month among the “Federal Business Opportunities” at FBO.gov, and spotted by the ACLU, gives notice that the TSA is considering “Third Party Prescreening” of travelers: TSA contractors would decide in advance (secretly, of course, on the basis of secret dossiers from private data aggregators) which travelers would be “invited” to proceed through the less-intrusive-search “Pre-Check” security lanes, and which would be subjected to “ordinary”, more intrusive groping of their bodies, opening of carry-on baggage and belongings, interrogation, etc.

In effect, “Third Party Prescreening”, as the concept is defined in the TSA notice to would-be contractors, would replace probable cause with private profiling as the basis for determining who among us would be legally obligated, as a condition of the exercise of Constitutional civil liberties and internationally recognized human rights, to submit to exactly what degree of intrusiveness of search of our persons and property.

The by-invitation-only TSA “Pre-Check” profiling scheme is already entirely arbitrary, as travelers have discovered when they have tried to find out how to obtain an invitation to the less-mistrusted-traveler club or why they haven’t been invited. “Don’t call us, we’ll call you” if we want to invite you, say airlines and the TSA. There are no publicly-disclosed substantive or procedural standards for invitation or inclusion.

“Third Party Prescreening” would extend that arbitrariness to advance decisions that particular travelers must submit to heightened “screening” (or are not to be allowed to proceed through lighter screening, which amounts to the same thing) before they will be “allowed” to exercise their right to travel.

Such a particularized decision, in advance, conditioning travel by a specific traveler on submission to a specific type or degree of intrusiveness of search is not what was contemplated in judicial decisions upholding “administrative” searches at airports. Rather, this is the sort of search that the Constitution demands be justified by probable cause, as articulated to and approved by a judge.

Private contractors are not judges. Fitting the profile, based on a secret commercial dossier, as determined by a secret algorithm, is not probable cause. No “Third Party Prescreening” could create a lawful basis for a search, or for interference with the right to travel of those who decline to submit to such a search.

Jan 09 2013

Judge refuses to look at secret “no-fly” evidence, reaffirms that travel is a right

What’s been most noteworthy in DHS legal arguments in “no-fly” and other related cases isn’t that the government has tried to argue in defense of intrusive and repressive surveillance and control of travel.

Instead, the consistent strategy of the DHS has been to argue (1) that it doesn’t have to give any arguments or evidence in support of these practices, because they are exempt from judicial review, and (2) that if it does have to give the courts any evidence or arguments, it can do so in secret, so that opposing parties and their lawyers are unable to know, or respond to, the government’s secret arguments and secret evidence.

Fortunately, some judges seem to be running out of patience with these claims that the executive branch of government is above the law.

We’re particularly encouraged by the latest order issued December 20, 2012 in the case of Ibrahim v. DHS, which continues to appear likely to result in the first review of a no-fly order, on its merits, by any court.

Since 2005, when she was refused boarding and detained by police when she tried to board a flight at San Francisco International Airport, Rahinah Ibrahim has been trying to find out who put her on the “no-fly” list and why, get off the “no-fly” lost, and obtain damages from the government agencies, contractors, and individuals responsible for her false arrest and the interference with her right to travel.

The city and county of San Francisco (responsible for the airport police) eventually paid Dr. Ibrahim $225,000 to settle her claims against them. But the federal government defendants have continued to try to get the case dismissed before any discovery, fact finding, or trial on the merits of Dr. Ibrahim’s claims.

The 9th Circuit Court of Appeals has twice rejected the government’s appeals of preliminary rulings allowing the case to go forward and allowing Dr. Ibrahim’s lawyers to proceed with discovery. But even after the federal defendants’ latest appeal was rejected, the government again moved the District Court to stay any discovery and dismiss the complaint.

In support of their latest motion to dismiss, the government went beyond filing evidence and legal arguments with the court “under seal” for in camera review by the judge (but not Dr. Ibrahim or her lawyers).

Instead, the government called the judge’s chambers to advise that a courier was on his way from Washington to the courthouse in San Francisco with some secret documents, which he proposed to show the judge, alone in chambers, and then take back to Washington so that there would be no record with the court, even in a “sealed” file, that would enable the court of appeals to review the basis for the judge’s decision.

Judge William Alsup of the U.S. District Court for the Northern District of California told the courier not to darken his door, and refused to look at any of the secret evidence, even in camera. Then he delivered a smackdown to the government in his ruling dismissing its motions.

Dec 05 2012

The DHS FOIA Office “is not in service”

We’ve been waiting for years for responses to some of our FOIA requests to the TSA and DHS, including a request for records of what happened to our earlier FOIA requests that were subjected to a special program of political review and reporting to the White House, a request for records that were previously improperly withheld under a claimed FOIA “exemption” which the Supreme Court eventually ruled didn’t exist, and a request for any records of the TSA having sought or obtained OMB approval for its Certification of Identity form.

Unfortunately, the de facto policy of the Department of Homeland Security is not just to ignore any FOIA requester who isn’t already suing it, but to make it impossible even to communicate with it or obtain proof of having made requests.

As we’ve noted before, the DHS uses a contractor who often fails either to deliver their mail or return the return receipts, making it impossible to prove they have received requests. Recipients have told us that the mail is often so browned and burnt by the contractor’s high-intensity x-ray screening that mail that is eventually delivered to DHS, after a delay of a week or so, is often illegible.

Despite huge expansion, changes, reorganizations, and relocations of DHS offices, the DHS FOIA Regulations and what is required by law to be the definitive list of DHS FOIA contacts hasn’t been updated since 2003, despite our repeated protests. Today, many of those addresses lead only to the dead-letter office.

Many DHS and component offices don’t disclose their physical locations. Even if you can find where their offices are, the doors are barred to those without appointments and government-issued photo ID.

And it’s getting worse. Now the main phone number for the DHS FOIA Requester Service Center (and, if you want to complain about their unresponsiveness, the DHS FOIA “Public Liaison” as well), has been disconnected or taken out of service. Not that it was usually answered by a human being, or that voicemail messages were usually returned, but turning off the phones entirely (or using only some other undisclosed phone numbers at their undisclosed location) is really a new low.

If you go to the Where to Make a FOIA Request page on FOIA.gov, and choose “Department of Homeland Security” and then either “Headquarters and Privacy Office” or “I don’t know which office”, you are directed to call (703) 235-0790. (Click the image above for a larger version of the Web page.) Call that number, and you get the recorded message, “Sorry. The number you have reached is not in service.”

We knew the DHS FOIA Office was “not in service”, or at least not serving us. But we didn’t realize that they had gotten the phone company to put a recording on their line telling that to anyone who tries to call.

[Update: The TSA and DHS claim that the “FOIA.gov” website is maintained by the Department of Justice and beyond the control of the DHS. But the same wrong number appears on DHS.gov at http://www.dhs.gov/check-status-your-foia-request as the number to call to find out the status of a FOIA request, along with a self-referential hyperlink for FOIA status information that links back to the same page.]

Nov 20 2012

TSA spreads FUD on “Opt Out and Film” week

This week is national Opt Out and Film Week. Across the country, travelers will be documenting the TSA’s practices of groping the genitals of anyone who wants to exercise their right to travel without “voluntarily” submitting to an x-ray or RF virtual strip search.

The TSA even acknowledges Opt Out and Film Week in its official blog, where Blogger Bob sez:

We’re also aware of the Opt Out and Film week, where some are planning on opting out of the body scanner and then filming their experience. TSA respects passengers rights to exercise freedom of speech as well as the rights of fellow travelers trying to get to their destination safely and without unnecessary delay. While the TSA does not prohibit photographs at screening locations, local laws, state statutes, or local ordinances may.

That looks to us like an attempt to sow Fear, Uncertainty, and Doubt (FUD) on clear-cut Constitutional rights.

While the TSA has a history of improperly calling local cops on photographers (for which we are currently suing both the TSA staff and the police who acted on their bogus complaints), it’s not true that “local laws, state statutes, or local ordinances may” restrict the exercise of First Amendment rights.

As we say in our cheat sheet, What you need to know about your rights at the airport:

You have the 1st Amendment right to film, photograph, and record what happens in public areas of airports, including your interactions with TSA and screeners. Photography and recording in airports and at TSA checkpoints violates no Federal law or TSA regulation. Any state or local laws that purport to prohibit this are likely to be unconstitutional. You have the right, for your own protection, to document what happens to you and what is done to you.

Nov 16 2012

The facts on the ground in Arizona

“Don’t trust, and don’t verify“, would seem to be the motto of authorities in Arizona when it comes to demands for documents and “proof” of citizenship and status — if your skin is brown.

Arizona’s SB1070 requires police, in certain circumstances, to “attempt” to determine your immigration status. But that obligation on the police does not create any obligation on individuals. In its initial decision on SB1070, the Supreme Court made clear that this provision of the law cannot Constitutionally be used as the basis to detain people without some other lawful basis.

Actions on the ground in Arizona, however, suggest that in practice the burden of proof is being placed on (brown-skinned) Arizonans to prove that they are “not illegal”, on pain of prolonged detention on the basis of mere suspicion (and regardless of the weight of the actual evidence).

The Phoenix New Times has been following the case of Briseira Torres. She was born (at her mother’s home, which the Department of State seems to find inherently suspicious) in Arizona, and her birth was registered (albeit late, as is common for home births) with the Arizona Office of Vital Records.

One doesn’t have to be registered with the government to be born, or to be a US citizen. But that didn’t stand in the way of Arizona and US authorities. When Torres went to the Federal Building to apply for a passport for her daughter, after submitting a copy of her own birth certificate as evidence of her daughter’s US citizenship by birth, the State Department employees at the passport office called in Arizona state law enforcement officers to help interrogate Ms. Torres.

Eventually, on the theory that the original registration of Ms. Torres’ home birth had been falsified, the Feds turned her over to state authorities, who had her indicted (withholding from the grand jury the state’s official record of her valid birth certificate, and falsely claiming to the grand jury that her birth registration had been “cancelled”) for fraud. She was jailed for 4 1/2 months, during which time she was separated from her child and lost her home and car because she couldn’t make the payments on them, before she got a lawyer and the state withdrew the charges.

Now, to try to retroactively justify their deprivation of Ms. Torres’ rights, state officials have initiated a newly-created administrative process to revoke the registration of her birth.

In other words, the state of Arizona wants to “un-birth” Ms. Torres — at age 31.

We’re glad Ms. Torres has a lawyer, and we hope she collects substantial damages from both Arizona state and county officials and the State Department “special agent” who initially detained her, called in the state cops, and eventually turned her over to their custody.

This incident began with Ms. Torres being called in to answer questions about her passport application for her daughter. The role of the Passport Office and other State Department employees shows exactly why we are so concerned about the State Department’s proposed new questionnaire for passport applicants.

Government “un-birthing” of citizens isn’t the only strange thing going on in Arizona, unfortunately.

At the Deconcini border crossing between the central business districts of Nogales, Arizona, and Nogales, Sonora, US Customs and Border protection is requiring some “trusted travelers” to submit to interrogation by allegedly lie-detecting robots developed (with DHS grant money, we presume) by the National Center for Border Security and Immigration at the University of Arizona.

If the robot thinks you are lying, “a more through interview would follow”, according to news reports.

But Ms. Torres’ example shows that if a human Fed in Arizona thinks you are lying about your papers, they will detain you and turn you over to the state of Arizona to be locked up without bail for months, without bothering even to look at your actual papers (not that you have to have any “papers” in the first place to be born or have rights).

In that light, we hope courts will look skeptically at the legality of prolonging the detention of a border crosser based on the statement of a semi-anthropomorphic animated robot that, “I think you are lying.”

Nov 13 2012

How Australia profiles travelers: A look inside the “black box”

At a “Big Data” conference in Sydney earlier this month, the head of Australia’s traveler tracking and profiling office (his actual title — we are not making this up — is “Director Intent Management & Analytics“) gave an unusually revealing presentation (PDF) [also here] about the nature of the government’s travel data warehouse and how it is used to predict the “intent” of travelers to and from Australia.

Klaus Felsche of the Australian Department of Immigration and Citizenship (DIAC) didn’t mince words, referring explicitly to “data mining”, “risk scoring”, and “profiling” systems and algorithms, although lamenting that DIAC doesn’t (yet) have access to social media profiles or some data from other Australian government agencies.

The US government has rarely used the words “scoring, “profiling”, or “data mining” with respect to its warehousing and use of Passenger Name Records (PNRs) and other travel data. Most of the architecture, as well as all of the rules and algorithms, have been withheld from public disclosure, even when we have requested this information under the Privacy Act, FOIA, and/or through foreign governments and airlines that have allowed PNR data subject to their jurisdiction to be fed into these data warehouses and data-mining systems.

The “threat analysis” component of US travel control systems like Secure Flight has remained an unexplained “black box” whose operations are part of the magical secret sauce that justifies the government in enforcing whatever its oracle decrees. In this diagram — the most detailed yet provided by the TSA — it’s the red box at right center.

So we are grateful to Mr. Felsche of the Australian DIAC for providing a clearer picture of what data governments are archiving about us and our travels, and how they are using it. Just remember, as you study his presentation, that:

“Targeting” — the one euphemism that still permeates Mr. Felshe’s presentation — means search, seizure, interrogation, and prohibition of travel. In other words, deprivation of fundamental rights, to a greater or lesser degree depending on whether it means mere delay and intrusion or whether it means being confined by a no-fly order to the island of Australia for the remainder of one’s natural life.
Australia is a relatively small country in population and (as his presentation makes clear) computing resources available to this component of the government. Presumably, what’s being done with travel data by DIAC is only a subset of what is being done by the DHS, and perhaps in the European Union.

Nov 06 2012

DHS Scrooge says U.S. citizen can’t come home for the holidays to see his ailing mother

In the latest episode in the increasingly bizarre but all too real saga of standardless secret administrative no-fly orders from the DHS to airlines, prohibiting the transportation back to their home country of US citizens, Oklahoma native Saadiq Long is being prevented from returning home to the US to spend the holiday season with his terminally ill mother.

Long is a US citizen and a veteran of the US Air Force, never charged with any crime in the US or any other country, who has been living and working as an English teacher in Qatar for the last several years. He’s also a convert to Islam, which shouldn’t be relevant but probably is.

When he learned of his mother’s illness back home in Oklahoma, he made reservations and bought tickets from KLM for flights from Qatar to the US for what might be a last visit with his mother.

Less than 24 hours before his scheduled departure from Qatar in May, KLM told Mr. Long that the airline (and all others serving the US) had been forbidden from allowing him to board any flight to the US.

Mr. Long has been trying ever since to find out why the government of his country has forbidden all airlines from transporting him, or to find a way to get those orders rescinded. But to date, the DHS has maintained its position that it will neither confirm nor deny whether it has issued any no-fly orders with respect to any specific person, much less the basis (if any) for such orders.

KLM explicitly informed Mr. Long that it had received a no-fly order from the DHS. So in theory, KLM would be required by Dutch data protection law to disclose that order to Mr. Long on request. That wouldn’t tell Mr. Long why he had been banned form returning to his country (the DHS probably didn’t share the reasons for its order with the airline), but would prevent the DHS from claiming in court that whether Mr. Long has been prohibited form flying is a state secret.

Given KLM’s poor track record when individuals have requested KLM’s records of its communications with governments, and the Dutch data protection authority’s poor track record of enforcing the law, it’s hard to predict whether KLM would comply with a request from Mr. Long for all orders or communications pertaining to him between KLM and the US government.

Mr. Long is being assisted by the Council on American-Islamic Relations (CAIR), which has led the struggle for judicial review of no-fly orders. CAIR staff attorney Gadeir Abbas, the leading advocate for US citizens exiled by no-fly orders, told Glenn Greenwald that, “Every few weeks I hear of another Muslim citizen who cannot return to the country of which he is a citizen.”

[Update: Mr. Long was again denied boarding by KLM in Qatar on November 8, 2012.]

Papers, Please!

The Identity Project