Minnesota

NEW VIDEOS: Interviews from Enbridge blockade in Leonard MN & Indigenous Canadians barred from their consulate by Minneapolis police

Got a batch of videos here from the last week to check out. Glad to have a little chance to bring these interesting projects, including Idle No More MN & the Enbridge Blockade near Leonard MN (also known as the encampment) going strong since late February. All these videos are basically unedited and you can remix them as Creative Commons at your leisure!

Interview w Tom Goldtooth, Indigenous Environmental Network, the Native fight for natural world

Really fascinating interview, unedited, with Indigenous Environmental Network longtime organizer Tom Goldtooth inside the kitchen tent at the Enbridge Blockade/encampment near Leonard MN. Covers capitalism, colonialism, Indigenous organizing and tar sands resistance. Thanks Tom!

VIDEO - CREATIVE COMMONS W REMIX!

https://www.facebook.com/EnbridgeBlockade?ref=ts&fref=ts

https://www.facebook.com/pages/Indigenous-Environmental-Network/18626498...

Interview with Tito Ybarra, Enbridge protest encampment organizer & Native comedian

Interview with Tito Ybarra, camped at Enbridge Encampment/blockade at Leonard MN. A popular native comedian has been bottomlining the camp protesting above several pipelines operated by Enbridge without an easement on Red Lake ceded land. Covers humor in politics, organizing the camp & more.

SUBSCRIBE: The 1491s: http://www.youtube.com/user/the1491s

Slapping Medicine Man: http://www.youtube.com/watch?v=MVWLHMZ-ceE

Learn the AIM Song: Singing lessons by the 1491s: http://www.youtube.com/watch?v=xJ89HBfaLs4

Follow Tito: https://www.facebook.com/TitoBAYBAY

Comedy page: https://www.facebook.com/TitoComedy?fref=ts

https://www.facebook.com/EnbridgeBlockade?ref=ts&fref=ts

https://www.facebook.com/pages/Indigenous-Environmental-Network/18626498...

////////////

So these are the videos from the March 20 Idle No More protest in Minneapolis. @tshirttoby also shot a livestream.

Canadian citizens barred from access to their Consulate in downtown Minneapolis as IdleNoMore protesters try to register their concerns with the Canadian govt.

This is related to a major Idle No More symposium happening Friday Mar 21st

INFO https://www.facebook.com/events/449434278463290/?ref=3

VIDEO - CREATIVE COMMONS W REMIX!

PT1 http://youtu.be/fQHAB0QgoTc

PT2 http://youtu.be/cQ8nr3oO7qk

PT3 http://youtu.be/g19DQUKu2rA

Minnesota Anonymous to protest "Church of Scientology" travesty-industrial complex in St Paul tomorrow - in blizzard?

UPDATE 3PM SUNDAY: Here's the video I livestreamed at the protest today. Bambuser link: http://bambuser.com/v/3363747 Pretty fun and good champs in the snow amirite?

Youtube version may finish processing this year?

spacegorillasvotexenu.jpeg

A heads-up for lulzcats in the Minnesnowta region: Minnesota Anonymous people have filed a permit to protest at the Church of Scientology "Ideal Org" at Wabasha & Exchange Streets, (the old Science Museum of MN building) starting at 10:30AM roughly, marking five years of Chanology, the large-scale protests which brought the old era of abusive Scientology schemes to a close. I will probably livestream from some part of this at http://bambuser.com/channel/hongpong & keep an eye on http://twitter.com/hongpong for updates otherwise.

Also given the expected snowy weather tomorrow, the exception to "CONCEALING IDENTITY" in Minnesota Statute may clearly apply:

609.735 CONCEALING IDENTITY. - 609.735, 2012 Minnesota Statutes

A person whose identity is concealed by the person in a public place by means of a robe, mask, or other disguise, unless based on religious beliefs, or incidental to amusement, entertainment, protection from weather, or medical treatment, is guilty of a misdemeanor.

Despite a decidedly lowprofile promotional scheme, this was already in the local paper. Info from PioneerPress.com published Feb 6th, updated 7th: Church of Scientology 'dance protest' in St. Paul a go. Vuvuzela playing? Limited. - TwinCities.com

The St. Paul City Council voted to allow a planned "dance protest" outside of the Church of Scientology in downtown St. Paul, but limited a requested noise variance to a single hour.

Members of Minnesota Anonymous had applied for a noise variance from 10:30 a.m. to 4:30 p.m. on Feb. 10. The group's application listed vuvuzelas, the type of horns used at sporting events, and speakers among their instruments.

"Free speech is one thing, and a total disruption of people's lives is another," said St. Paul City Council Member Dave Thune. "They're free, of course, to picket, carry signs, at various times."

Before the vote, Nancy Schumacher, a public affairs director for the Church of Scientology, told the council that a noisy protest would disrupt Sunday services, church courses and residential neighbors.

"The intent of the group is to actually harass and intimidate church members, and we're hoping you will vote against it," she said.

sci-org-stpaul.jpeg

No one representing Minnesota Anonymous spoke at the hearing.

Here is my commentary on this ugly fake religion on PP:

It was a sad travesty when the once proud, educational and even fun Science Museum of Minnesota building of my youth got taken over by this nasty, greedy little corporate cult which is partially based on the intrinsically selfish & maniacal teachings of Hubbard's personal hero & organizer of Satanic sects, Aleister Crowley. It turns the principles of the Enlightenment on its head to have such 'black disinformation' spammed out into the larger community.

I have met people whose family lives have been ruined, through no choices of their own, because of Scientology's classic cult strategy of dominating and splitting families, requiring years of deprogramming simply to obtain a normal life once more. That type of abuse certainly suffices to justify protesting this corporatist, 'intellectual property' hoarding knockoff cult. Also they kill people through brainwashing at their front organizations such as "Narconon Arrowhead" in Oklahoma. I'm not a "member of Anonymous" but I can agree this travesty of a site offends me as much as anything in the Cities.

See pics from Fibonacci Blue for older local protests at the now-closed Nicollet Mall org: Flickr: Fibonacci Blue's Photostream. See late 2011 opening of this place post: Largest Scientology church in Midwest opens in downtown St. Paul - TwinCities.com.

How to check cops checking your driver's license! Plus full texts of Anne Marie Rasmusson lawsuit settlements for cop ID checks

Yet another nasty branch on the poisonous tree of data abuse in Minnesota is bearing its digital fruit. Anne Marie Rasmusson, a former law enforcement officer, got 'checked out' by an absurdly sprawling array of Minnesota law enforcement officers illegally abusing their driver's license lookup systems. Three major legal documents from the settlements are included below, I believe for the first time on the web (I might be wrong but didn't spot anything on Google).

For the backstory of the weird law enforcement gangstalking of Rassmusson & subsequent litigation, see Nov 2 2012: Anne Marie Rasmusson's settlement haul now over $1 million - Aaron Rupar / CityPages.

From a clever data-fishing colleague, here is one proven method for promptly obtaining your own DVS data:

E-mail kim.jacobson@state.mn.us with "Hi Kim! This is a request to inspect public data under the Minnesota Government Data Practices Act using my own equipment, in electronic form. I would like to inspect all records and logs of when my driver's license and motor vehicle information on file with DVS was accessed, along with date, time, request detail and requesting agency. My driver's license number and license plates are: X. Thanks!"

100% Lulz virtually guaranteed. Not a horrible time lag either, from what I am hearing from people.

Better Know An Acronym: Mpls PD's ALPR & MnDOT's MBUF, the Parallel DataSchemes: Better get yr DVS records while they're hot: the government has a habit of clamping down on these kinds of data flows, legislative authorization be damned!

On another critical but separate mass surveillance & data control issue, IPAD | Information Policy Analysis Division, Minnesota Department of Administration is taking public comment until January 30, 2013 on the issue of the automated license plate reader system which Minneapolis has semi-extralegally shifted from public to non-public data classification. The PDF is here: www.ipad.state.mn.us/docs/mplsappalpr.pdf. One idea: let IPAD know that this tech is dangerous for data regardless of who is supposed to have access. As the burgeoning DVS omnishambles indicates, 'sensitive' data should be minimized in government, and even 'authorized' personnel actually shouldn't be trusted to operate these systems without granular and public systems of accountability.

Again it is worth pointing out that the City of Minneapolis itself argued in the PDF above that the data generated by the Minneapolis Police Department's Automated License Plate Reader (ALPR) system is dangerous and must be made non-public for the same reasons that MnDOT's Mileage Based User Fee (MBUF, aka Intellidrive) data is dangerous.

MBUF is a story I have been following for several years - it would send extremely frequent location/direction/velocity info to the government & its military-industrial contractor, Battelle, for every user in order to generate a dollar figure for taxing the vehicle - only nuking all your remaining privacy in the process. After many months, much MnDOT MBUF data was released via a Mn Data Practices Act Request, though it is difficult to work with. See Nov 30 2012: EXCLUSIVE MnDOT info cake: 2.97gb emails/docs on the Mileage Based User Fee (MBUF)- Minnesota's GPS vehicle taxing regime in the works

Previously: Jan 9 2013: MPD Tracking OccupyMN Facebook BBQs: Minneapolis "secret" Strategic Information Center / Emergency Operations and Training Facility 25 37th Ave NE in Fridley // MPD Homeland Security Unit at Cruz House: Minneapolis Police Department data request on Occupy Minnesota finally released; sketchy anti-Occupy fusion-style police material from Nevada // Dec 14 2012: Mordor Mayor Rybak makes moves to hide Minneapolis panopticon: Total Minneapolis Awareness Automatic License Plate Reader records form 'retroactive surveillance' empire. Ye Gods we keep catching substantial fish!

The issue of abusive operations in the MN Department of Public Safety-controlled DVS database is becoming a major issue recently, with the decidedly unlikely duo of Republican-aligned Hennepin County Sheriff Rich Stanek and indefatigable Star Tribune reporter Randy Furst both finding highly indefensible query activity on their records. Minn. driver’s license data snoopers are difficult to track | StarTribune.com:

Despite widespread misuse of driver's license records in Minnesota, determining just who is peeking into your files can prove nearly impossible.

The Minnesota Department of Public Safety, which oversees the driver's license database, refuses to tell people the names of users -- generally public employees -- who have looked up their information. Perhaps the most high-profile citizen getting stonewalled by the state is Hennepin County Sheriff Rich Stanek, who is sparring with the department over what he believes were inappropriate queries into his driver's license records.

The Driver and Vehicle Services (DVS) database, which contains addresses, photographs and driving records on nearly every Minnesotan, is protected under state and federal law. State records show that public employees frequently have misused the database by running people's names without a business purpose. That is the subject of a major lawsuit that recently ensnared police officers across Minnesota, as well as a criminal case pending against two Minneapolis employees.

Stanek learned in June that employees at 21 agencies, including his own office, had accessed his records over several years. Some of the queries came from as far away as Wells, Minn., a small town 117 miles south of Minneapolis that he has never visited. The Department of Public Safety would not provide him with the names of the users.

"I believe that some or all of these requests may have been without a legitimate government purpose," Stanek wrote in a December letter to the Department of Administration, asking for an advisory opinion on the matter. The Department of Public Safety "and DVS appear to have purposely created obstacles to deny me an opportunity to track illegitimate access."

Stanek had made two previous requests for his lookups out of curiosity, and was surprised by how many agencies had queried his name.

This time, he says, a security concern prompted his request for the lookups.

He believes the state has an obligation to show that the lookups had a legitimate purpose, even if they do not hand over the names.

Anyhow, a source provided a great deal of the Rasmusson legal paperwork obtained via the Minnesota Data Practices Act. I don't think it's around elsewhere on the Internet, so here it is. I haven't looked over too many settlements myself, so this is overall just funny stuff about a serious topic -- nothing like a government formally conceding abuse and paying out hard-collected taxpayer cash to cover for some ridiculous abuse of officially "necessary" authority.

I wonder what kind of world we'd live in if our government units were actually run by people who never screw up like this, wasting all these resources and being generally abusive. There will surely be more inquiries along these lines...

Three parts:

Rassmusson Lawsuit 1 1110 001 (44pgs) - direct download 1.8MB: rassmusson_lawsuit-1-1110_001.pdf

Rassmusson Lawsuit 1 1110 001 by Dan Feidt

Rassmusson Lawsuit 2 1109 001 (5 pgs) - direct download 205KB: rassmusson_lawsuit-2-1109_001.pdf

Rassmusson Lawsuit 2 1109 001 by Dan Feidt

Rassmusson Lawsuit 3 1102 001 (39 pgs) - Direct download 1.9MB: rassmusson_lawsuit-3-1102_001.pdf

Rassmusson Lawsuit 3 1102 001 by Dan Feidt

Leaving it there for now, but hell, something will probably turn up yet again before I even have time to deal with it!!

MPD Homeland Security Unit at Cruz House: Minneapolis Police Department data request on Occupy Minnesota finally released; sketchy anti-Occupy fusion-style police material from Nevada

///// UPDATE 2:30AM Jan 9: Diggings lead to a truly under-appreciated and basically new police strategic intelligence outfit in Fridley complete with documentation about why they ought to be tracing protesters on state-of-the-art gear - WCCO stated this place is "secret"! LOTS MOAR: MPD Tracking OccupyMN Facebook BBQs: Minneapolis "secret" Strategic Information Center / Emergency Operations and Training Facility 25 37th Ave NE in Fridley /////

After some months, the Minneapolis Police Department released dozens of pages about Occupy Minnesota / Occupy Minneapolis and several high-profile operations, particularly the eviction of protesters from 4044 Cedar Ave. This data was released from the Department late yesterday afternoon.

Interestingly the suppression of the civil disobedience at 4044 Cedar fell under the rubric of the MPD Special Operations Division / Homeland Security Unit. Further data requests to this unit could be interesting, including federal grants applied for similar suppression activities in the name of "Homeland Security."

occupy-mpls-mpd-net7.png occupy-mpls-mpd-net6.png

This email related to the "Emerging Issues" PDF from Nevada below (see the attachments field).

occupy-mpls-mpd-net1.png

One interesting feature: the coordination between the MPD and the Downtown Improvement District (DiD) which is aligned & serves the purposes of the downtown property owners (as opposed to homeless, indigent people downtown etc). DiD, while seen as a semi-public entity, is privately directed and is not an openly participatory structure. DiD has a central office that coordinates over a digital radio system with the downtown First Precinct and corporate building security officers including during protests.

The other major item of wider interest is a sketchy Nevada operation partially merged with the Los Vegas Police Department. It was use as "a lot going on" from Darrel Stephens@carolina.rr.com whoever that is...

"Emerging Issues in the Occupy Movement" from the Major Cities Intelligence Commanders Group (MCC ICG Sub-Committee)and the Southern Nevada Counterterrorism Center (SNCTC) is really a classic chestnut. The email addresses to LVMPD.com seem to be an official domain of Las Vegas law enforcement, not a private organization. I don't recall seeing this Occupy-related writing from this organization circulate elsewhere. If so, we have a new taxpayer-supported 'node' generating more hype in the "counterterror" national political activist monitoring network.

occupy-mpls-mpd-net2.png occupy-mpls-mpd-net3.png occupy-mpls-mpd-net4.png occupy-mpls-mpd-net5.png

Fortunately the "LAW ENFORCEMENT ONLY - DO NOT DISSEMINATE" pseudo-classification does not really have much if any actionable meaning under the Minnesota Data Practices Act, though we can surely expect proposals to create tons of secret data piles under loosey-goosey unnecessary pseudo-secrecy at the Minnesota Legislature this session. Follow @richneumeister for sharp updates on that whole front for sure!

