#1395 Marine Links Serco Canada’s Front Running Slave Clocks to Harper’s Resolute Killi-Second Crash
Plum City – (AbelDanger.net). United States Marine Field McConnell has linked Serco Canada’s front-running slave clocks installed on Boeing’s E4B Nightwatch aircraft, to Stephen Harper’s allegedly illegal delegation of a ‘Killi-Second’ authority to his (?) military commanders to avoid a mid-air collision during Operation Nanook by crashing a civilian plane near Resolute, Nanavut, on August 20, 2011.
“Prime Minister Stephen Harper met with community members and first responders Tuesday in the remote Nunavut community of Resolute after 12 people were killed in a deadly plane crash on the weekend. Harper’s sixth annual visit to Canada’s North was delayed after the plane went down near the remote community Saturday, leaving only three survivors. The visit comes as a major joint military exercise, Operation Nanook, is in its third week in the Resolute region. If not for the military exercise in the region, it would have taken hours for help to arrive. No military search and rescue resources are permanently based in the high Arctic [Serco bankers’ (HSBC) think we are all stupid; it’s the same DMORT portable morgue and Serco front-running bullshit as the lone-gunman exercise near the Sandy Hook Elementary School and Naudet snuff film money shot of 9/11]. http://www.cbc.ca/news/canada/story/2011/08/23/harper-arctic-tour.html”
“Crashed Resolute plane posed mid-air collision risk
TSB directive says that had plane not crashed, it was at risk of colliding with another plane
Posted: Aug 20, 2012 4:51 PM CT
Last Updated: Aug 21, 2012 7:56 AM CT
The airport in the hamlet of Resolute, Nunavut, had been temporarily taken over by the military on Aug. 20, 2011 – the day of the deadly First Air crash near the community. The TSB said had the plane not crashed, it was at a risk of a mid-air collision with another plane which was coming to the community around the same time. (Vincent/Desrosiers/CBC)
Report on Resolute crash likely won’t be ready until 2013
Resolute plane crash investigation update 2:14
Had the First Air flight 6560 not crashed in Resolute, Nunavut, one year ago, there was a risk that it could have collided mid-air with another incoming plane, according to the Transportation Safety Board of Canada.
The TSB’s final report on the tragic crash which claimed 12 lives is still pending. However, CBC News has learned the board released two air safety warnings since its interim report on the crash.
The advisories are not necessarily linked to the cause of the crash, but they identify issues found in the course of the investigation.
One points to military protocols during Operation Nanook and the other points to problems with the plane’s flight recorder.
On the day of the crash, the military had temporarily taken over control of the airspace around Resolute. The TSB discovered there were gaps in communication between the military and aircraft in the area. The board is advising that the Canadian Forces ensure adequate space between planes.
“In the North, they have procedures and the pilots are supposed to communicate on a frequency to let everyone know where they are. For this particular exercise, the military was setting up a radar station. Before it was completely set up we noticed that there was aircraft flying through there that weren’t contacting the military, so we informed them they may want to add that to their procedure,” said Mark Clitsome, the director of air investigations with the board.
Clitsome said at this time, the TSB won’t say if this gap in communication was a factor in the First Air crash.
However, the board did say that had the First Air Flight not hit the ground, there was a risk of a mid-air collision with another plane that was landing in the community around the same time.
The TSB also found problems with the flight’s data recorder – it failed to record the first 29 minutes of the flight. The board said the regular maintenance check on the recorder was not sufficient because it didn’t spot the problem. The board added that the recorder problems had been going on since 2008.
Read the full TSB directives below.”
More to follow.