I want to also point out a couple other good recent releases posted on Scribd about Minneapolis. The ALPR reader system ongoing story - see Dec 2012: Mordor Mayor Rybak makes moves to hide Minneapolis panopticon: Total Minneapolis Awareness Automatic License Plate Reader records form 'retroactive surveillance' empire | HongPong.com && also Nov 30 2012: EXCLUSIVE MnDOT info cake: 2.97gb emails/docs on the Mileage Based User Fee (MBUF)- Minnesota's GPS vehicle taxing regime in the works. The City of Minneapolis itself neatly ties both these stories together in the next link by arguing that these surveillance data programs are both dangerous! Thanks!

City of Minneapolis Application to IPAD requesting classification of all ALPR data as not public. It's worth an entirely separate post, but basically here the City of Mpls argues that the ALPR license plate reader should be classified by the State of Minnesota Dept of Administration's "IPAD" division as confidential, because IPAD classified data from an entirely different tracking project, the MnDOT IntelliDrive / Mileage Based User Fee (MBUF) system, is also dangerously specific data which easily indicates when homes are vacant due to daily traffic patterns, etc. So the argument from the city is that the data is dangerous: ALPR is dangerous, MBUF is dangerous, therefore should be classified -- but still collected of course!

Page 7 of this one: http://www.scribd.com/doc/117555926/Metro-Transit-Police-Report-on-Chalk-and-Silly-String talks about using Trespass notices specifically because of OccupyMN. For more docs like these see SmileyRevolt & twitter.com/smilyus.

There does not seem to be very much other personal data of regular people, besides one page of mugshots of arrestees with their birthdays. However I do not have the time to parse more carefully & if this acts as an intrusion to anyone in the public I apologize in advance. IN theory, what the state defines as private personal data should not be released on this kind of material. Lacking a handy secure redaction tool for PDFs, I deleted page 99 from part 1 in this release..

Here is the Data Practices Act official response email which accompanied this. If the requestor wishes to have their name added back onto this I will do that, just took it off by default.

----- Forwarded Message -----

From: "Meyers, Linda" <Linda.Meyers@minneapolismn.gov>

To: [....]

Date: Mon, 7 Jan 2013 19:43:48

Subject: DP 1229 - Occupy MN data

Mr. [....],

We received your check today and I’ve attached the data you requested regarding Occupy MN. There are 259 pages. Again, we apologize for the delay in getting this to you.

Linda Meyers

Police Support Technician I

MPD Records Information Unit

350 S. 5th St.

Minneapolis, MN 55415

612-673-2961

linda.meyers@minneapolismn.gov

Non-public and/or Privileged and/or Confidential and/or Private Information:

This electronic message may contain investigative data which is non-public pursuant to Minnesota Statutes section 13.82 subdivision 7, or personnel data which is non-public pursuant to Minnesota Statutes section 13.43 subdivision 4. If you are not the intended recipient of this e-mail: (1) do not read the content of the message; (2) immediately notify the sender that you incorrectly received the message; and (3) do not disseminate, distribute, or copy this e-mail.

//////////

134 pages (135 before the removed page) - Part1 originally 4242Kb. With the edit, the md5 sum is aef289624969402680255a15dea1aec3 MPD_OccupyMN_Data_part1b.pdf - Posted also at http://www.scribd.com/doc/119531853/MPD-OccupyMN-Data-Part1b

Direct download: MPD_OccupyMN_Data_part1b.pdf 6.7MB

MPD OccupyMN Data Part1b


Part2 3183Kb.

1d58ba5700273ede7b3dd5ad0595fa5c MPD_OccupyMN_Data_part2.pdf - Posted also at

http://www.scribd.com/doc/119527079

Direct download 3.3MB MPD_OccupyMN_Data_part2.pdf

MPD OccupyMN Data Part2

The Next Big Thing - Idle No More MN: Indigenous protest at Mall of America

Many hundreds, perhaps a thousand or more, Natives and supporters joined up at the Mall of America on Dec. 29 in sympathy with those struggling against the Canadian government. Burned sage wafted out into the crowd as echoes of drums & cheers throbbed off the walls. Reportedly, many were in extra high spirits later Saturday at the Minneapolis American Indian Center New Year's Powwow gathering, as so many indigenous people have mobilized so quickly across international borders in just recent days.

This went off way easier than some expected. I heard secondhand something like that management had offered the rotunda - or at least, more like there was an understanding that there would not be arrests. Earlier someone said that a VP for Operations had called and threatened arrests a little while after the event was first suggested, so in any case MOA management didn't want arrests to happen it appears. The rotunda which was full of Xmas stuff, and instead everyone headed for the large space on the Northeast corner in front of Sears.

(Another likely factor: I heard from one person that MOA owners are still trying to get in on a casino, so they had a fiscal incentive to work something out & not get the MN tribes angry. There have been casino plans near the Mall site previously, years ago Caesar's spent lots of money in Minnesota lobbying for this, & the dream of raking cash from Japanese tourists continues...)

It was really nice to be able to livestream this to GlobalRevolution.tv and a wider audience. A Best Buy ad placard overhead declared "The Next Big Thing" which seemed quite appropriate!

Earlier videos from the first US demonstration: Idle No More in Minneapolis: First indigenous protest vs new Canadian repression in the United States - The Seventh Fire isn't just an Anishinaabe thing!

Main video: Not great audio at the high levels, but good interviews I think. Please remix - Creative Commons!

Shorter clip shot by a friend:

Additionally a friend sent video of a pretty sketchy guy that admitted to being a corporate videographer, though he did not say for where. Here are the 2x clips of this guy:

Photo via Patricia Shepard: (SRC)

229944_10151395600794796_1199062464_n.jpg

Image by Robert DesJarlait:

533546_10200202396404518_1803348670_n.jpg

All these videos are licensed Creative Commons - with attribution. So please remix!

If you see this guy taping your events - well watch out for him!

idlenomore-MOA-creeper.png

idlenomore-MOA-creeper2.png

idlenomore-MOA-creeper3.png

idlenomore-MOA-creeper4.png

idlenomore-MOA-creeper5.png

This guy reminded me of earlier work on the weird Mall of America shady intelligence operations & Suspicious Activity Reports, which I and some other colleagues with TC Indymedia discovered a few months before PBS made a big deal out of it. Here is the video that I shot in late 2010 about this:

You'll see a certain resonance with this weird guy. [Also this was the same group of people evaluative state law enforcement intelligence systems who I notified of the routine laundering of drug money through the banking system including the Federal Reserve (VIDEO). Good times!]

Idle No More in Minneapolis: First indigenous protest vs new Canadian repression in the United States - The Seventh Fire isn't just an Anishinaabe thing!

On Wednesday, Dec 19th, indigenous and allies launched the first protest in the United States in solidarity with their kin further north in what is known today as Canada. Prime Minister Harper basically decreed a bunch of lakes critical to indigenous survival are no longer environmentally protected, which clears the way to their destruction at the hands of the tar sands-oriented petrochemical industry.

According to Robert DesJarlait (talking in the first video) the US/Canadian border is becoming more restricted for natives/shut down right now & border protests have been called as well.

Unedited / Creative Commons with attribution to HongPong or Dan Feidt. Unfortunately was not able to livestream it - either maple syrup-powered EMP cannons or the relatively mild cold interfered with power levels. Technology not cooperating with me lately - not easy to edit FlipCam clips either :-/ I have not videotaped any protests in quite a while & this one was really inspiring, I was lucky to be involved in any way.

Later in the day at the American Indian Center I also saw representatives from Red Lake reservation leaving for the site of the school shooting in Connecticut in solidarity with those victims, since Red Lake had its own disastrous school shooting in 2005.

I wish our indigenous brothers and sisters the best of luck struggling against the power structures in both these nationstates which are determined to strip them of dignity and the means to survive autonomously in harmony with nature.

Also our colleague Will already posted three videos as well - this one has the most views - http://www.youtube.com/watch?v=06xImpIKyDc - get the rest on his channel. Here's the original event post on Facebizzle with a bunch of comments and links.

On Friday the Day of Action for Idle No More will be starting - where else? in Egypt! Idle No More day of action Friday will begin in Egypt | APTN National News. Drum circles for noon Mountain time zone have been called so I believe there will be a protest at 1PM around Minnehaha Park/Coldwater Springs though I am not sure of where exactly.

I like this one - it's 18 minutes totally unedited, the last song and going up in the elevator to the Consulate & most of that time in there. Watch Harper's Canadian consular staff lurk behind their thick walls & bulletproof glass, taking cell pics and dipping!

MORE LINX:

http://idlenomore1.blogspot.com/

http://idlenomore.tumblr.com/post/38329891610/idle-no-more-support-rally...

http://thelapine.ca/obama-calls-harper-large-lump

https://www.facebook.com/events/205119732946505/?ref=3

http://aptn.ca/pages/news/2012/12/19/idle-no-more-day-of-action-friday-w...

http://www.youtube.com/watch?v=06xImpIKyDc

http://www.youtube.com/watch?v=TsSUkwZ1VZg

http://idlenomore.makook.ca/

Friday, December 21, 2012

Idle No More - PARLIAMENT HILL- OTTAWA

http://www.facebook.com/events/437759016287760/

Friday, December 21, 2012

Idle No More, Solidarity Action -LONDON, UNITED KINGDOM

http://www.facebook.com/events/458961510829311/

Friday, December 21, 2012

IDLE NO MORE: Peace River Region -BRITISH COLUMBIA

http://www.facebook.com/events/492285850793858/

Sunday, December 23, 2012

Idle No More -VANCOUVER

http://www.facebook.com/events/539740012721038/

Saturday, December 22, 2012

Idle No More -HAMILTON, ONTARIO

http://www.facebook.com/events/448076668589295/

Friday, December 21, 2012

Idle No More rally- PRINCE ALBERT- SASKATCHEWAN

https://www.facebook.com/events/127655597393724/

Friday, December 21, 2012

IDLE NO MORE - WINNIPEG NATIONAL EVENT

https://www.facebook.com/events/551422504885143/

Friday, December 21, 2012

IDLE NO MORE -SASKATOON

http://www.facebook.com/events/123368197825076/

Friday, December 21, 2012

"IDLE NO MORE" PROTEST - MONTREAL

http://www.facebook.com/events/430768096977486/

Friday, December 21, 2012

Idle No More Rally - OWEN SOUND

http://www.facebook.com/events/307840622669177/

Friday, December 21, 2012

IDLE NO MORE - SAN FRANCISCO

RALLY SOLIDARITY WITH CANADIAN FIRST NATIONS

https://www.facebook.com/events/374271672664448/

Friday, December 21, 2012

IDLE NO MORE - LOS ANGELES -

RALLY IN SOLIDARITY WITH CANADIAN FIRST NATIONS

http://www.facebook.com/events/349497715147942/

///////

Here are a few pics, one I found and the two from Weds. posted by Robert DesJarlait. They overflow my blog border but you can right-click to save them!

380027_525743317444256_1775335406_n.jpg 281202_10200139707277329_1344415347_n.jpg

37108_10200140052845968_5920830_n.jpg

Mordor Mayor Rybak makes moves to hide Minneapolis panopticon: Total Minneapolis Awareness Automatic License Plate Reader records form 'retroactive surveillance' empire

rybak-licenseplate-mordor-panopticon.jpg

"It is poor civic hygiene to install technologies that could someday facilitate a police state." ~ Cryptographer/security guy Bruce Schneier (src)

We all know the old motif - Feds staking out parking lots, reporting the license plates back to Hoover. Nowadays things are a little different - computers can trivially hoover up all the unique features like license plates and faces from video signals, 24/7. These are technical capabilities that Hitler and Stalin only dreamed of. The former National Security Agency employee William Binney described the system locking into place as a "turnkey totalitarian state" is arriving one system at a time. One of those turnkeys just turned up in Minneapolis.

The word is out now that more than 2 million license plate records have been obtained through a data request, since the surveillance material consists of mostly public record fields. Minneapolis developer Tony Webster (@webster) wrote up the info on what happened here - and quite correctly calls for the government to quit holding this kind of data for a number of serious reasons. See TonyWebster.com: Minneapolis Police release 2.1 million license plate records.

Rybak wants quick action on license plate data | StarTribune.com:

A day after the city released a database containing more than two million license plate scans, Mayor R.T. Rybak wants expedited state action to make the data non-public.

The Legislature is already expected to take action this session to reclassify license plate tracking data, which is derived from cameras mounted on local police squad cars across the state. But after complying with a request for Minneapolis' entire public database -- featuring dates, times and locations of all plates scanned in a 90 day period -- Rybak wants more immediate action.

He said the request was "already in the works" before Tuesday's data release, but "it does concern me." His request to temporarily reclassify the data would, if approved by the Commissioner of Administration, prevent the city from releasing the tracking data to members of the public.

See also latest on MPR: Lawmakers mull bill to regulate automatic license plate readers Minnesota Today. I think MPR is inaccurate as MPD said they'd shortened this to 90 days from the original year, as Strib indicated. (otherwise they would have violated MN Data Practices Act by failing to release earlier public records upon request)

Minneapolis' DFL Mayor RT Rybak (@mayorRTrybak) has sprung into action to demand the records generated by Minneapolis Police Department's Automated License Plate Reader (ALPR) system become classified as "private data", which means only the government, cops, various lawyers under different circumstances, etc, could trivially get ahold of incredibly detailed data & patterns about your vehicle's movements without a warrant.

Rybak's thoughtful plan is to make sure that no one else can get that data, only that bloated galaxy of whom John Young @ Cryptome.org calls the 'authoritatives' lording the new panopticon over us.

This is our window - our snapshot of the beta test - into the hellish future of total 'retroactive surveillance' awaiting us, when all our actions are constantly recorded to be 'played backwards' whenever some bureaucratic enforcer wants to increment his career through hassling us, demanding civil fines for infractions etc.

As recent posts on this site have documented, the Minnesota Department of Transportation (which just got a new chief) is spending state taxpayer money funnelled to military-industrial contractors in order to build a local version of a GPS tracking system called Intellidrive, which would transmit every damn move, including velocity, of every tagged car.

Additionally, exposure of abusive & immoral practices in the Drug Recognition Evaluator training program (& main BCA file) resulted not in a candid cleanup by law enforcement, but stonewalling. When individual law enforcement officers invariably abuse these massive data mining deployments, as some do, is there really adequate oversight let alone punishment for turning these 'necessary' technologies into avenues of abuse?

Plus of course, what are the implications of the chilling effects of these ALPR systems? What is the price paid by society when the chilling effect of avoiding ALPRs by staying put kicks in? How many people refuse to fly because of the intrusive & abusive security measures? And what happens when municipal cameras collect data even more granular and intrusive than the federal TSA?

For more on this stuff I recommend following @webster, and @RichNeumeister, a citizen activist on nearly all data & privacy matters at the Mn State Capitol. It seems like Webster triggered the Rybak blocking him on Twitter. Classy - especially since Webster posted in this recent context he's a lifelong DFL supporter.

To quote a bit from Rich Neumeister's blog which is VERY helpful for Minnesota issues: Two meetings: prescription records and license plate scans

Now to the Criminal Justice and Juvenile Information Policy Group meeting which was to make a decision about the collection and retention of millions of records of where you and I travel if we happen to be owners of cars collected secretly by the cops.

Per Eric Roper's Star Tribune Blog post  the Policy Group made up of Commissioners, judges, and others decided to make the license scan data private, but deleted the retention of 180 days for the data if there were no hits for law enforcement investigation.

Now I have to scratch my head on this one. By deleting the retention of 180 days, is the Policy Group saying with all intents and purposes, DO NOT KEEP OR COLLECT LICENSE SCANS ON INNOCENT AND LAW ABIDING PEOPLE, or are they saying the COPS CAN COLLECT ALL THE LICENSE SCAN DATA THEY WANT ON INNOCENT AND LAW ABIDING PEOPLE AND KEEP IT AS LONG AS THEY WANT.

I am perplexed.

& also earlier: Email to Minnesota Criminal Justice Policy Group on License Plate Cameras. For what it's worth Webster tweeted this afternoon (Tues Dec 13th) that the division of the state govt that implements/sets the rules, IPAD, has NOT yet received anything new from Minneapolis about ALPR data.

The reality is that politicians are not that responsible about these data issues. Instead you get ignored, blocked on Twitter etc. I am writing another post about yet another newly relevant old case - the Norm Coleman credit card database leak which I covered at Politics In Minnesota circa January 2009, eerily similar to the new charges against alternative journalist Barrett Brown. (Posting links to data like the Coleman leak is a form of journalism & research that feds are trying to redefine [unconstitutionally] as a felony! NOT GOOD). But that is definitely a whole 'nother story....

/////

MORE ON RETROACTIVE SURVEILLANCE LIKE MINNEAPOLIS POLICE DEPARTMENT ALPR SYSTEM: (not to be confused with the practice of retroactively legalizing the earlier illegal surveillance performed by telecoms during the Bush administration). 'Retroactive surveillance' is basically a timestamped panopticon.

Retroactive surveillance is a class of technology which can easily destroy certain dimensions of 'free will' and therefore should be considered extremely carefully as a keystone type of social control system. It's my personal opinion it will take at least a century for this type of tech to be possible to be used ethically (if ever), as the ethical structures do not currently exist – a major reason we are all descending into a kind of neo-feudal technocratic authoritarianism worldwide.

cryptogon.com » NYPD and Microsoft Team Up to Peddle Retroactive Surveillance System [WSJ] - same type of camera data inputs

NYPD, Microsoft Hope to Make a Mint off New Surveillance System - National - The Atlantic Wire

Coming soon: Ubiquitous surveillance from Big Brother's wayback machine (the archive.org wayback machine snapshots many websites over time, invaluable!)

NetworkWorld, 2011: Coming soon: Ubiquitous surveillance from Big Brother's wayback machine

cryptogon.com » New Video Surveillance System Tags, Tracks and Follows

a commenter puts it well at cryptogon.com » Coming Soon: Retroactive Surveillance on Anyone: "A present anxiety of future trouble from the unforgotten past; black to the future."

A change in tune: law enforcement now aggressively promoting retroactive surveillance capabilities of license plate readers | Privacy SOS

Is there any science (social science) of retroactive surveillance?

House Passes Surveillance Bill without Retroactive Immunity | TPMMuckraker

Drug war provides cover for retroactive surveillance without probable cause | Privacy SOS

.. That's all for now - this post is licensed Creative Commons remix/reuse with attribution to Dan Feidt/Hongpong.com non-commercially, including the "sheeple style" remix image I slapped together.

EXCLUSIVE MnDOT info cake: 2.97gb emails/docs on the Mileage Based User Fee (MBUF)- Minnesota's GPS vehicle taxing regime in the works

After a long wait, on Nov 28 2012, the Minnesota Department of Transportation (MnDOT) released ~2.97 gigabytes of data from inside the development of a GPS-based vehicle tracking system intended to introduce a vehicle tax - which would entail a great deal of data constantly collected by the government on the whereabouts and everyday patterns of the taxed vehicles. The source URL posted yesterday is ftp://ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/ .

My friend Nathan Hansen made the request, pursuing a long-running story of the buildout of these taxation-tracking highway techs. (Disclosure: I did some design work for Hansen previously) The 2008 story I did: Now Searchable: The MnDOT NASCO NAFTA Superhighway Document Stash && Index of /June 2008 MN DOT Request/NASCO - Hansen Request && Index of /June 2008 MN DOT Request/June 2008 Request && Index of /DOT. A lot of these plans fell by the wayside - and a special Minnesota Intellidrive project and MBUF is the new plan. Related: Melissa Hill's new blog allows you to "Track the Police" using public data && Private company hoarding license-plate data on US drivers. In May 2011 I did this story: Contracts for IntelliDrive MnDOT Military-Industrial/U of M plan to GPS-track all cars. This data dump continues the story.

There are a few important angles: comprehensive vehicle tracking data would be great for law enforcement, lawyers and big corporations to investigate everything in one's life, including 'retroactive surveillance' of previous activities. However, the "fees" that would be imposed on rural Minnesotans who have to drive around a lot would be quite burdensome.

From a quick look at the PDFs we find internal discussion points about such impending scams as 'carbon credit' trading (a greenwashing Goldman Sachs sponsored futures bubble, as Matt Taibbi reported). Additionally Raytheon and SAIC have both been involved in this "Intellidrive" national-scale super-project. Also, just because the user data is processed behind Battelle's firewall in no way signifies any level of security of personal information.

The main block of data posted is in huge Acrobat Reader X sized PDF files (1.1 and 1.6GB) . We have mirrored around the files and checked with md5hash in case the govt pulls any later. Acrobat Reader X is kinda bogging on these giant files -- it loads all the emails in a slow email reader-like interface). Plenty of items like "concept of operations" or "MBUF CONOPS" is in there, a lot of stuff about consultants. We are just starting to peer at it, but Adobe is difficult to work with (a svelte 400MB app yay).

To get this batch of files yourself, if you have UNIX wget for mirroring:

$ wget -mb ftp://ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/

I definitely recommend installing wget for things like this, where the files are listed in a directory for quick scraping.

//////////////

DATA EXTRACTION BONUS CHALLENGE: To open the attachments on these emails, for OSX you have to use a program such as the free MailRaider: Download MailRaider for Mac - Read Outlook .msg files on your Mac. This is what you gotta do - in Acrobat, hit the paperclip on the side:

acrobatreader.png

After first picking out the individual PDF attachments in Acrobat (the paperclip icon) you can get it to open in MailRaider. Hit the 'Open' button in that side panel. Hopefully this will launch MailRaider. In MailRaider, flip open the sidebar you can get it to work like so:

mailraider.png

Here is the first PDF I was able to extract - Intell~1.pdf (2MB) - it is a "business sensitive" presentation by military-industrial contractor Battelle to MnDOT. Let's have some choice excerpts including particularly how they use taxing people driving around rural-ish places like Wright County as a target for the mileage tax.

mndotcake000.png mndotcake001.png mndotcake002.png mndotcake003.png mndotcake004.png mndotcake005.png mndotcake006.png mndotcake007.png mndotcake008.png mndotcake009.png mndotcake010.png mndotcake011.png mndotcake012.png mndotcake013.png mndotcake014.png mndotcake015.png mndotcake016.png mndotcake017.png mndotcake018.png mndotcake019.png mndotcake020.png

What could possibly go wrong?!

mndotcake021.png

It is always sad to see fine open source techs like GnuPG used to encrypt tracking data. Damn you Technocratic Capitalism!

mndotcake022.png mndotcake023.png

This is pretty alarming. Sterns, Wright, etc are counties full of peopl that can't afford to pay more.

mndotcake025.png mndotcake026.png

LOOKS LEGIT:

mndotcake027.png mndotcake028.png

So this is just one extracted PDF from a single email. If Battelle was actually a front for malicious space aliens who want all the inhabitants of this planet tagged and tracked, I would not be surprised!

///////////////

MIRROR ADDRESSES: Here is the first mirror of it. These files are big enough to crash your browser - maybe rightclick & Save As link so the PDF plugin doesn't keel over... I don't think we'll need tons of mirrors for this, but it's good to have a couple around.

the big ones are at:

http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun... & also:

http://hongpong.com/files/mndotcake/Public%20QAM.pdf
http://hongpong.com/files/mndotcake/Public%20CommVault.pdf

dfc0fd1d4d6bdbcaf0498a50ee0f5fec Public CommVault.pdf 1.22 GB on disk (1,216,990,533 bytes)

cec386cc20000b7fe10297fc3ca0cdab Public QAM.pdf 1.7 GB on disk (1,698,431,132 bytes)

If you find gems tweet em with hashtag #mndotcake. If you find an open source way to work with files this big let us know. It will take some people to work on this. We invite people to occupythecomms.cc group infocake for looking at PDFs - this has group writing pads available (very easy, much like googledocs). Info on occupythecomms: https://occupythecomms.cc/pages/view/90009/activism-and-collaborative-media-methods

On the indymedia mirror the directoryIndex isn't cooperating yet (no folders list) but the files are here. The big ones are in bold, not too much in the others so far found.

You can generate a list of your wget mirror like this with:

$ find -name \*

http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/Public%20QAM.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/Public%20CommVault.pdf

http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes16.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes27.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes26.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes3.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes9.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes13.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes8.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes29.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes10.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes5.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes11.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes12.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes19.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_phone%20for%2027th%20and%2028th....and%20a%20TIP!%20_).pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes17.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes22.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes6.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/6_5_07%20Commissioner's%20Staff%20Meeting%20Minutes.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/RE_%20Dieringer%20Pre-Award---IMPORTANT!!!!.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes15.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/RE_%20Dieringer%20Pre-Award---IMPORTANT!!!!3.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Ray's%20requests.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_RE_%20Dieringer%20Pre-Award---IMPORTANT!!!!2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes30.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes28.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_Re_%20MNDOT_MBUF%20Discussion%20guide%20v2.DOC%20(Lucy's%20out%20of%20the%20office%20).pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes18.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Attachments/r_6%205%2007%20Commissioner's%20Staff%20Meeting%20Minutes.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes20.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_This%20should%20do%20it!.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes%20-%20No%20major%20issues%20FYI.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes25.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes7.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_This%20should%20do%20it!2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_RE_%20Help_!_.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes14.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_headin'%20home%20with%20MBUF%20as%20my%20bedmate....pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes24.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/r_Selection%20Committee%20%20(Just%20In%20Case)%20.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...).pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes21.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes4.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes23.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/6_5_07%20Commissioner's%20Staff%20Meeting%20Minutes2.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/QAM%20Redactions/Fwd_%206_5_07%20Commissioner's%20Staff%20Meeting%20Minutes31.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RECEIVED!!%20%20_)%20%20%20%20MBUF%20Presentation%20Draft_11_16_2009_415pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_09_2011_128pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_09_2011_136pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_09_2011_133pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_08_2011_1141am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20CONSULTANT%20CONTRACTs_last%20night!_12_02_2009_1127am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20Temp%20classification%20is%20here!_02_08_2011_1130am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20CONSULTANT%20CONTRACTs_last%20night!_12_02_2009_1132am.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outbound/chiefcounsel/Nate%20Hansen%20Email/CommVault%20Redactions/RE_%20News%20from%20Mileage%20Based%20User%20Fee%20Alliance%20(MBUFA)_04_11_2011_309pm.pdf
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...
http://tc.indymedia.org/files/mndotcake/ftp2.dot.state.mn.us/pub/outboun...

/////////////////

Here is the MD5 hashes for all these files. (for fingerprinting/verification of file uniqueness, accept no substitutes). There are a bunch of apparently empty emails in "redactions" directories - or going to try another PDF reader to see if something is hiding.

a1541603442a1f0a6c2c7487c947e35b Hansen, Nathan 4_20_2011.xlsx

dfc0fd1d4d6bdbcaf0498a50ee0f5fec Public CommVault.pdf 1.22 GB on disk (1,216,990,533 bytes)

cec386cc20000b7fe10297fc3ca0cdab Public QAM.pdf 1.7 GB on disk (1,698,431,132 bytes)

$ cd QAM\ Redactions/

$ md5sum *

2bd53b4d4cfdf5735c6acb3d78dcac68 6_5_07 Commissioner's Staff Meeting Minutes.pdf

ac02fb8d2d000af38df63e9d6804a5bd 6_5_07 Commissioner's Staff Meeting Minutes2.pdf

bb562e176106b9436968ec57312fd74c Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes - No major issues FYI.pdf

cbbb2e9d9d81892a865d6539216d768c Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes.pdf

5294e1ef211a8a2de42749ab525b53ff Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes10.pdf

dba29ffb9fc67b3a389dbfc7e67ea8f7 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes11.pdf

e77272f7a0b33506dbf7e284f553bc58 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes12.pdf

8b0f53991f8b62fc2d1c92407839a4cc Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes13.pdf

a6b449f524250717b8fcdbac45abe537 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes14.pdf

c0b806598d33db35b25a167558e61dca Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes15.pdf

3243ea3f27b71c5da5d8aa146033fd45 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes16.pdf

091a17b9fd52dcb52f8ee9f2e1087426 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes17.pdf

61f4122e7d61e84099bcd39479c389a0 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes18.pdf

f8537cda72dc63a7dd3e6fd5bdf96f80 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes19.pdf

1dc010c5ff89962ae132c242d99cdd4e Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes2.pdf

d005b7b9edf6acf4046e57f0f157b098 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes20.pdf

0b9c231b2a572b29bc0b26e533b49416 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes21.pdf

9234a884059b1667134a3a60438da49d Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes22.pdf

16095da57ce2c90ab73ea3acb470231a Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes23.pdf

e834fc715abed962a5926db379b7d47b Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes24.pdf

44bc416f5ed69a62dbc3284bddf45be4 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes25.pdf

93db674814645af1a9b2e3b86e0cedbb Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes26.pdf

7dfb0294d4e9916117d48f87399396b4 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes27.pdf

0d1e549ec6911fb272c273cc9cdb85d2 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes28.pdf

af0b4c77b40a92f007f6de0937689666 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes29.pdf

14ad0e9eaf2a1ec784a7f64a4677d1fd Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes3.pdf

eb3c3a2ab081cd011cb8dc3cc4220c17 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes30.pdf

babb6166d521b7bd5e3da38e549101b9 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes31.pdf

faa33837481a7ea9ce5389301005d276 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes4.pdf

ec283884cf4eb57c1902f554c6daf88a Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes5.pdf

fd3955363a06c5e4f073b9a0eb685dce Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes6.pdf

9bb8bb439de8ebd31245d9e5c8039ba1 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes7.pdf

7e8d8bf30cb1979c98d26b68f74b4354 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes8.pdf

5e691539c7ab6721cd39e1739a63c977 Fwd_ 6_5_07 Commissioner's Staff Meeting Minutes9.pdf

eaf5422b97c8ada9bc1a2e2eebfef0bf Fwd_ MNDOT_DOCS-#573688-v3-MBUF_EXEC_SUMM.DOC.pdf

17f5832daf02053ece137906874516a2 Fwd_ Re_ CANCELED TONIGHT.pdf

4324e83ef735d5e77d99dfd22044224f Fwd_ Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al.pdf

3b7488cce7ecd2166663f08279cfc3dd Fwd_ Russian exchange program.pdf

fdd5552a9a0a29ea87998d4836e80e96 RE_ Dieringer Pre-Award---IMPORTANT!!!!.pdf

d0658a06b65516fca4053fc9b36ecb8c RE_ Dieringer Pre-Award---IMPORTANT!!!!3.pdf

0dbcad4857d9b6403a2e853cd78c6972 RE_ Dieringer Pre-Award.pdf

a1d456e7e7b594fe400f3848aa11e98c RE_ Dieringer Pre-Award3.pdf

6fd5adfd694451487ccdf26373eeab55 Ray's requests.pdf

39468301435c56e3ec93fc588c92819a Re_ Fwd_ Fox 9 follow up.pdf

58e487d24be75a7d253941dde63b08fc Re_ Fwd_ UPA.pdf

f01b3471912eedfdba901c0c593de83a Re_ Fwd_ UPA2.pdf

d3b3a8c4347947539ca68b1e9c1d6e51 Re_ MBUF_ Invoice Questions.pdf

b063347fb895a472d4dbfd830646ddad r_Final payment on MBUF.pdf

d215cb89c3fd54140daf25b9ef8284ce r_MBUF Session at Research Conference.pdf

5b355449e4377a26817cd4c6811596bf r_MBUF_EXEC_SUMM.DOC.pdf

62531bda63cf387a9af54c603c485f05 r_MNDOT_DOCS-#573688-v3-MBUF_EXEC_SUMM.DOC.pdf

9d58ff05a42d717ab21fb16b025ae57a r_One-pager on MBUF.pdf

00498befc398512b83fd12a504885117 r_RE_ Couple quick thoughts for the morning....pdf

f7f56814799552a8c7623a05651abf6a r_RE_ Dieringer Pre-Award---IMPORTANT!!!!2.pdf

21f3cd6184330313fd4c968a7f028cbd r_RE_ Dieringer Pre-Award2.pdf

44b00634488d6c0a4047f001d0458fe0 r_RE_ EGADS___.pdf

ab4a3171454d293faf05282fd2d83eec r_RE_ Help_!_.pdf

0fd3fb1e29875e32749ea7c14c04c3f4 r_RE_ RE_ MBUF 3 Informational Materials.doc.pdf

326fc5ab634d7bfedb4c1bb5f301f2c0 r_RE_ Revised Proposal.pdf

4653657972f849fd9a1c7054079d000c r_RE_ Weighting issue_ new thought_.pdf

c61c3d6a1ef1be417f9d00c7be8b77cb r_RE_ dang, did it again.....pdf

91179ab7d3629f5762bd8e18ab4afca5 r_RE_ tomorrow_ or... in the meantime....pdf

08d3bea45066ef0c5d509828947797d8 r_RFI Responses.pdf

e507c028247157bf0860a7ed793f429a r_RFI Responses2.pdf

9cb9fe08acb375b3ddfbedfb27c640fe r_RFI Responses3.pdf

3d9ee0668e57b78f837885a77e7afe80 r_Re_ WANT INPUT FROM RW_KM- Re_ Notes from the second pretest.pdf

477daab48437d06bbc3d48763f849c09 r_Re_ Any MBUF updates_.pdf

5db8f9421c5edf2810be6964febc0d4c r_Re_ Budget review.pdf

4606fdd159fd22f59b610edfddd6e8ca r_Re_ Checking in.....pdf

51f6f0c7e5b327a6378b96dc2d0ba936 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al.pdf

4ab4226505ba43336ca2ddfb864de016 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al2.pdf

c980c15aa1358178a1766ce97f04f090 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al3.pdf

37258df0b414af50f8c64d51e0bcf500 r_Re_ Contract 93707.pdf

63c77560c995c1f95af81637e25a0cbf r_Re_ Div. Directors.pdf

fb76beed27f4086fc713c6d6bc59159c r_Re_ Final payment on MBUF.pdf

0c045b993642661cfc57e47d2998f539 r_Re_ Focus Groups_ MBUF.pdf

13369f6c2c7d1f15947be9f5451ecf3e r_Re_ MBUF FAQ.pdf

c0f66f0d95a6bb505dfe5a152f4a6d04 r_Re_ MBUF FAQ2.pdf

6768b6bb46892736ca405151827dc3e1 r_Re_ MBUF FAQ3.pdf

5548eb744fdefe5edc438d777aee0e7b r_Re_ MBUF Posting.pdf

f452cc41fb449ac5a532fe69e36f9aae r_Re_ MBUF TRB Paper.pdf

fdc671465cca77c1ac28c624c66eec60 r_Re_ MBUF TRB Paper2.pdf

15fdbfc26e9c1d7d1d75bebf19bd3d4b r_Re_ MBUF TRB Paper3.pdf

f9064a7d54b55dbdfee12201f5a6d6fb r_Re_ MBUF TRB Paper4.pdf

1ea6c324c4810a187fbb466f090e9dc8 r_Re_ MBUF TRB Paper5.pdf

ee2bf6d95d1dde47efad543d7fcd72f7 r_Re_ MNDOT_MBUF Discussion guide v2.DOC (Lucy's out of the office ).pdf

908d43977c57905893b1876c3743680b r_Re_ MNDOT_MBUF Discussion guide v2.DOC.pdf

c953af1a4399e1c7186b760163d22cf4 r_Re_ PAYD Market Research.pdf

2c3ff87a050058633837b932e27ffdf3 r_Re_ Presentation of MBUF Public Perceptions Study.pdf

ab603f4bed9c05693a38a2fbbbfab8dd r_Re_ RFP Questions - 3.pdf

971fa164a5f7b261c89828bf7abc9396 r_Re_ What time do you think you will go to lunch__.pdf

1322615f623d2ad114f056d96ac22800 r_Re_ What time do you think you will go to lunch__2.pdf

2e4cac2496e0ae647c75c03336ea1365 r_Re_ What time do you think you will go to lunch__3.pdf

d1cc38d07c46de1d9603c9d0e34c9e46 r_Re_ checking on your status.pdf

b0ee689930c73f8f899ef89dc65996b0 r_Re_ project status.pdf

d98803d63a7121d7475fa402037bde55 r_Re_ project status2.pdf

75339d3c33fa450cde6aeb9f61d4cf46 r_Revised Proposal.pdf

2b719b5df5c7e94cb4c254a923a77029 r_Selection Committee (Just In Case) .pdf

9b858373c2c295719101426381877004 r_This should do it!.pdf

3e0a41234df919fc5748fb0f3733f5a0 r_This should do it!2.pdf

3c0202bf34f06fca292a363ded23d808 r_Travel Authorization Signatures.pdf

4ff5b016ecab1a8194ba82d1f3166166 r_What time do you think you will go to lunch__4.pdf

f9b137390f0e4be87d0eacc412e55cbf r_headin' home with MBUF as my bedmate....pdf

74da3639cfd3c5cad57a802cfb571df6 r_last Friday....pdf

8a720e445fbd86bae91c273b7ee94bec r_meeting today.pdf

01517f469063f9f88b231abbf3c60fe0 r_phone for 27th and 28th....and a TIP! _).pdf

1893859cb7ef79f3e8edeaa57e6d40bc r_to hear the second pretest interviews_.pdf

ec21dda39b263e35e15ffa1a7106e3d7 r_up and taking nourishment _).pdf

$ cd ../CommVault\ Redactions/

$ md5sum *

4526805e569ac612e8b47e0baa0f18c5 Bernie Lieder Update_04_12_2011_316pm.pdf

965a35632c7ee3c5b4a77953c819b6e7 Email address_04_19_2011_152pm.pdf

ea00a30ddde74758dfb632444ee17554 FW_ MBUF Online Community_02_14_2011_122pm.pdf

c30785e48c44ab468535c835ea8808ca FW_ MBUF Symposium & PAYD Insurance_03_23_2010_1002am.pdf

ae3f69040f670c509ed143bf937abeb6 FW_ MBUF_12_10_2010_1006am.pdf

1f217b45f730ab22fa987aec48ec1797 FW_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1143am.pdf

6c04c8b976f6c6615aaf1f3e553eef4a FW_ Mn_DOT MBUF RFP_08_10_2010_1032pm.pdf

be0486bbafba485cf73e797cf57cce1d FW_ TRB_01_06_2011_1148am.pdf

5dd29c7fdc005ea0d1872b7b50db4f9c FW_ Temp classification Ready for your review_11_17_2010_330pm.pdf

da1c6529e24b3aeb622e465810d2493d FW_ Terminology for legislation_12_02_2010_832am.pdf

60526ffba0b83ed3ca2de4b1d0ee4d93 FW_ US-2 Alternative Risk Analysis_12_02_2009_126pm.pdf

356efd4378b9f723631510c6da3ab9ec FW_ my schedule_06_02_2010_339pm.pdf

8134913b6cb4291df781450444fad923 Fw_ MBUF project name_03_18_2011_405pm.pdf

4806c46d5527908e4f5d6d69ecc3fb9e Fw_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_358pm.pdf

03a2a1ca03c16fb5b1cbec671111a729 Fw_ TRB_01_06_2011_937am.pdf

14db70ba2b1af71c30c850b9a6470dd5 Hansen, Nathan 4_20_2011.xlsx

abb315692a9475591a3f3ebebb2ca0df I-394_05_20_2010_848am.pdf

484c3fad46b8460e8cc8e024d44b2eda Letter to Administration and IPAD_02_21_2011_221PM.pdf

30f936b3baf79c8a3f4adf0c37b9cd17 MBUF Exec Summ in one pager template.docx_02_24_2010_139pm.pdf

54447e231cc5e7d1d12d52cfcb2cb51e MBUF Online Community_02_11_2011_1223pm.pdf

8144d33f994c47817ec2ea44e06ec98a MBUF Project_02_08_2011_143pm.pdf

b27c2fdf06cd476d21c4e66b772d3fb1 MBUF_10_22_2010_839am.pdf

be348e1362ac6ccece5756bcf754d3f1 MBUF_11_30_2009_1013am.pdf

c4b6a0285baa57dfd06cc49e19228773 Mbuf name_02_23_2011_1141am.pdf

274c29d8c6e94608478aa42efaad281e MnDOT & Communispace weekly call agenda_02_25_2011_919am1.pdf

71d3478d4d6332dc22e6c575ef2e0512 MnDOT & Communispace weekly call agenda_02_25_2011_919am2.pdf

39d76453ecd31324635d95e3891e9d13 MnDOT Snapshot - Reaching Older Generations_02_22_2011_943am.pdf

671fe8c19a2f81667a52fe78075655b1 MnDOT Snapshot - Reaching Older Generations_02_22_2011_944am.pdf

b135755acaa77b327ddd2f8339179b0c RECEIVED!! _) MBUF Presentation Draft_11_16_2009_415pm.pdf

886befdaa2332b043dc63e9800f8f6f6 RE_ CONSULTANT CONTRACT EXPIRATION ALERT_12_01_2009_1035am.pdf

d63301b6ab7408fd335ecd01c22bfba9 RE_ CONSULTANT CONTRACT EXPIRATION ALERT_12_01_2009_1059am.pdf

c3c35a0da620de7e9fabf3e281b33cd1 RE_ CONSULTANT CONTRACTs_last night!_12_02_2009_1127am.pdf

66c4c8e5721a887186ef32c29e24ff93 RE_ CONSULTANT CONTRACTs_last night!_12_02_2009_1132am.pdf

78d6d6ef56ecfc67fcaf61e5a332127a RE_ I-394_05_20_2010_902am.pdf

05df7eaf8b317c80f13820f1e1cee14b RE_ IntelliDrive MBUF Project_12_16_2009_333pm.pdf

2b7f16e797a7a0c6ad62c7ed1333b8f5 RE_ IntelliDrive MBUF Project_12_16_2009_810am.pdf

9a0cec08313abcf1c9ca70c658f80e14 RE_ Letter to Administration and IPAD_02_22_2011_927AM.pdf

e30e6e048ba92ef1a599a2600bd6498f RE_ MBUF Exec Summ in one pager template.docx_02_24_2010_154pm.pdf

70c7b32debe5a55e2f8f2d67bebb76b8 RE_ MBUF Focus Group_01_17_2011_511pm.pdf

50e47e4450bab89d5500f5eb35a036a4 RE_ MBUF Online Community_02_11_2011_1225pm.pdf

92fcfc9630992a333dc3b46bd48732c4 RE_ MBUF Online Community_02_11_2011_1231pm.pdf

f027c45acab6e57b1d36e24d0ee93772 RE_ MBUF Online Community_02_15_2011_1100am.pdf

a1b6ce5cde68ea77a9c23c95ea8dcb9a RE_ MBUF Online Community_02_15_2011_1129am.pdf

deb5838863a641688c6e7c85ece7b5db RE_ MBUF Policy Kick-Off Meeting_12_01_2010_1236pm.pdf

7899b2e46e7bbc1d7d3dab6b67204ef8 RE_ MBUF Policy Study Draft Online Survey Approach_02_03_2011_1206pm.pdf

04a3bd71953c8a3116c6d5302d71b583 RE_ MBUF news release going out today_04_18_2011_419pm.pdf

0f97d747bd627273951ae52d9f47af52 RE_ MBUF news release going out today_04_18_2011_506pm.pdf

5d7c9d7b938d012327ad74e8adc1c6ef RE_ MBUF news release going out today_04_18_2011_603pm.pdf

1108a01bc5647242129db848b1968ad0 RE_ MBUF project name_03_18_2011_424pm.pdf

9d04bdc4f3d47bd9aa6a42cc86e8111c RE_ MBUF project name_03_18_2011_425pm.pdf

e1b29a363a67381a2bf62b520b81c54b RE_ MBUFF meeting today; cancelling_04_15_2011_215pm.pdf

2b62cff8e2356af2367a533757fecd3c RE_ MBUFF meeting today; cancelling_04_18_2011_830am.pdf

8c6f28f8bfad5e6269be821d90a38ef3 RE_ MBUF_11_30_2009_1149am.pdf

e44110f22e541bd4e66165e507305409 RE_ MBUF_12_10_2010_1103am.pdf

999925ec95ed3a13e110e798bf1555c1 RE_ MBUF_12_10_2010_1111am.pdf

27a82743582cefc14bb61353f8551a06 RE_ MBUF_12_10_2010_950am.pdf

27956fe15cf55ca0c7f0287b03148ea6 RE_ MBUF_12_10_2010_953am.pdf

81af256a23a3809ff8bb8d622b70d4a0 RE_ MBUF_12_10_2010_954am.pdf

3e13a81758d56493a83f5c7428ed370b RE_ MBUF_12_10_2010_955am.pdf

19d4fb79563af9ee4d8fdd44b9ee2508 RE_ MBUF_12_10_2010_957am.pdf

f9f6f496419b156db9f74f4f7683f83b RE_ MNDOT & Communispace weekly call - 2_15_02_17_2011_236pm.pdf

5b8361f64e68eab5c8a8342fbcfda50d RE_ Mbuf name_02_23_2011_1144am.pdf

006f09322d12e50fb6f0f819bea23fbe RE_ Media contact-mileage based user fee_04_19_2011_319pm.pdf

f1ee5606964818951a6c908260505a4a RE_ MnDOT & Communispace weekly call agenda - NOTES_02_28_2011_957am1.pdf

cb9614632da4c99f2b63cab39767a502 RE_ MnDOT & Communispace weekly call agenda - NOTES_02_28_2011_957am2.pdf

dc0c94c5bda4f38f9b50e5bbee1adeb1 RE_ MnDOT Snapshot - Reaching Older Generations_02_22_2011_504pm.pdf

4700a7736adc778ff83d49f14c6ab184 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1153am.pdf

7ab57aca29541ad59aa8cb4aa735396d RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_12483.pdf

e8021d8f7e3afdd8629541fd1a9b0cc3 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1248pm.pdf

fa54ec8e94bf5fb5cdbe3fa6e1c4db9f RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_1248pm2.pdf

3218af37335c0e06c3f3b9a011b19e39 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_328pm.pdf

eb696b4ffeee4e306e2eb7e484bba2d6 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_331pm.pdf

2dd4f45c1331c9db6bc6ad13cad669e7 RE_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_331pm2.pdf

6dcab9c1d50ee4793d1c2f50ac5c1aac RE_ Mn_DOT MBUF RFP_08_11_2010_1031am.pdf

8d4ac4b9986a2dee1ebdf640cc241aa4 RE_ News from Mileage Based User Fee Alliance (MBUFA)_04_11_2011_309pm.pdf

e210a430bee280107a58c426d63a4bdd RE_ Next steps_Action Planning_12_03_2009_124pm.pdf

dd51eb0f42aea93f113ff5753b23f7f5 RE_ TRB Presentation_01_28_2011_125pm.pdf

4dc9010d0d7df27e8d5dd8689beebd0b RE_ TRB Presentation_01_28_2011_133pm.pdf

f910d3770ae1253cb5a096f9fc89be26 RE_ TRB_01_05_2011_543pm.pdf

3559e8bf7034bd767690c270c54aa1d8 RE_ TRB_01_06_2011_1111am.pdf

be8de9d4e1d3f82ab1a7567cbbbd0db2 RE_ TRB_01_06_2011_1116am.pdf

276086ae4495d14e7cbb077238747743 RE_ TRB_01_06_2011_1136am.pdf

de5827e592a282eea1853abaf717bc0d RE_ TRB_01_07_2011_840am.pdf

1e20ee8d269538d3c51f1e4a394813a9 RE_ TRB_01_07_2011_848am.pdf

29bbb01ead3b247be765ae31ccc4af0b RE_ TRB_01_24_2011_450pm.pdf

b44878a8ba14e90d657e411ad8d6f3f8 RE_ TRB_01_26_2011_620am.pdf

0c08f27a10d2e6df4d0562d7a6f1c0ff RE_ TRB_01_26_2011_801am.pdf

76495b1ee7bf01d8cd82d00f844a3df4 RE_ Temp class_02_17_2011_412pm.pdf

2f0318acfd3b1dcb960d5ea3a58a3264 RE_ Temp classification Ready for your review_11_17_2010_636pm.pdf

920a5c9704de481feb63d517712c1bbc RE_ Temp classification Ready for your review_11_18_2010_1105am.pdf

91d9a6e0ecaccd8038d737fb9e018548 RE_ Temp classification is here!_02_08_2011_1130am.pdf

f00a78733245cdb151b70161e8b0c6c6 RE_ Temp classification is here!_02_08_2011_1141am.pdf

88084dd4767ce27fb1c98cab13fe86c8 RE_ Temp classification is here!_02_09_2011_128pm.pdf

325966f645ec703d7da2d357249d6678 RE_ Temp classification is here!_02_09_2011_133pm.pdf

5c900f9cadf4e5037c0cd14da33e283c RE_ Temp classification is here!_02_09_2011_136pm.pdf

eb559b717547c18aa1ce5de7f4a334fb RE_ This AM_06_11_2010_934am.pdf

1d52160c492897b3bca16ee9df7ffa8b RE_ VM yesterday_12_05_2009_1131am.pdf

6be20bbfc07fe87eaecab816bc64e9dc RE_ another version of the policy study overview_01_07_2011_835am.pdf

3eebed34ca6fdfd6224366da55a0364e RE_ another version of the policy study overview_01_07_2011_932am.pdf

221e425208d0c9dea2da17e21cedaf78 Re_ 2010 MBUF Symposium Call March 12, 3 p.m. Central time_02_27_2010_1006am.pdf

4a7ad39b42e8063a51090e4dfc4c9ac3 Re_ Jon H.2_01_05_2011_759am.pdf

bf84169642681c0393244cbdb2661a3e Re_ Jon H._01_05_2011_838am.pdfbf84169642681c0393244cbdb2661a3e Re_ Jon H._01_05_2011_838am.pdf

ec3787db74d4c1110113c0b45f0a355e Re_ Letter to Administration and IPAD_02_22_2011_155PM.pdf

7cb7973b2280ba2688b13512ebcb7625 Re_ MBUF Policy Meeting_03_02_2011_215pm.pdf

739ed2f8cadb31733edb0fdfd97f04e7 Re_ MBUF_03_31_2011_714pm.pdf

5cabfd708b4c7a48068bcb609c853d79 Re_ MBUF_03_31_2011_824pm.pdf

4ee94529b2e9ec85f9f64693e0dff2cf Re_ MBUF_12_09_2010_911pm.pdf

2ea238fe33918e7b7eebc5ac7ec96c1e Re_ MBUF_12_10_2010_1047am.pdf

5baa528dfaecef9cd4ed408f2d94a650 Re_ MBUF_12_13_2010_746am.pdf

f7adb768801ba9af6150f1cbc9053a97 Re_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_155pm.pdf

8bc02ad9e7444b670486bc1fc4f1fb2c Re_ MnDOT Snapshot - Reaching Older Generations_02_23_2011_323pm.pdf

36fdd9e21207b2267c0d13fbb8baad70 Re_ TRB_01_25_2011_148pm.pdf

7c3a94657f2afb64691f52ede7db19cb Shortened Presentation draft_11_18_2009_104pm.pdf

e82b4a99ead5133167d892c292950a64 Temp classification citations and final Attachment _11_18_2010_146pm.pdf

e3a1eb76c041f03400532d26a93c01b7 Temp classification_11_09_2010_420pm.pdf

f35b892dcd07cae5ef763765ec8e8989 VM yesterday_12_05_2009_718am.pdf

ad284dd91760b55caa43d94947bcb309 my notes from focus group_07_15_2010_1042pm.pdf

5ec009dc1d2b30fd7180043d71e431d2 my schedule_06_01_2010_306pm.pdf

df2c566cec38e930b2fc0b89c5467048 note changes per my vm on your cell...._07_22_2010_1142am.pdf

adcbf8b475c7158e8800c223e06b1783 r_VPPP Grant Apps_02_03_2011_905am.pdf

2bc792828e021379bd6508c0a8e5e808 your 3905 and 3924_ classifying data_12_21_2010_403pm.pdf

$ cd ../QAM\ Redactions/Attachments/

$ md5sum *

3fd8f0f9226e7b23383fb4e9820800ef r_0584_001.pdf

5fe5e205e8c9673a577d2acb389fbbd7 r_09xxx Dieringer 2009 FHR Cost Detail.pdf

8b56f9fb39fa8b7a6d58e2b2da23776c r_09xxx Dieringer 2009 FHR Cost Detail_for revi.pdf

e22812037eada83aecf6311eb08a7b4a r_1.30.07 Commissioners Staff Meeting Minutes.pdf

f713229f7f300f227589bd89aaad2002 r_2.06.07 Commissioners Staff Meeting Minutes.pdf

f3375414fc619ee175b5dc224a5e07a1 r_2.13.07 Commissioners Staff Meeting Minutes.pdf

22f6f34e84981638ffa263c1f5a434fd r_6 5 07 Commissioner's Staff Meeting Minutes.pdf

52a28aea5fffa90a906a41dd04d6ea5c r_Addresses_2009.pdf

8c31824d4de7622ffcffaf8d4a44fcd4 r_Fwd_ Re_ CANCELED TONIGHT.pdf

d52b1e9786833b3d758a0e642afd0507 r_Grants-dot-gov-20070522131848652_1.pdf

cf02b8b051229580d130fadce52e7a67 r_MNDOT_DOCS-#573688-v3-MBUF_EXEC_SUMM.DOC.pdf

0298e9beac45b9d02e9c3c5f3e4fae96 r_Re_ Contract 90815 with The Dieringer Research Group; Mileage Based User Fee et al.pdf

///////////////////

More on this as stuff develops. Happy tracker hunting!

A few more elements on the semi-suspended MN Drug Recognition Evaluator (DRE) program

Previously on hongpong.com: MK Occupy Minnesota: The Drug Recognition Evaluator BCA Investigation files (Nov 12 2012) -- MK Occupy Minnesota (May 3 2012)

The training section of Minnesota's Drug Recognition Evaluator program continues to be suspended, after a 513-page Bureau of Criminal Apprehension investigation raised more questions and stonewalling from officials. Whether or not anyone will 'get real' about intrinsically corrupt war on drugs and protected misconduct is another question. Whether or not anyone will admit the war on drugs funnels profits into Wall Street is yet another.

Fox 9 reporter Tom Lyden covered the DRE story (VIDEO), talking to one of the test subjects as well as my friend, attorney Nathan Hansen, who is planning to file a lawsuit. (I have done a little design work for Hansen in years past)

The role of the Minneapolis Police Department in DRE remains untouched by local officials. 3 months ago I interviewed the chair of the city public safety committee, council member Don Samuels (VIDEO) about the shutdown of civilian oversight in the city, and he said that there was no expected report from MPD about the DRE.

Other typical recent misconduct: MPD Officer Blayne Lehner named in misconduct lawsuit; Mpls settles for $85k - City Pages Blotter

CityPages has covered DRE from the beginning and has posted a series on it: DRE 'victims' to file civil lawsuit against alleged pot-distributing officers [SECOND IN SERIES] - Minneapolis - News - The Blotter

Here are a few more new DRE documents a research colleague found from elsewhere on the interwebs:

http://www.decp.org/documents/pdfs/WhatNew/Labor%20Day%20Period%20Totals%2020102.pdf - typical touting of arrests. Crossposted to Scribd: DRE Labor Day Period Totals 20102

Via Washington state, the 2010 version of the official DRE manual (it has the same distinct typeface as the DRE IACP certification form in the BCA document) : http://www.wsp.wa.gov/breathtest/docs/webdms/DRE_Forms/Manuals/dre7/Student%20Manual%20-%20January%202010%20-%20Part%201.pdf - rejected by Scribd because of password protection. Mirrored at http://hongpong.com/files/dre/DREStudentManual-January2010-Part1.pdf  - 4MB - 212 pgs. Again it is important to note this material emerges from a committee of the decidedly sketchy International Association of Chiefs of Police, not a scientific body with open peer review. Good stuff about licking toads on page 187 etc etc.

Minnesota - the 1997 DRE plan: http://archive.leg.state.mn.us/docs/pre2003/mandated/970234.pdf - crossposted to Scribd: DRE-MN-POST-1997-970234

Another DRE document from Littleton CO indicates state & federal funding: http://townoflittleton.org/images/TOLimgs/files/septpdactivities2012.pdf -

A password-protected Powerpoint. Anyone care to take a look? http://hongpong.com/files/dre/DRE_STL06.ppt . via http://entrapped.com/Media/DRE_STL06.ppt .

*****

Out in the wider world the drumbeat of drug war corruption continues. A popular cartoon from Politico / M.Wuerker:

drugwar-politico-cartoon.jpg

In both Mexico and Afghanistan, absurd formations are emerging. (via here) Pentagon Wants to Keep Running Its Afghan Drug War From Blackwater's HQ | Danger Room | Wired.com, related to 2009 - cryptogon.com » Blackwater Worldwide Changes Its Name to Xe; Same Mercenaries, but Now with More “Aviation Support”. Also the latest from NarcoNews: Mexico’s New President Set to Empower a “Devil’s Cartel” | the narcosphere.

Also via DaveyD, thorough documentation of this racist project: US Marshal Told By Supervisors Not to Bring the ‘War on Drugs’ to White Communities | Davey D's Hip Hop Corner

We'll leave it there for now...

FAA Sets Large ND Drone Training Airspace - Federal Register Makes It So

The plan to convert America, and the world, into a hellish dystopia patrolled by killer flying robots continues apace with a fine fanciful scheme for flying more drones around North Dakota. It is apparently controlled by the FAA Minneapolis office to some extent.

PublicIntelligence.net reported more on the drone scheme at http://publicintelligence.net/dod-us-drone-activities-map/

According to their data, doom bogies to keep an eye on include:
Grand Forks Air Force Base, ND Air Force Global Hawk, Predator - Future
Camp Ripley, MN Army Shadow - Current
Fargo, ND Air Force Predator - Current
Ellsworth Air Force Base, SD Air Force Predator - Future

Via the crucial Cryptome.org : http://cryptome.org/2012/06/faa062012.htm

20 June 2012

FAA Sets Large ND Drone Training Airspace

[Federal Register Volume 77, Number 119 (Wednesday, June 20, 2012)]
[Rules and Regulations]
[Pages 36907-36914]
From the Federal Register Online via the Government Printing Office [www.gpo.gov]
[FR Doc No: 2012-15008]



========================================================================
Rules and Regulations
                                                Federal Register
________________________________________________________________________

This section of the FEDERAL REGISTER contains regulatory documents 
having general applicability and legal effect, most of which are keyed 
to and codified in the Code of Federal Regulations, which is published 
under 50 titles pursuant to 44 U.S.C. 1510.

The Code of Federal Regulations is sold by the Superintendent of Documents. 
Prices of new books are listed in the first FEDERAL REGISTER issue of each 
week.

========================================================================


Federal Register / Vol. 77, No. 119 / Wednesday, June 20, 2012 / 
Rules and Regulations

[[Page 36907]]



DEPARTMENT OF TRANSPORTATION

Federal Aviation Administration

14 CFR Part 73

[Docket No. FAA-2011-0117; Airspace Docket No. 09-AGL-31]


Establishment of Restricted Areas R-5402, R-5403A, R-5403B, R-
5403C, R-5403D, R-5403E, and R-5403F; Devils Lake, ND

AGENCY: Federal Aviation Administration (FAA), DOT.

ACTION: Final rule.

-----------------------------------------------------------------------

SUMMARY: This action establishes restricted area airspace within the 
Devils Lake Military Operations Area (MOA), overlying Camp Grafton 
Range, in the vicinity of Devils Lake, ND. The new restricted areas 
permit realistic training in modern tactics to be conducted at Camp 
Grafton Range while ensuring the safe and efficient use of the National 
Airspace System (NAS) in the Devils Lake, ND, area. Unlike restricted 
areas which are designated under Title 14 Code of Federal Regulations 
(14 CFR) part 73, MOAs are not regulatory airspace. However, since the 
restricted areas overlap the Devils Lake East MOA, the FAA is including 
a description of the Devils Lake East MOA change in this rule. The MOA 
change described herein will be published in the National Flight Data 
Digest (NFDD).

DATES: Effective Dates: Effective date 0901 UTC, July 26, 2012.

FOR FURTHER INFORMATION CONTACT: Colby Abbott, Airspace, Regulations 
and ATC Procedures Group, Office of Airspace Services, Federal Aviation 
Administration, 800 Independence Avenue SW., Washington, DC 20591; 
telephone: (202) 267-8783.

SUPPLEMENTARY INFORMATION: 

History

    On November 28, 2011, the FAA published in the Federal Register a 
notice of proposed rulemaking (NPRM) to establish Restricted Areas R-
5402, R-5403A, R-5403B, R-5403C, R-5403D, R-5403E, and R-5403F in the 
vicinity of Devils Lake, ND (76 FR 72869). Interested parties were 
invited to participate in this rulemaking effort by submitting written 
comments on the proposal. In response to public request, the FAA 
extended the comment period for 30 additional days (77 FR 1656; January 
11, 2012). There were 43 comments received in response to the NPRM with 
42 opposing various aspects of the proposal and one comment supporting 
the proposal as published. All comments received were considered before 
making a determination on this final rule. The following is a 
discussion of the substantive comments received and the agency's 
response.

Discussion of Comments

    One commenter contended that the 500 feet above ground level (AGL) 
base for R-5402 would impact low level, aerial operations such as crop 
dusters, wildlife and agricultural surveys, and emergency medical 
access. The FAA recognizes that when active, R-5402 would restrict 
nonparticipating aircraft from operating within its boundaries. To 
mitigate impacts to the aviation activities described above, the United 
States Air Force (USAF) has agreed to implement scheduling coordination 
measures to de-conflict laser operations and accommodate access by 
local farming, ranching, survey, and medical aviation interests when 
they need to fly in or through R-5402, when it is active.
    Another commenter noted that VFR traffic would have to 
circumnavigate active restricted airspace resulting in increased time 
and distances flown. The FAA acknowledges restricted area airspace 
segregates nonparticipating aircraft from hazardous activities 
occurring inside the restricted area and that, on occasion, 
nonparticipating aircraft affected by the restricted area will have to 
deviate from preferred routings to remain clear. The lateral boundaries 
and altitudes of the restricted area complex were defined to minimize 
impacts to nonparticipant aircraft, yet still support the military in 
accomplishing its training mission. The subdivided configuration of the 
restricted area complex, the altitude stratifications, and the entire 
restricted area complex designated as ``joint use,'' affords 
nonparticipant aircraft access to the portions of restricted area 
airspace not in use by the military to the greatest extent possible.
    One commenter expressed concern that segregating airspace for new 
types of aircraft sets a dangerous precedent. The FAA agrees and 
maintains its policy to establish restricted area airspace when 
determined necessary to confine or segregate activities considered 
hazardous to nonparticipating aircraft. The FAA considers UAS 
operations to be non-hazardous. However, the FAA recognizes that some 
UAS platforms have the ability to employ hazardous ordnance or sensors. 
Since the MQ-1 Predator [UAS] laser is non-eye safe and will be used 
during training sorties flown by the military, its use constitutes a 
hazardous activity that must be confined within restricted area 
airspace to protect nonparticipating aircraft.
    Two commenters suggested that Special Use Airspace (SUA) should be 
ceded back to civil control when not in use. The FAA proposed that the 
restricted areas be designated as ``joint use'' airspace, specifically 
to afford the highest level of access to NAS users and limit this 
access only when necessary. This rule provides that when the restricted 
areas are not needed by the using agency, the airspace will be returned 
to the controlling agency, Minneapolis Air Route Traffic Control 
Center, for access by other NAS users.
    Another commenter recommended that the proposed restricted area 
airspace be developed for concurrent use. The FAA considered the 
commenters use of ``concurrent use'' to mean ``sharing the same 
airspace, at the same time, between participating and nonparticipating 
aircraft.'' As noted previously, restricted areas are established to 
confine or segregate activities considered hazardous to 
nonparticipating aircraft; such as dropping bombs, firing guns/
missiles/rockets, or lasing with a non-eye safe laser. Concurrent use, 
as described above, would not be prudent in such an environment as it 
constitutes an unacceptable risk to nonparticipating aircraft.
    Twenty-two commenters stated that the proposed restricted areas 
should

[[Page 36908]]

have been developed in conjunction with the North Dakota Airspace 
Integration Team (NDAIT), a group formed to find solutions to UAS 
integration into the NAS, as well as coordinate UAS activities state-
wide. To clarify, the focus of this proposed action is consideration of 
establishing restricted areas to support hazardous military training 
activities, not UAS integration into the NAS. The FAA notes that the 
NDAIT was not established until after the USAF airspace proposal was 
submitted to the FAA and many of the NDAIT members took the opportunity 
to submit comments on the proposal.
    One commenter stated that the proposed airspace should be 
environmentally assessed for the broad array of military aircraft that 
would be expected to employ in conjunction with UAS. The FAA agrees and 
has confirmed that the Environmental Impact Statement for the bed down 
of the MQ-1 Predator at Grand Forks Air Force Base (AFB) addresses 
other aircraft that would likely train with the UAS in the proposed 
restricted area airspace complex.
    Another commenter stated that the proposed restricted area airspace 
would eventually be activated almost full time as is the current 
Temporary Flight Restriction (TFR) over Grand Forks AFB. The TFR 
referred to by the commenter is contained in the Special Security 
Instruction authorized under 14 CFR 99.7 for Customs and Border 
Protection (CBP) UAS operations conducted from Grand Forks AFB. 
Although the TFR is active while the CBP UAS is flying, it allows 
airspace access by non-participant aircraft using procedural separation 
rules. The restricted areas proposed by this action are being 
established with specific times of designation, to support the 
hazardous non-eye safe laser training conducted by the USAF. The times 
are described by ``core hours'' and also may be activated by NOTAM to 
allow for training periods outside the core hours, i.e. at night.
    Twenty commenters argued that the proposal is contrary to FAA 
policy, in that it is designed for the sole purpose of separating non-
hazardous types of VFR aircraft. The FAA has established this 
restricted area airspace to confine the MQ-1 Predator employment of a 
non-eye safe targeting laser, which is hazardous to nonparticipating 
pilots. This laser training for UAS pilots must be contained in 
restricted areas to confine the hazardous activity, as well as protect 
non-participating aircraft flying in the vicinity of the restricted 
areas. Even though the Predator operations in the restricted areas will 
normally occur in Visual Meteorological Conditions (VMC), the UAS will 
be on an IFR flight plan in accordance with U.S. Air Force 
requirements.
    Two commenters requested that the FAA establish a formal, annual 
review process and public report on the use and impacts of any 
designated airspace associated with UAS activity in Grand Forks, ND. 
The request to establish a formal annual review process with public 
reporting on use and impacts falls outside the scope of this proposed 
action. However, the FAA has a Restricted Area Annual Utilization 
reporting program already established to assist the FAA in managing 
special use airspace areas established throughout the NAS. These annual 
utilization reports provide objective information regarding the types 
of activities being conducted, as well as the times scheduled, 
activated, and actual use, which the FAA uses to assess the appropriate 
use of the restricted areas.
    Nineteen commenters recommended that proposed restricted airspace 
have a ``sunset'' date. The restricted areas are established to confine 
hazardous non-eye safe laser training, which will continue as long as 
the Predator UAS are operating from Grand Forks AFB. Technology 
developments to integrate UAS into the NAS with manned aircraft, as 
well as military Tactics, Techniques and Procedures (TTP) maturation 
may provide an opportunity to reconfigure the restricted area airspace 
at a future date, but the requirement for restricted area airspace will 
exist as long as the non-eye safe laser training is conducted.
    One commenter recommended a requirement for equipping the UAS with 
forward viewing sensors that would enable the UAS to comply with 14 CFR 
part 91 see-and-avoid rules. While the FAA is working with the industry 
to develop see-and-avoid solutions for the safe and eventual seamless 
integration of UAS into the NAS, this suggestion is outside the scope 
of this action.
    One commenter asked that the proposal be tabled until the FAA 
publishes its final Order/Advisory Circular regarding UAS operations in 
the NAS. The Order/Advisory Circular address the integration of UAS in 
the NAS, which is separate from the action of establishing restricted 
area airspace to confine hazardous non-eye safe laser training 
activities. This action is necessary to support the military's training 
requirement beginning this summer. The FAA is completing this airspace 
action separate from its UAS NAS integration guidance development 
efforts.
    Several commenters recommended that instead of creating new SUA for 
these activities that the USAF use existing restricted areas or the 
airspace subject to flight restrictions under Sec.  99.7 SSI and used 
by the Customs & Border Protection Agency (CBP) at Grand Forks AFB. The 
FAA advocates the use of existing SUA and requires proponents to 
examine all reasonable alternatives, prior to considering the need to 
establish new SUA. In this case, the USAF conducted an extensive 
analysis of alternatives and considered criteria including proximity to 
Grand Forks AFB, existence of a suitable air-to-ground range for laser 
targeting, and air traffic density both en route and at the training 
complex. The Beaver MOA in north central Minnesota is approximately 
three times as far as the proposed airspace, has much heavier air 
traffic density, and has no air-to-ground gunnery range. The Tiger MOAs 
in north central North Dakota are the same distance as the proposed 
airspace, have favorable air traffic density, but have no air-to-ground 
gunnery range. The airspace in the vicinity of the existing CBP Sec.  
99.7 SSI flight restriction would be closer, but has much higher 
traffic density and complexity, and has no air-to-ground range. 
Additionally, there were no useable restricted areas within reasonable 
distance of Grand Forks AFB for consideration. The FAA believes the 
USAF considered and analyzed the alternatives to this action and that 
establishing new SUA is the only reasonable option.
    One commenter suggested that the restricted area complex be moved 
north of Devils Lake. The FAA notes that the USAF studied an 
alternative of establishing restricted areas in the Tiger North and 
Tiger South MOAs, located north of Devils Lake, ND. While proximity to 
Grand Forks AFB and the air traffic density compared favorably to the 
proposed airspace area, the lack of an air-to-ground gunnery range 
suitable for hazardous laser training made this option operationally 
unfeasible. The FAA accepted the USAF's consideration and analysis of 
this alternative and proposed establishing the restricted areas set 
forth in this action.
    One commenter recommended that the proposed airspace be moved to 
another state as it would impact flying training in the vicinity of 
Grand Forks. This airspace proposal resulted from Congress' Base 
Realignment and Closure Commission of 2005 decision to retain Grand 
Forks Air Force Base in North Dakota for an emerging UAS mission. As 
addressed previously, Beaver MOA in north central Minnesota is the 
nearest SUA outside of North Dakota. It was approximately three times 
the distance from Grand Forks AFB, has much higher

[[Page 36909]]

air traffic density airspace, and has no air-to-ground gunnery range 
for hazardous laser training. The FAA recognizes the proposed 
restricted areas could impact civil flight training, largely conducted 
by the University of North Dakota and east of the proposed complex. 
Additionally, nearly all civil flight training activity that currently 
occurs in the vicinity of the restricted areas would take place below 
the proposed R-5403 footprint. Whereas the floor of R-5402 goes down to 
500 feet above ground level (AGL), its cylinder footprint was reduced 
to a 7 NM radius around R-5401 and the Camp Grafton Range to mitigate 
impacts to these civil operations. This airspace action provides a 
reasonable balance between military training requirements and 
accommodation of non-participant flight training.
    Three commenters stated that the vast size of the restricted area 
complex is not necessary. The restricted areas being established by 
this action provide the minimum vertical and lateral tactical 
maneuvering airspace required for UAS operators to accomplish target 
acquisition prior to attack, and then contain the non-eye safe laser 
during firing. The restricted area complex was configured to confine 
two UAS operating on independent mission profiles at the same time, 
while minimizing airspace impacts to non-participating aircraft. As the 
UAS training flight transitions from one phase of the mission profiles 
to another, unused segments will be deactivated and returned to the NAS 
consistent with the FAA's Joint Use Airspace policy. The subdivided and 
stratified configuration of the restricted area complex enables the 
USAF to only activate the restricted areas needed for their training 
sorties while leaving the rest of the complex inactive and available 
for NAS users. The FAA believes the segmentation and stratification of 
the complex will enhance civil access to those parts of the complex not 
activated for USAF training requirements. Actual procedures for 
restricted area activation and deactivation will be defined in a Letter 
of Procedure between the using and controlling agencies.
    Two commenters asked if the USAF could find a less cluttered area 
with more suitable weather for MQ-1 Predator operations. The FAA 
acknowledges that weather challenges will exist for the MQ-1 Predator 
operations at Grand Forks AFB. The decision to base Predator UAS at 
Grand Forks AFB, however, was mandated by Congress. The restricted 
areas proposed by this action were situated and proposed in the only 
location that met the USAF's operational requirements of proximity to 
launch/recovery base, low air traffic density, and availability of an 
existing air-to-ground gunnery range suitable for the hazardous non-eye 
safe laser training activities.
    One commenter contended that Alert Areas are more appropriate for 
UAS training activity. Alert Areas are designated to inform 
nonparticipating pilots of areas that contain a high volume of pilot 
training operations, or an unusual type of aeronautical activity, that 
they might not otherwise expect to encounter. However, only those 
activities that do not pose a hazard to other aircraft may be conducted 
in an Alert Area. Since employment of the non-eye safe laser carried by 
the MQ-1 Predator UAS is an activity hazardous to non-participants, an 
Alert Area is not an appropriate airspace solution.
    Two commenters stated that the Air Force is proposing restricted 
areas as a means to mitigate for lack of see-and-avoid capability for 
UAS operations. They noted, correctly, that the Air Force could use 
ground-based or airborne assets to provide see-and-avoid compliance 
instead. FAA policy dictates that restricted areas are established to 
confine activities considered hazardous to non-participating aircraft. 
As mentioned previously, the focus of this action is establishing 
restricted areas to support hazardous military training activities, not 
UAS integration into the NAS. As such, the FAA does not support 
establishing restricted areas as a solution to overcome UAS inability 
to comply with 14 CFR Part 91 see-and-avoid requirements. The FAA is 
establishing the restricted areas addressed in this action to confine 
the hazardous non-eye safe laser training activities conducted by the 
USAF.
    One commenter stated that new restricted airspace should be offset 
by reallocation of unused SUA elsewhere in the NAS. The proposed 
restricted areas fall almost entirely within the existing Devils Lake 
East MOA. When activated, the new restricted areas will be, in effect, 
replacing existing SUA. Although the regulatory and non-regulatory 
process for establishing SUA is not directly linked to the restricted 
area and MOA annual utilization reporting process, the FAA does review 
restricted area and MOA utilization annually. If candidate SUA areas 
are identified, the FAA works with the military service to 
appropriately return that airspace to the NAS.
    Seventeen commenters stated that Predator pilots can get the same 
training through simulation. The FAA cannot determine for the USAF the 
value of simulated UAS operator training over actual flying activities. 
The USAF is heavily investing in Live, Virtual, and Constructive (LVC) 
training options. As the commenters infer, the migration to a virtual 
training environment would be expected to reduce the demand for 
activating R-5402 and R-5403A-F. However, actual employment of the non-
eye safe laser will still be required for both training proficiency and 
equipment validation. This action balances the training airspace 
requirements identified by the USAF as it matures its UAS capabilities 
with the airspace access requirements of other NAS users.
    Twenty commenters addressed the increased collision hazard due to 
air traffic compression at lower altitudes and around the periphery of 
the proposed complex. The FAA recognizes that compression could occur 
when the restricted areas are active; however, the actual impact will 
be minimal. The FAA produced traffic counts for the 5 busiest summer 
days and 5 busiest winter days of 2011 during the proposed times of 
designation (0700-2200L) from 8,000 feet MSL to 14,000 feet MSL. Totals 
for all IFR and known VFR aircraft ranged between 4 and 22 aircraft 
over the 17-hour span. Volumes such as this are easily managed by 
standard ATC procedures. To enhance non-radar service in the far 
western part of the proposed complex, the FAA is considering a separate 
rulemaking action to modify V-170 so that it will remain clear of R-
5402 to the west. On average, four aircraft file V-170 over a 24-hour 
day. Lastly, the FAA is nearing completion of a project to add three 
terminal radar feeds, from Bismarck, Fargo, and Minot AFB, covering the 
restricted area airspace area into Minneapolis ARTCC. These feeds will 
improve low altitude radar surveillance and enhance flight safety 
around the proposed restricted areas.
    One commenter argued that the proposed airspace should be limited 
to daylight hours only. While daytime flying is usually safer in a 
visual see-and-avoid environment; when it comes to the military 
training for combat operations, darkness provides a significant 
tactical advantage and UAS must be capable of operating both day and 
night. While the USAF has a valid and recurring requirement to train 
during hours of darkness, the USAF was able to accept a 2-hour 
reduction in the published times of designation core hours from ``0700-
2200 daily, by NOTAM 6 hours in advance,'' to ``0700-2000 daily, by 
NOTAM 6 hours in advance.''

[[Page 36910]]

    Another commenter sought details on the UAS lost link plan. 
Although the lost link plan is not within the scope of this action, the 
FAA does require detailed procedures for UAS lost link situations for 
all UAS operations. These procedures will be similar to those in place 
today for UAS operations across the NAS. The servicing ATC facility and 
UAS operators closely coordinate lost link procedures and will 
incorporate them into the implementing Letters of Procedure (LOP) for 
the restricted areas established in this rule.
    Two commenters commented that the proposed restricted area complex 
stratification and segmentation was confusing and would lead to SUA 
airspace incursions. The FAA promotes stratifications and segmentation 
of large SUA complexes to maximize the safety and efficiency of the NAS 
and to enable more joint use opportunities to access the same airspace 
by non-participating aircraft. Sub-dividing the complex permits 
activation of a small percentage of the overall complex at any one time 
while still providing for a diverse set of training profiles during UAS 
sorties, which is especially well-suited for long duration UAS training 
missions. Additionally, enhanced joint use access eases compression of 
air traffic in the local area; thus, increasing flight safety.
    Nineteen commenters noted that UAS will not be able to see-and-
avoid large flocks of birds using migratory flyways, which could create 
a hazard for personnel on the ground. Both Grand Forks AFB and the 
University of North Dakota flight school, located at the Grand Forks 
International Airport, have conducted extensive research into bird 
strike potential and prevention. Their research found that more than 90 
percent of bird strikes occur below 3,500 feet AGL and that there are 
predictable windows for migratory bird activity, which are adjusted 
year-to-year based on historical and forecast weather patterns. Also, 
bird strikes are nearly twice as likely to occur at night compared to 
the day. The USAF has long standing bird strike avoidance procedures 
specifically customized for Grand Forks AFB, which will be optimized 
for UAS operations. Other mitigations include having the bases of the 
restricted airspace well above most bird activity, conducting most 
training during daylight hours, and adjusting UAS operations during 
seasonal migratory activity. These mitigations conform to both civil 
and military standard bird strike avoidance measures that are in place 
across the NAS.
    Eighteen commenters contended that persons and property under the 
proposed airspace would not be protected from the non-eye safe laser 
training. The USAF conducted a laser safety study in 2009 for the Camp 
Grafton Air-to-Ground Range. This range, where the laser targets will 
be placed, lies within the existing R-5401. The study examined laser 
and aircraft characteristics, topography, target composition, and 
employment parameters, and determined that the proposed airspace would 
adequately protect persons and property outside the footprint of R-
5401. Personnel working at the range will use proper protective gear 
should they need to access the target areas during laser employment 
periods. The FAA has reviewed and accepts the USAF's laser safety 
study. The restricted areas established by this action are designed to 
allow laser employment without hazard to persons and property in the 
vicinity of R-5401.
    Two commenters stated that it is dangerous to mix UAS with visual 
flight rules (VFR) air traffic. UAS are permitted to fly outside 
restricted area airspace in the NAS today and in the vicinity of VFR 
aircraft, under FAA approved Certificate of Waiver or Authorization 
(COA). Specific to this action, UAS operations will be occurring inside 
restricted area airspace that is established to confine the hazardous 
non-eye safe laser training activities; thus, segregated from 
nonparticipating aircraft.
    One commenter said that VFR pilot violations will increase and 
those less informed will pose a safety hazard. The FAA interpreted the 
commenters use ``violations'' to mean SUA airspace incursions. VFR 
pilots must conduct thorough pre-flight planning and are encouraged to 
seek airborne updates from ATC on the status of SUA. The FAA finds that 
the restricted areas established by this action pose no more risk of 
incursion or safety hazard than other restricted areas that exist in 
the NAS.
    Two commenters observed that the NPRM failed to identify how UAS 
would transit from Grand Forks AFB to the proposed restricted areas. 
The FAA considers UAS transit and climb activities to be non-hazardous; 
therefore, establishing new restricted areas for transit and climb 
purposes is inappropriate. While UAS transit and climb activities are 
non-hazardous, they are presently atypical. Therefore, specifics on 
transit and climb ground tracks, corridor altitudes and widths, and 
activation procedures will be accomplished procedurally and consistent 
with existing COA mitigation alternatives available today. The 
establishment of restricted areas airspace is focused on the hazardous 
non-eye safe laser training activities.
    Twenty four commenters noted that the proposed restricted areas 
would block V-170 & V-55 and impact V-169 & V-561. The FAA acknowledges 
that the proposed restricted area complex will have a minimal impact on 
three of the four Victor airways mentioned, depending on the restricted 
areas activated. The airway analysis began with V-170, which runs 
between Devils Lake, ND, and Jamestown, ND, with a Minimum En route 
Altitude (MEA) of 3,500 feet MSL along the effected segment of the 
airway. An average of four aircraft per day filed for V-170. R-5402, 
when active, impacts V-170 from 1200 feet AGL to 10,000 feet MSL. The 
FAA is considering a separate rulemaking action to modify V-170 by 
creating a slight ``dogleg'' to the west, which would allow unimpeded 
use of V-170 below 8,000 feet MSL regardless of the status of R-5402. 
Impacts to V-170 above 8,000 feet MSL are dependent upon which 
restricted areas are active.
    V-55 runs between Grand Forks, ND, and Bismarck, ND, with an MEA of 
8,000 feet MSL along the affected segment of the airway. An average of 
7 aircraft per day filed for V-55. Activation of R-5402, R-5403A, R-
5403B, or R-5403C would have no impact on V-55. The FAA raised the 
floor of R-5403D to 10,000 feet MSL and reduced the blocks for R-5403D 
and R-5403E to 2,000 feet each to allow ATC more flexibility to climb/
descend IFR traffic on V-55. The FAA is also considering establishing a 
Global Positioning Satellite MEA along the affected segment of V-55 to 
allow properly equipped non-participating aircraft to fly the V-55 
ground track, but at a lower altitude.
    V-561 runs between Grand Forks, ND, and Jamestown, ND, with an MEA 
of 4,000 feet MSL along this segment of the airway. An average of two 
aircraft per day filed for V-561. When activated, the southeast corner 
of R-5403D, R-5403E, and R-5403F encroach upon V-561 from 10,000 feet 
MSL-11,999 feet MSL, 12,000 feet MSL-13,999 feet MSL, or 14,000 feet 
MSL-17,999 feet MSL, respectively.
    V-169 runs between Devils Lake, ND, and Bismarck, ND, with an MEA 
of 3,500 feet MSL along this segment. The nearest point of any 
restricted area is 5 nautical miles (NM) from the centerline of V-169. 
Since Victor airways are 4 NM wide; the restricted areas do not 
encumber the use of V-169.
    The FAA acknowledges potential impacts to users on Victor airways 
V-55, V-170, and V-651 by the restricted areas established in this 
action.

[[Page 36911]]

However, based on the 13 total average daily flights filing for V-55, 
V-170, and V-651 in the same airspace as the proposed restricted area 
complex (V-169 is not affected by the proposed airspace), the impacts 
of the restricted areas on the three affected airways is considered 
minimal. These aircraft have air traffic control procedural 
alternatives available to include vectoring, altitude change, or re-
routing as appropriate.
    Nineteen commenters found that transcontinental and local area 
flights would be forced to deviate around restricted areas, increasing 
cost and flight time. The FAA understands that when the restricted 
areas are active, non-participation aircraft will have to accomplish 
course deviations or altitude changes for avoidance, which can increase 
distances flown and costs incurred. For this action, the FAA and USAF 
worked together to define the minimum airspace volume necessary to meet 
USAF training mission requirements and maximize airspace access to 
other users of the NAS. Reducing the overall size and internally 
segmenting and stratifying the complex have reduced course deviation 
distances and altitude changes required by non-participants to avoid 
active restricted areas. Additionally, the USAF as agreed to 
temporarily release active restricted airspace back to ZMP for non-
participant transit during non-routine/contingency events (i.e. due to 
weather, icing, aircraft malfunction, etc.). Air traffic in this part 
of the NAS is relatively light and the level of impact associated with 
establishing the restricted areas in this action is considered minimal 
when balanced against valid military training requirements.
    Twenty-four comments were received stating that four hours prior 
notice is insufficient lead time for activation by NOTAM, with most 
recommending that the prior notification time be increased to six 
hours. The FAA recognizes that many aircraft today have flight 
durations long enough that flight planning before takeoff may occur 
outside of the 4-hour window. Restricted areas provide protected 
airspace for hazardous operations with no option to transit when 
active, so changes in airspace status after flight planning would have 
an impact on routing or altitude. These impacts could be reduced by 
increasing the NOTAM notification time; therefore the proposed time of 
designation for R-5402 and R-5403A-F is amended to ``0700-2000 daily, 
by NOTAM 6 hours in advance; other times by NOTAM.''
    One commenter stated that the SUA should be limited to published 
times of designation or times that can be obtained through an Automated 
Flight Service Station (AFSS) or ZMP. The times of designation for the 
restricted areas conforms to FAA policy and provides military users the 
operational flexibility to adjust for unpredictable, yet expected 
events, such as poor weather conditions or aircraft maintenance delays. 
By establishing the restricted areas with a ``By NOTAM'' provision for 
activations, the AFSS will receive scheduled activation times at least 
6 hours in advance and can provide activation information when 
requested. Additionally, ZMP can provide the most current restricted 
areas status to airborne aircraft, workload permitting, as an 
additional service to any requesting IFR or VFR aircraft.
    Nineteen commenters contended that local and transient pilots would 
avoid the restricted areas regardless of the activation status. The FAA 
understands that some pilots may opt to avoid the vicinity of this 
proposed airspace complex; however, pilots have multiple ways to obtain 
SUA schedule information during preflight planning and while airborne 
to aid their situational awareness. Daily SUA schedules will be 
available on the sua.faa.gov Web site, NOTAMs will be issued at least 6 
hours prior to activating the restricted areas, and AFSS will brief SUA 
NOTAMS upon request. Airborne updates will also be available through 
ZMP or AFSS. Lastly, the USAF will provide a toll-free phone number for 
inclusion on aeronautical charts that will enable NAS users to contact 
the scheduling agency for SUA status information; similar to what is in 
place for the Adirondack SUA complex in New York.
    Two commenters requested that the FAA chart an ATC frequency for 
updates on the restricted areas. The FAA has frequencies listed on both 
the L-14 IFR Enroute Low Altitude Chart and the Twin Cities Sectional 
Aeronautical Chart already. Upon review, the VHF frequency listed on 
the IFR Enroute Low Altitude Chart near where R-5402 and R-5403A-F 
restricted areas will be established was found to be different than the 
frequency listed on the Sectional Aeronautical Chart listing of SUA for 
the existing R-5401 (which R-5402 and R-5403A-F will overlay). The FAA 
is taking action to correct the discrepancy so that matching 
frequencies are charted.
    Seventeen commenters stated that the NOTAM system is generally 
inadequate to inform users of SUA status, and the number of components 
to this restricted airspace would lead to intricate and confusing 
NOTAMs. The restricted area complex is comprised of 7 individual areas 
and structured to minimize complexity and maximize nonparticipant 
access when not required for military use during certain phases of a 
training mission. The overall complex configuration, with seven sub 
areas, is a reasonable balance between efficiency, complexity, and 
military requirements. The NOTAM system is designed to disseminate many 
types of aeronautical information, including restricted area status 
when activation is ``By NOTAM'' or outside published times of 
designation. Because of the ``By NOTAM'' provision in the legal 
description times of designation, activation NOTAMs for R-5402 and R-
5403A-F will be included in verbal briefings from AFSS, upon pilot 
request.

The Rule

    The FAA is amending 14 CFR part 73 to expand the vertical and 
lateral limits of restricted area airspace over the Camp Grafton Range 
to contain hazardous non-eye safe laser training operations being 
conducted by the emerging UAS mission at Grand Forks Air Force Base 
(AFB); thus, transforming the range into a viable non-eye safe laser 
training location. Camp Grafton Range is currently surrounded by R-
5401; however, the lateral boundaries and altitude are insufficient to 
contain the laser training mission profiles and tactics flown in combat 
operations today. This action supplements R-5401 by establishing 
additional restricted areas, R-5402, R-5403A, R-5403B, R-5403C, R-
5403D, R-5403E, and R-5403F, to provide the vertical and lateral 
tactical maneuver airspace needed for UAS target acquisition prior to 
attack, and to contain the non-eye safe laser during laser target 
designation training operations from medium to high altitudes.
    The restricted area R-5402 is defined by a 7 nautical mile (NM) 
radius around the center of R-5401, with the northern boundary adjusted 
to lie along the 47[deg]45'00'' N latitude. The restricted area 
altitude is upward from 500 feet above ground level to, but not 
including 10,000 feet MSL. This new restricted area provides a pathway 
for the non-eye safe laser beam to transit from R-5403A, R-5403B, and 
R-5403C (described below) through the existing R-5401 and onto Camp 
Grafton Range.
    The restricted areas R-5403A, R-5403B, and R-5403C share the same 
lateral boundaries, overlying R-5402 and layered in ascending order. 
The northern boundary of these R-5403 areas, as described in the 
regulatory text, share the same northern boundary as R-5402, the 
47[deg]45'00'' N latitude. The

[[Page 36912]]

western boundary lies approximately 14 NM west of R-5402 along the 
99[deg]15'00'' W longitude and the eastern boundary lies approximately 
7 NM east of R-5402 along the 98[deg]15'00'' W longitude. Finally, the 
southern boundary is established to remain north of the protected 
airspace for V-55. The restricted area altitudes, in ascending order, 
are defined upward from 8,000 feet MSL to, but not including 10,000 
feet MSL for R-5403A; upward from 10,000 feet MSL to, but not including 
14,000 feet MSL for R-5403B; and upward from 14,000 feet MSL to, but 
not including Flight Level (FL) 180 for R-5403C. The additional lateral 
and vertical dimensions provided by these restricted areas, in 
conjunction with R-5401, R-5402, R-5403D, R-5403E, R-5403F, establish 
the maneuvering airspace needed for UAS aircraft to practice the 
tactical maneuvering and standoff target acquisition training 
requirements necessary for the combat tactics and mission profiles 
flown today and to contain the hazardous non-eye safe laser, when 
employed, completely within restricted airspace.
    The areas R-5403D, R-5403E, and R-5403F also share the same lateral 
boundaries, adjacent to and southeast of R-5403A, R-5403B, and R-5403C, 
and are also layered in ascending order. The northern boundary of these 
R-5403 areas, as described in the regulatory text, shares the southern 
boundary of R-5403A, R-5403B, and R-5403C. The western boundary point 
reaches to the 99[deg]15'00'' W longitude and the eastern boundary lies 
along the 98[deg]15'00'' W longitude. Finally, the southern boundary is 
established to lie along the 47[deg]15'00'' N latitude. The restricted 
area altitudes, in ascending order, are defined upward from 10,000 feet 
MSL to, but not including 12,000 feet MSL for R-5403D; upward from 
12,000 feet MSL to, but not including 14,000 feet MSL for R-5403E; and 
upward from 14,000 feet MSL to, but not including Flight Level (FL) 180 
for R-5403F. The additional lateral and vertical dimensions provided by 
these restricted areas, in conjunction with R-5401, R-5402, R-5403A, R-
5403B, R-5403C, and the Camp Grafton Range, establish the maneuvering 
airspace, standoff target acquisition, and hazardous non-eye safe laser 
employment training completely within restricted airspace, as noted 
above.
    During the NPRM public comment period, it was realized that the 
proposal section of the NPRM preamble described the southern boundary 
for the proposed R-5403D, R-5403E, and R-5403F to lay along the 
47[deg]30'00'' N latitude, in error. However, the regulatory text in 
the NPRM correctly described the southern boundary for these proposed 
restricted areas to lie along the 47[deg]15'00'' N latitude. This 
action confirms the southern boundary for R-5403D, R-5403E, and R-5403F 
is along the 47[deg]15'00'' N latitude.
    Restricted areas R-5402, R-5403A, R-5403B, R-5403C, R-5403D, R-
5403E, and R-5403F are all designated as ``joint-use'' airspace. This 
means that, during periods when any of the restricted airspace areas 
are not needed by the using agency for its designated purposes, the 
airspace will be returned to the controlling agency for access by other 
NAS users. The Minneapolis Air Route Traffic Control Center is the 
controlling agency for the restricted areas.
    Lastly, to prevent confusion and conflict by establishing the new 
restricted areas in an existing MOA, and having both SUA areas active 
in the same volume of airspace at the same time, the Devils Lake East 
MOA legal description is being amended in the NFDD. The Devils Lake 
East MOA amendment will exclude R-5401, R-5402, R-5403A, R-5403B, R-
5403C, R-5403D, R-5403E, and R-5403F when the restricted areas are 
active. The intent is to exclude the restricted areas in Devils Lake 
East MOA individually as they are activated. This MOA amendment will 
prevent airspace conflict with overlapping special use airspace areas.

Regulatory Notices and Analyses

    Changes to Federal regulations must undergo several economic 
analyses. First, Executive Order 12866 and Executive Order 13563 direct 
that each Federal agency shall propose or adopt a regulation only upon 
a reasoned determination that the benefits of the intended regulation 
justify its costs. Second, the Regulatory Flexibility Act of 1980 (Pub. 
L. 96-354) requires agencies to analyze the economic impact of 
regulatory changes on small entities. Third, the Trade Agreements Act 
(Pub. L. 96-39) prohibits agencies from setting standards that create 
unnecessary obstacles to the foreign commerce of the United States. In 
developing U.S. standards, the Trade Act requires agencies to consider 
international standards and, where appropriate, that they be the basis 
of U.S. standards. Fourth, the Unfunded Mandates Reform Act of 1995 
(Pub. L. 104-4) requires agencies to prepare a written assessment of 
the costs, benefits, and other effects of proposed or final rules that 
include a Federal mandate likely to result in the expenditure by State, 
local, or tribal governments, in the aggregate, or by the private 
sector, of $100 million or more annually (adjusted for inflation with 
base year of 1995). This portion of the preamble summarizes the FAA's 
analysis of the economic impacts of this final rule.
    Department of Transportation Order DOT 2100.5 prescribes policies 
and procedures for simplification, analysis, and review of regulations. 
If the expected cost impact is so minimal that a proposed or final rule 
does not warrant a full evaluation, this order permits that a statement 
to that effect and the basis for it to be included in the preamble if a 
full regulatory evaluation of the cost and benefits is not prepared. 
Such a determination has been made for this final rule. The reasoning 
for this determination follows:
    As presented in the discussion of comments section of this 
preamble, commenters stated that there could be the following potential 
adverse economic impacts from implementing this final rule: the rule 
will block V-170 and V-55 and limit the use of V-169 and V-561; VFR and 
local area flights will be forced to deviate around restricted areas, 
increasing cost and flight time; and the 500 feet AGL floor for R-5402 
will affect low level aerial operations such as crop dusters, wildlife 
and agricultural surveys, and emergency medical access.
    With respect to the first potential impact, as discussed in the 
preamble, the FAA acknowledges that users of Victor airways V-55, V-
170, and V-561 could be potentially affected when the restricted areas 
established in this action are active; however users of V-169 will not 
be affected at all. Users of V-170 from 1200 feet AGL to 8,000 feet MSL 
would be affected only when R-5402 is active. The FAA's has determined 
that there is an average of 4 flights per day between Devils Lake, ND, 
and Jamestown, ND. Of these flights, 90 percent are general aviation 
flights (many of them University of North Dakota training flights) and 
10 percent are military or air taxi flights. The potential effect on 
users of V-170 could be offset by several actions. One action would be 
to modify V-170 by creating a slight ``dogleg'' further west of R-5402 
to allow unimpeded use of V-170 below 8,000 feet MSL regardless of the 
status of R-5402. The FAA estimates that this ``dogleg'' would add 
about 5 miles to the length of the flight between Devils Lake and 
Jamestown. Another action would be for air traffic control to either 
vector the aircraft west of R-5402 or climb the aircraft to 8,000 feet 
MSL to avoid R-5402. V-170 above 8,000 feet MSL, V-55, and V-561 can 
still be used by the public, even during military training

[[Page 36913]]

operations, if the nonparticipant aircraft flies at a different 
altitude than the altitudes the military is using at that time. The FAA 
has determined that these adjustments will result in minimal cost to 
the affected operators.
    With respect to the second potential impact, with the exception of 
R-5402, the public will not be required to deviate around the 
restricted areas, even during military operations, as long as the 
nonparticipating aircraft flies at an altitude above or below the 
altitudes that the military is using at that time. The FAA has 
determined that these altitude adjustments will have a minimal effect 
on cost.
    With respect to the third potential impact, the USAF has agreed to 
implement scheduling coordination measures for R-5402 that will 
accommodate access by local farming, ranching, survey, and medical 
aviation interests. Further, when any of the restricted areas are not 
needed by the USAF for its intended purposes, the airspace will be 
returned to the controlling agency, Minneapolis Air Route Traffic 
Control Center, for access by other NAS users; providing considerable 
time for these interests to perform most of their aviation activities 
in a timely manner. The FAA has determined that these potential 
disruptions in public aviation will have a minimal effect on cost.
    The FAA has, therefore, determined that this final rule is not a 
``significant regulatory action'' as defined in section 3(f) of 
Executive Order 12866, and is not ``significant'' as defined in DOT's 
Regulatory Policies and Procedures.

Regulatory Flexibility Determination

    The Regulatory Flexibility Act of 1980 (Pub. L. 96-354) (RFA) 
establishes ``as a principle of regulatory issuance that agencies shall 
endeavor, consistent with the objectives of the rule and of applicable 
statutes, to fit regulatory and informational requirements to the scale 
of the businesses, organizations, and governmental jurisdictions 
subject to regulation. To achieve this principle, agencies are required 
to solicit and consider flexible regulatory proposals and to explain 
the rationale for their actions to assure that such proposals are given 
serious consideration.'' The RFA covers a wide-range of small entities, 
including small businesses, not-for-profit organizations, and small 
governmental jurisdictions.
    Agencies must perform a review to determine whether a rule will 
have a significant economic impact on a substantial number of small 
entities. If the agency determines that it will, the agency must 
prepare a regulatory flexibility analysis as described in the RFA.
    However, if an agency determines that a rule is not expected to 
have a significant economic impact on a substantial number of small 
entities, section 605(b) of the RFA provides that the head of the 
agency may so certify and a regulatory flexibility analysis is not 
required. The certification must include a statement providing the 
factual basis for this determination, and the reasoning should be 
clear.
    The FAA received two comments from small business owners and a 
comment from the North Dakota Agricultural Aviation Association 
(NDAAA), representing agricultural aviation operators. The comments 
from the business owners expressed concerns about the availability of 
airspace and that they would be diverted from their normal flight 
plans, thereby increasing their costs. As previously stated in this 
preamble, however, these routes will not be closed even during military 
operations--they can be flown by nonparticipant aircraft so long as 
those aircraft are not at the altitudes being used by the military. The 
NDAAA comment that agricultural aircraft are frequently ferried at 
altitudes greater than 500 feet applies only to those aircraft in R-
5402--not in any of the other areas. As previously noted, the agreement 
with the USAF and the fact that there are no restrictions in R-5402 
when it is not being used by the military will minimize the potential 
economic impact to agricultural aviation operations in this airspace.
    While the FAA believes that one air taxi operator, a few small 
business operators, and a few agricultural aviation operators 
constitute a substantial number of small entities, based on the 
previous analysis, the FAA determined that the final rule will have a 
minimal economic impact.
    Therefore, as the acting FAA Administrator, I certify that this 
rule will not have a significant economic impact on a substantial 
number of small entities.

International Trade Impact Assessment

    The Trade Agreements Act of 1979 (Pub. L. 96-39), as amended by the 
Uruguay Round Agreements Act (Pub. L. 103-465), prohibits Federal 
agencies from establishing standards or engaging in related activities 
that create unnecessary obstacles to the foreign commerce of the United 
States. Pursuant to these Acts, the establishment of standards is not 
considered an unnecessary obstacle to the foreign commerce of the 
United States, so long as the standard has a legitimate domestic 
objective, such the protection of safety, and does not operate in a 
manner that excludes imports that meet this objective. The statute also 
requires consideration of international standards and, where 
appropriate, that they be the basis for U.S. standards. The FAA has 
assessed the potential effect of this final rule and determined that it 
will have only a domestic impact and therefore no effect on 
international trade.

Unfunded Mandates Assessment

    Title II of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-
4) requires each Federal agency to prepare a written statement 
assessing the effects of any Federal mandate in a proposed or final 
agency rule that may result in an expenditure of $100 million or more 
(in 1995 dollars) in any one year by State, local, and tribal 
governments, in the aggregate, or by the private sector; such a mandate 
is deemed to be a ``significant regulatory action.'' The FAA currently 
uses an inflation-adjusted value of $143.1 million in lieu of $100 
million. This final rule does not contain such a mandate; therefore, 
the requirements of Title II of the Act do not apply.

Environmental Review

    Pursuant to Section 102(2) of the National Environmental Policy Act 
of 1969 (NEPA), the Council on Environmental Quality (CEQ) regulations 
implementing NEPA (40 CFR parts 1500-1508), and other applicable law, 
the USAF prepared and published The BRAC Beddown and Flight Operations 
of Remotely Piloted Aircraft at Grand Forks Air Force Base, North 
Dakota'' dated July 2010 (hereinafter the FEIS) that analyzed the 
potential for environmental impacts associated with the proposed 
creation of Restricted Areas R-5402, R-5403A, R-5403B, R-5403C, R-
5403D, R-5403E, and R-5403F. In September 2010, the USAF issued a 
Record of Decision based on the results of the FEIS. In accordance with 
applicable CEQ regulations (40 CFR 1501.6) and the Memorandum of 
Understanding (MOU) between FAA and Department of Defense (DOD) dated 
October 2005, the FAA was a cooperating agency on the FEIS. The FAA has 
conducted an independent review of the FEIS and found that it is an 
adequate statement. Pursuant to 40 CFR 1506.3(a) and (c), the FAA is 
adopting the portions of the FEIS for this action that support the 
establishment of the above named restricted areas. The FAA has 
documented its partial adoption in a separate document entitled 
``Partial Adoption of Final EIS and Record of

[[Page 36914]]

Decision for the Establishment of Restricted Areas R-5402 and 5403.'' 
This final rule, which establishes restricted areas R-5402, R-5403A, R-
5403B, R-5403C, R-5403D, R-5403E, and R-5403F, will not result in 
significant environmental impacts. A copy of the FAA Partial Adoption 
of FEIS and ROD has been placed in the public docket for this 
rulemaking and is incorporated by reference.

FAA Authority

    The FAA's authority to issue rules regarding aviation safety is 
found in Title 49 of the United States Code. Subtitle I, Section 106 
describes the authority of the FAA Administrator. Subtitle VII, 
Aviation Programs, describes in more detail the scope of the agency's 
authority.
    This rulemaking is promulgated under the authority described in 
Subtitle VII, Part A, Subpart I, Section 40103. Under that section, the 
FAA is charged with prescribing regulations to assign the use of the 
airspace necessary to ensure the safety of aircraft and the efficient 
use of airspace. This regulation is within the scope of that authority 
as it establishes restricted area airspace at Camp Grafton Range, near 
Devils Lake, ND, to enhance safety and accommodate essential military 
training.

List of Subjects in 14 CFR Part 73

    Airspace, Prohibited areas, Restricted areas.

The Amendment

    In consideration of the foregoing, the Federal Aviation 
Administration amends 14 CFR part 73 as follows:

PART 73--SPECIAL USE AIRSPACE

0
1. The authority citation for part 73 continues to read as follows:

    Authority:  49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854, 
24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389.


Sec.  73.54  [Amended]

0
2. Section 73.54 is amended as follows:
* * * * *

R-5402 Devils Lake, ND [New]

    Boundaries. Beginning at lat. 47[deg]45'00'' N., long. 
98[deg]47'19'' W.; to lat. 47[deg]45'00'' N., long. 98[deg]31'25'' 
W.; then clockwise on a 7 NM arc centered on lat. 47[deg]40'31'' N., 
long. 98[deg]39'22'' W.; to the point of beginning, excluding the 
airspace within R-5401 when active, and R-5403A when active.
    Designated altitudes. 500 feet AGL to, but not including, 10,000 
feet MSL.
    Time of designation. 0700-2000 daily, by NOTAM 6 hours in 
advance; other times by NOTAM.
    Controlling agency. FAA, Minneapolis ARTCC.
    Using agency. U.S. Air Force, 119th Operations Support Squadron, 
Hector International Airport, Fargo, ND.
* * * * *

R-5403A Devils Lake, ND [New]

    Boundaries. Beginning at lat. 47[deg]45'00'' N., long. 
99[deg]15'00'' W.; to lat. 47[deg]45'00'' N., long. 98[deg]15'00'' 
W.; to lat. 47[deg]35'39'' N., long. 98[deg]15'00'' W.; to lat. 
47[deg]15'00'' N., long. 99[deg]15'00'' W.; to the point of 
beginning.
    Designated altitudes. 8,000 feet MSL to, but not including, 
10,000 feet MSL.
    Time of designation. 0700-2000 daily, by NOTAM 6 hours in 
advance; other times by NOTAM.
    Controlling agency. FAA, Minneapolis ARTCC.
    Using agency. U.S. Air Force, 119th Operations Support Squadron, 
Hector International Airport, Fargo, ND.

R-5403B Devils Lake, ND [New]

    Boundaries. Beginning at lat. 47[deg]45'00'' N., long. 
99[deg]15'00'' W.; to lat. 47[deg]45'00'' N., long. 98[deg]15'00'' 
W.; to lat. 47[deg]35'39'' N., long. 98[deg]15'00'' W.; to lat. 
47[deg]15'00'' N., long. 99[deg]15'00'' W.; to the point of 
beginning.
    Designated altitudes. 10,000 feet MSL to, but not including, 
14,000 feet MSL.
    Time of designation. 0700-2000 daily, by NOTAM 6 hours in 
advance; other times by NOTAM.
    Controlling agency. FAA, Minneapolis ARTCC.
    Using agency. U.S. Air Force, 119th Operations Support Squadron, 
Hector International Airport, Fargo, ND.

R-5403C Devils Lake, ND [New]

    Boundaries. Beginning at lat. 47[deg]45'00'' N., long. 
99[deg]15'00'' W.; to lat. 47[deg]45'00'' N., long. 98[deg]15'00'' 
W.; to lat. 47[deg]35'39'' N., long. 98[deg]15'00'' W.; to lat. 
47[deg]15'00'' N., long. 99[deg]15'00'' W.; to the point of 
beginning.
    Designated altitudes. 14,000 feet MSL to, but not including, FL 
180.
    Time of designation. 0700-2000 daily, by NOTAM 6 hours in 
advance; other times by NOTAM.
    Controlling agency. FAA, Minneapolis ARTCC.
    Using agency. U.S. Air Force, 119th Operations Support Squadron, 
Hector International Airport, Fargo, ND.

R-5403D Devils Lake, ND [New]

    Boundaries. Beginning at lat. 47[deg]35'39'' N., long. 
98[deg]15'00'' W.; to lat. 47[deg]15'00'' N., long. 98[deg]15'00'' 
W.; to lat. 47[deg]15'00'' N., long. 99[deg]15'00'' W.; to the point 
of beginning.
    Designated altitudes. 10,000 feet MSL to, but not including, 
12,000 feet MSL.
    Time of designation. 0700-2000 daily, by NOTAM 6 hours in 
advance; other times by NOTAM.
    Controlling agency. FAA, Minneapolis ARTCC.
    Using agency. U.S. Air Force, 119th Operations Support Squadron, 
Hector International Airport, Fargo, ND.

R-5403E Devils Lake, ND [New]

    Boundaries. Beginning at lat. 47[deg]35'39'' N., long. 
98[deg]15'00'' W.; to lat. 47[deg]15'00'' N., long. 98[deg]15'00'' 
W.; to lat. 47[deg]15'00'' N., long. 99[deg]15'00'' W.; to the point 
of beginning.
    Designated altitudes. 12,000 feet MSL to, but not including, 
14,000 feet MSL.
    Time of designation. 0700-2000 daily, by NOTAM 6 hours in 
advance; other times by NOTAM.
    Controlling agency. FAA, Minneapolis ARTCC.
    Using agency. U.S. Air Force, 119th Operations Support Squadron, 
Hector International Airport, Fargo, ND.

R-5403F Devils Lake, ND [New]

    Boundaries. Beginning at lat. 47[deg]35'39'' N., long. 
98[deg]15'00'' W.; to lat. 47[deg]15'00'' N., long. 98[deg]15'00'' 
W.; to lat. 47[deg]15'00'' N., long. 99[deg]15'00'' W.; to the point 
of beginning.
    Designated altitudes. 14,000 feet MSL to, but not including, FL 
180.
    Time of designation. 0700-2000 daily, by NOTAM 6 hours in 
advance; other times by NOTAM.
    Controlling agency. FAA, Minneapolis ARTCC.
    Using agency. U.S. Air Force, 119th Operations Support Squadron, 
Hector International Airport, Fargo, ND.

    Issued in Washington, DC, on June 14, 2012.
Paul Gallant,
Acting Manager, Airspace, Regulations and ATC Procedures Group.
[FR Doc. 2012-15008 Filed 6-19-12; 8:45 am]
BILLING CODE 4910-13-P
Syndicate content