As part of the strengthened and modernized Canadian Environmental Assessment Act, 2012 (CEAA 2012) put in place to support the government’s responsible resource development initiative, the Canadian Environmental Assessment Agency must determine whether a federal environmental assessment is required pursuant to the CEAA 2012 for the proposed Coastal GasLink Pipeline Project in British Columbia (B.C.). To assist it in making its decision, the Agency is seeking comments from the public on the project and its potential effects on the environment.
Coastal GasLink Pipeline Ltd. is proposing the construction and operation of an approximately 650-km pipeline to deliver natural gas from the area near the community of Groundbirch, B.C. (40 km west of Dawson Creek) to a proposed liquefied natural gas facility near Kitimat, B.C. The project will initially have the capacity to flow approximately 1.7 billion cubic feet of natural gas per day and could deliver up to approximately 5.0 billion cubic feet per day of natural gas after further expansion.
Written comments must be submitted by December 3, 2012.
Like the current Enbridge Northern Gateway project Joint Review Panel and the National Energy Board hearings in June 2011 on the Kitimat LNG project all comments received will be considered public.
The CEAA says after it has received the comments whether or not there should be an assessmet, it will post a decision on its website stating whether a federal environmental assessment is required.
The CEAA goes on to say:
If it is determined that a federal environmental assessment is required, the public will have three more opportunities to comment on this project, consistent with the transparency and public engagement elements of CEAA 2012.
Projects subject to CEAA 2012 are assessed using a science-based approach. If the project is permitted to proceed to the next phase, it will continue to be subject to Canada’s strong environmental laws, rigorous enforcement and follow-up, and increased fines.
If there is a federal assessment, the most likely course would be to create a new Joint Review Panel. However, this will not be a JRP with the National Energy Board, because the Coastal GasLink project does not cross a provincial boundary, thus it would not make it subject to scrutiny by the NEB.
Instead, if current practice is followed (and that is uncertain given the evolving role of the Harper government in environmental decisions) the new JRP would be in partnership with the British Columbia Oil and Gas Commission, which has jurisdiction over energy projects that are entirely within the province of BC.
The Jackpine Joint Review Panel is the first to held under the new rules from Bill C-38 that limit environmental assessment.
The lead up to the Alberta Jackpine Joint Review Panel hearings was mired in confusion, partly because of the restrictions imposed by the Harper government in Bill C-38 which limited the scope of environmental assessments.
According to initial media reports in The Financial Post, the Joint Review Panel excluded First Nations further downstream from the Jackpine project ruling and individual members of the Athabasca Chipewyan First Nation that they were not “interested parties.” The Post cited rules on who can participate were tightened up when the Harper government changed the criterion for environmental assessment under Bill C-38. The Financial Post reported a French-owned oil company was permitted to participate.
A few days after the Financial Post report, Gary Perkins, counsel for the Jackpine Joint Review Panel released a letter to participants including Bill Erasmus, Dene National chief and Assembly of First Nations regional chief, who said he was denied standing. There appears to have been confusion over how people could register as intervenors for the Jackpine hearings, since according to the Perkins letter they apparently did so on a company website that no relation to the Jackpine JRP. Perkins also attempted to clarify its constitutional role with First Nations, saying it did not have jurisdiction to decide whether or not the Crown was consulting properly. (PDF copy below)
The Perkins letter also said that the Fort McKay First Nation, Fort McMurray First Nation #468, the Athabasca Cree First Nation, Fort McKay Metis Community Association and the Metis Association of Alberta Region 1 plus some individual members of First Nations are allowed to participate in the hearings.
The arcane rules of the Northern Gateway Joint Review Panel has caused months of confusion and frustration for many of those who participated, whether they from the BC provincial Department of Justice or other government participants, intervenors or those making ten minute comments.
Although most people in northwestern British Columbia support the liquified natural gas projects, the prospect of a new Joint Review Panel could likely quickly become controversial in this region. A Coastal GasLink JRP will be the first real test of the restrictions on environmental review imposed on Canada by the Harper government. Environmental groups, especially the few groups that oppose any pipeline projects, will be wary of precedents and likely to test the limits from Bill C-38. Both environmental groups and First Nations will be on alert for any limitations on who can participate in a review. First Nations, even if they support the LNG projects, as most do, will be wary of any attempt by the federal government to limit consultation, rights and title.
A Coastal Gaslink JRP will be a big hot potato for District of Kitimat Council, which has taken a controversial strictly neutral position on the Enbridge Northern Gateway pipeline project until after that Joint Review Panel reports sometime in 2014. Can the District Council now take a positive position on a natural gas pipeline, which from all appearances council supports, long before a Coastal GasLink JRP report (if there is a panel) without facing charges of hypocrisy?
Kitimat, BC and New York City had one thing in common this week, the misuse and use of social media, Twitter and Facebook, that spread both accurate warnings and dangerous misinformation about an impending disaster. In the case of New York and the surrounding area, it was Superstorm Sandy that caused widespread devastation. For Kitimat it was the tsunami warning after the 7.7 earthquake off Haida Gwaii and no damage but a lot of worry for residents.
New York has a population of millions, it is the media centre for the United States, and much of the U.S. Northeast coast is still recovering from the horrendous damage from Superstorm Sandy.
Kitimat has a population of about 8,000 and my home town is off the media radar except when the Enbridge Northern Gateway pipeline issue pops up on the national assignment desks. If the October 27, 2012 tsunami from the Haida Gwaii earthquake did come up Douglas Channel to Kitimat harbour, it was so minimal that any water rise was scarcely noticed.
In one way New York (the state and the city) plus New Jersey and other states were ahead of Kitimat. In the US, there were numerous official sources on Twitter and Facebook, as well as those ubiquitous live TV news conferences with New York Mayor Michael Bloomberg or various state governors.
On October 27, neither Kitimat nor the nearby town of Terrace had any official emergency outlets on social media. In Kitimat, that may change as early as this Monday when District Council considers what happened last Saturday night.
It has been documented that there was no official response from Emergency Management British Columbia (still largely known under its former name Provincial Emergency Program) until an hour after the first earthquake report from the US Geological Survey. Only sometime later did BC’s provincial emergency officials hold a short conference call with reporters. (At the time the BC Liberals were holding a policy convention at Whistler. After the conference call, TV reporters at the convention in Whistler were doing live reports with taped clips of Attorney General Shirley Bond. It should have been easy for Bond and other senior government officials, including Premier Christy Clark–who is plummeting the polls– to hold a live news conference just as US state governors and mayors did later in the week when it came to Superstorm Sandy)
So in that hour of silence from the BC government, one question that has to be raised is: Were the tsunami warnings so completely uncoordinated–at least as far as the public is concerned– that that was one cause of the misinformation and inaccurate information on Twitter and Facebook? Or did confusing information from authorities simply compound and amplify the social media misinformation that was already spreading across British Columbia and around the world?
Here in the northwest, the two area fire chiefs Trent Bossence of Kitimat and John Klie of Terrace have said after the quake that landline phones and some cell phones were out, in some areas up to an hour after the first shock. Klie told CFTK’s Tyler Noble on Open Connection that after the landline phones came back up the Terrace fire department was flooded with calls from people “who wanted it now.” The ability of firefighters to get information was then delayed “because so many people were trying to get through.”
Kitimat has the advantage of being a small town. Emergency services already had scheduled a volunteer recruiting session last Monday night (October 29) for Emergency Social Services–the folks who run, coordinate and work in reception centres during an emergency–so it was easy to turn that meeting into a earthquake/tsunami warning post mortem. (Imagine that happening in New York?)
The most important issue on Saturday night was the false information on both Facebook and Twitter that the Kildala neighbourhood was being evacuated due to the tsunami warning. Other false information on social media indicated that the giant Bechtel work camp at the Rio Tinto Alcan Kitimat Modernization Project was also being evacuated.
As Kitimat’s Emergency Plan Coordinator Bob McLeod told the earthquake post mortem about the information on Facebook and Twitter:
Kitimat Emergency Coordinator Bob McLeod at the earthquake postmortem Oct. 29, 2012 (Robin Rowland/Northwest Coast Energy News)
“Your aim is to be saving people, and you’re not saving people. There was one case where someone was going around banging on doors in Kildala, telling them to get out. I think it was over when he was in the lockup that night. But this is the type of foolishness that goes on. You have people going on Facebook saying ‘Alcan’s been evacuated. they’re evacuating Kildala.’ I am going to be generous and say it is misinformation… It was a blatant lie. And that does not help.”
(For those outside Kitimat you can check the town on Google maps) As seen on this screen grab, Kildala is a low lying part of town. The area north of Highway 37 is higher on a hill. Closer to the ocean at Douglas Channel are the Bechtel/RTA Kitimat Modernization Project work camps.
After driving from the village to the town, McFarlane told the meeting that he stopped at the town viewpoint where “people were telling me they had already been evacuated out of the Kildala neighbourhood, so my first stop after that was the fire department.” The fire hall is about a couple of blocks from the viewpoint, so it was easy to get accurate information from the fire department.
McFarlane continued, “I found the night of the earthquake that no information is just as bad as wrong information. People were calling me on my cell saying why does the Kitimat Daily say we have to evacuate.” That is because the Daily republished a warning from the Pacific Tsunami Warning Centre that “said tsunami warning, evacuation for the north coast. People were saying we’re on the north coast, we got to go.”
I was about fifteen to twenty minutes behind McFarlane in reaching town. (I did not leave Kitamaat Village until after we heard the first tsunami warning.) As soon as I got to back in cell range, my cell phone started to beep with saved messages from my TV and radio news clients calling for information. When I got to my home office, my landline was still dead and would be for about another twenty minutes. The only source of information at that point was Google News, Facebook and Twitter.
I saw the initial, and it turns out general, warning from the Pacific Tsunami Warning Center. Soon I was also getting what I hoped was more specific information on my marine radio from the Canadian Coast Guard Prince Rupert communications station.
But that, too was somewhat confusing. That Coast Guard advisory mentioned various zones, for example, Zone A and Zone B, but there was little specific context and that point I had no idea what Zone A meant. Prince Rupert Coast Guard Radio then went on to say evacuate low lying coastal areas. (transcript below)
With that confusion, and mindful of “when in doubt, leave it out,” I did not mention the zone system in any information I posted on Facebook and Twitter that night. I only retweeted official information or tweets from reporters I knew and trusted (and I did not see any tweeted official information from the province with a link to the page that identifies the official tsunami zones)
From the interview on CFTK, it appears that both the Kitimat and Terrace fire departments were also getting inadequate information.
“We went to our normal place to look EM BC (Emergency Management BC) and there was nothing there,so we went to Plan B to get information and went on from there,” Bossence told Tyler Noble.
Klie said: “We struggle with that every disaster big or small. Social media, I think emergency organizations are trying to tap into more and more. Up north we may be a little behind the eight ball but sure enough Twitter and Facebook information is out there instantly. Looking at Facebook with my son, I saw that they were evacuating whole cities and I knew that was not true. Because of my experience I can filter some of the information, but there is so much information out there that it’s hard to filter what’s real and not real. It’s an area where emergency coordinators have to get into because its the fastest way of getting information out.”
“Once the phone system came back online at the Fire Hall we got a flood of phone calls,” Bossence told CFTK, “it was nonstop and it was people wanting to know. ‘What’s going on? What are we going to do? Are we leaving?’ and they’re giving us ‘This is what is what I’m reading, this is what I’m being texted, on Facebook they’re saying we’re supposed to evacuate’ adding to that we had an individual going around claiming he was a fire department, he was going door to door and telling people to evacuate. That was the added issue we had to deal with. It was definitely misinformation and a sense of urgency that was coming out through the social network (and eventually the media) was big problem for us.”
In Kitimat, I was told about the man going door to door with inaccurate information and as soon as I confirmed it with reliable official sources, I posted that on both Twitter and Facebook, emphasizing there was, at that time, no evacuation order.
But every situation is different. In contrast, in Superstorm Sandy, another story about men going door to door in Williamsburg, a section of Brooklyn was not true, as can be seen in an article summing problems with Twitter in New York, where Jared Keller of Bloomberg reported
I experienced this firsthand during Hurricane Sandy. After retweeting a message warning about muggers in Williamsburg dressed as Con Ed workers as an experiment, I received two sceptical responses checking the claim within 15 minutes, both from people who work in the media industry and spend a significant amount of time on Twitter. Within an hour, I received a mass text message from friends of mine who aren’t completely plugged into the social Web with the same warning: “I just read a news alert of two separate reports of people posing as coned workers, knocking on people’s door and robbing them at gunpoint in Williamsburg. I just want to pass along the info. Stay safe and maybe don’t answer your door.” Two other friends responded with thanks.
Keller goes on to stay “I know a lot of people, especially on Facebook, who end up believing whatever they see first,” says Kate Gardiner, a social media journalist. “It’s almost impossible to track something back to its point of origin there.”
With the earthquake and tsunami warning Saturday night, Twitter misinformation spread internationally. The first hashtag I saw was #bcquake, but as the the tsunami warning gained traction (especially after the warning was extended from BC and Alaska to Washington, Oregon and California and then to Hawaii) the more common hashtag #tsunami became prominent. As people outside BC began tweeting, they began using #Canadaquake and soon #prayforcanada also began to trend. Completely inaccurate information spread on #prayforcanada (believed to have originated in Indonesia) that it was Vancouver, not the north coast that had been hit by the 7.7 magnitude earthquake.
Are you in the Zone?
At this point, one question has to be asked. The spread of information, first the well-intended but wrong, second just rumour and third, the deliberately misleading, has been seen in social media not only during the earthquake and tsunami on the West Coast last weekend, and during Superstorm Sandy on the East Coast but all the way back to the 2004 Christmas tsunami in Southeast Asia.
For the west coast in 2012, however, how much of the problem of misinformation on social media during the earthquake and tsunami warning was the fault of confusing information from the authorities? Just how were people going to interpret such general terms as “north coast” and “low lying areas.”?
From the BC Provincial Emergency Program you have to ask “What is Zone A?” It turns out by checking a day or so later that the province of British Columbia has created Tsunami Identification Zones.
Before October 27, it is likely no one outside of the provincial bureaucracy had ever heard of the provincial tsunami zones. At that time no one in BC, either on Twitter or Facebook or through the media was identifying the BC Tsunami Zones for the public. Later on, the television networks put up maps showing Zones A and B —but that was only good if you had power and were watching the right channel. Kitimat Daily and Terrace Daily posted an official update at 10:42 long after the danger was past explaining the Zone system. It was no good at all if you were listening to news reports on radio or to Prince Rupert Coast Guard Radio on a fishing boat and had no access to the actual maps.
Compounding the confusion is that the US system appears to be very different from the Canadian.
Also the US system has two levels of warning. The Pacific Tsunami Warning Center sends out general warnings but hands over for a more specific warning map from the Alaska -based West Coast and Alaska Pacific Tsunami warning centre. It uses its own system of lettered and numbered zones for the west coast of North America. (See the Oct 27 tsunami advisory here Note it is a Google maps plugin.)
Fisheries management zones as defined by the Department of Fisheries and Oceams (DFO)
So in case of a tsunami warning, Kitimat is in Zone B for the province of British Columbia and the Provincial Emergency Program and in Zone BZ921 for the West Coast and Alaska Tsunami Warning Centre. For the much more familiar fisheries management areas Kitimat is in Zone 6 (which of course has nothing to do with a tsunami, it’s simply the coastal zone system everyone is familiar with)
Adding to the confusion is the fact that the EM British Columbia map shows Terrace, far inland up the Skeena River is considered in Zone A, along with Prince Rupert for tsunami warnings (if a tsunami was big enough to reach Terrace along the Skeena River valley, then I can only assume that much of the west coast of North America would have already been wiped out).
The Monday Post mortem
At the Monday, October 29 post mortem, when McLeod outlined the events of October 27, he began by looking back three weeks, saying, “I have feeling of frustration about a couple of things. October 7, I took 4,000 brochures [How Prepared Are you if Disaster Strikes?] down to the post office to mail out to the residents of Kitimat, They were all delivered by the post office. On Sunday, I had people coming to me and saying what are we supposed to do in the case of an earthquake? It is really, really difficult to get people interested.”
McLeod said that after he felt the earthquake, he went online to check information and then went up to the fire hall, which is Kitimat’s emergency coordination centre. There he met Fire Chief Bossence, his deputy, the RCMP detachment commander Staff Sergeant Steve Corp and representatives from Bechtel and the Rio Tinto Alcan modernization project.
“For the first little while we were going on line trying to get information. The usual method of dissemination getting information it comes from the West coast and Alaska tsunami warning system, then it goes to Victoria, Victoria gives it to the geophysical specialists and they will confirm or deny what ever the information and then it goes to the Provincial Emergency Program and they shoot it out to coastal communities.
“While in this case you’re working with what you find out from different sources and you are trying to determine how reliable these sources are.”
“In our case, for me the first thing you do when you get word of an impending tidal wave [tsunami] action is check the tide. If you’re on a high tide, it’s a different situation than a low tide
“The movie version of a tidal wave is this 50 foot mountain of water roaring along and this is not what is going to happen particularly in Douglas Channel because of the depth. So you are going to see a surge such as we saw in Japan and it will be an increasing surge of water.
“We were told that potentially some sort of surge hitting Langara [the northern most island in Haida Gwaii) at 9:16, 9:16 came and went and there was no notification of a noticeable surge of water. So were down to a non event and we were on a receding tide.” (See advisory below)
“Misinformation going out is not helpful,” McLeod said. “You’ve got to set up a stream of how you get information out to people and it’s a valid point. The District Website, the Facebook page, something like that can get information out. But again if you lose power where do get it? Text can work even locally with cell phones. if you’re in a dead area with a cell phone, you can still get text”
McLeod then asked the audience, mainly people ranging from their thirties to seventies if they text. Only four or five people put up their hands. “You people are going to be saved, the rest of us…” McLeod quipped.
If a conclusion can be drawn from the earthquake and tsunami warning in the Kitimat region on October 27, it’s not just that in an emergency inaccurate, incomplete or malicious information can spread a the speed of light on social media, it’s worse that incomplete, inadequate and confusing information from the authorities is amplified and distorted by rapid posting on social media. That concept is not new for anyone who has tried the phone chain game where the outcome is often completely different from the start.
If Gardiner is correct when she says “I know a lot of people, especially on Facebook, who end up believing whatever they see first,” the BC government delays made everything worse. People Tweeted the first thing they saw and the first thing people saw came from multiple and often conflicting sources. Add that to those Tweets that were exaggeration, rumour and lies.
The problem in 2012 it is not one person talking to one person talking to one person, it is a Tweet or Facebook posting that go out to thousands, or millions of people and that’s a lot more dangerous.
McLeod said the post mortem who said emergency services is trying to get more information out to public, but he added. “The unfortunate part is that if you publish it this week, by Christmas no one will remember. If you start throwing it out every week, it becomes like a stop sign at the end of the street. Nobody sees it.”
(Coming next. If Kitimat had to evacuate)
Transcript of Prince Rupert Coast Guard Radio tsunami warning.
Pan pan. Pan pan. This is Prince Rupert Coast Guard Radio, Prince Rupert Coast Guard Radio. Warning for coastal British Columbia issued by Environment Canada on behalf of the British Columbia Provincial Emergency Program at 2057 Pacific Daylight Time Saturday 27 October. Tsunami warning for Zone A, the north coast and Haida Gwaii,Zone B, the central coast and including Bella Coola, Bella Bella and (unintelligible). A tsunami warning has been issued, if you are in a low-lying area coastal area, you are at risk and must move to higher ground or inland now.
Do not return until directed to do so. Closely monitor local radio stations for additional information from local authorities. Please minimize phone use in affected areas, for further information contact the provincial emergency program at website www. papa echo papa period bravo charlie period charlie alpha.Prince Rupert Coast Guard Radio over.
TSUNAMI BULLETIN NUMBER 003
PACIFIC TSUNAMI WARNING CENTER/NOAA/NWS
ISSUED AT 0341Z 28 OCT 2012
THIS BULLETIN APPLIES TO AREAS WITHIN AND BORDERING THE PACIFIC
OCEAN AND ADJACENT SEAS…EXCEPT ALASKA…BRITISH COLUMBIA…
WASHINGTON…OREGON AND CALIFORNIA.
… TSUNAMI INFORMATION BULLETIN …
THIS BULLETIN IS FOR INFORMATION ONLY.
THIS BULLETIN IS ISSUED AS ADVICE TO GOVERNMENT AGENCIES. ONLY
NATIONAL AND LOCAL GOVERNMENT AGENCIES HAVE THE AUTHORITY TO MAKE
DECISIONS REGARDING THE OFFICIAL STATE OF ALERT IN THEIR AREA AND
ANY ACTIONS TO BE TAKEN IN RESPONSE.
AN EARTHQUAKE HAS OCCURRED WITH THESE PRELIMINARY PARAMETERS
ORIGIN TIME – 0304Z 28 OCT 2012
COORDINATES – 52.9 NORTH 131.9 WEST
DEPTH – 10 KM
LOCATION – QUEEN CHARLOTTE ISLANDS REGION
MAGNITUDE – 7.7
EVALUATION
NO DESTRUCTIVE WIDESPREAD TSUNAMI THREAT EXISTS BASED ON
HISTORICAL EARTHQUAKE AND TSUNAMI DATA.
HOWEVER – THE WEST COAST/ALASKA TSUNAMI WARNING CENTER HAS
ISSUED A REGIONAL WARNING FOR COASTS LOCATED NEAR THE EARTHQUAKE.
THIS CENTER WILL CONTINUE TO MONITOR THE SITUATION BUT DOES NOT
EXPECT A WIDER THREAT TO OCCUR.
THIS WILL BE THE ONLY BULLETIN ISSUED FOR THIS EVENT UNLESS
ADDITIONAL INFORMATION BECOMES AVAILABLE.
THE WEST COAST/ALASKA TSUNAMI WARNING CENTER WILL ISSUE PRODUCTS
FOR ALASKA…BRITISH COLUMBIA…WASHINGTON…OREGON…CALIFORNIA.
BULLETIN
PUBLIC TSUNAMI MESSAGE NUMBER 2
NWS WEST COAST/ALASKA TSUNAMI WARNING CENTER PALMER AK
834 PM PDT SAT OCT 27 2012
THE MAGNITUDE IS UPDATED TO 7.7. THE WARNING ZONE REMAINS THE
SAME.
…THE TSUNAMI WARNING CONTINUES IN EFFECT FOR THE COASTAL
AREAS OF BRITISH COLUMBIA AND ALASKA FROM THE NORTH TIP OF
VANCOUVER ISLAND BRITISH COLUMBIA TO CAPE DECISION
ALASKA/LOCATED 85 MILES SE OF SITKA/…
…THIS MESSAGE IS INFORMATION ONLY FOR COASTAL AREAS OF
CALIFORNIA – OREGON – WASHINGTON AND BRITISH COLUMBIA FROM
THE CALIFORNIA-MEXICO BORDER TO THE NORTH TIP OF VANCOUVER
ISLAND BRITISH COLUMBIA…
…THIS MESSAGE IS INFORMATION ONLY FOR COASTAL AREAS OF
ALASKA FROM CAPE DECISION ALASKA/LOCATED 85 MILES SE OF
SITKA/ TO ATTU ALASKA…
A TSUNAMI WARNING MEANS… ALL COASTAL RESIDENTS IN THE WARNING
AREA WHO ARE NEAR THE BEACH OR IN LOW-LYING REGIONS SHOULD MOVE
IMMEDIATELY INLAND TO HIGHER GROUND AND AWAY FROM ALL HARBORS AND
INLETS INCLUDING THOSE SHELTERED DIRECTLY FROM THE SEA. THOSE
FEELING THE EARTH SHAKE… SEEING UNUSUAL WAVE ACTION… OR THE
WATER LEVEL RISING OR RECEDING MAY HAVE ONLY A FEW MINUTES BEFORE
THE TSUNAMI ARRIVAL AND SHOULD MOVE IMMEDIATELY. HOMES AND
SMALL BUILDINGS ARE NOT DESIGNED TO WITHSTAND TSUNAMI IMPACTS.
DO NOT STAY IN THESE STRUCTURES.
ALL RESIDENTS WITHIN THE WARNED AREA SHOULD BE ALERT FOR
INSTRUCTIONS BROADCAST FROM THEIR LOCAL CIVIL AUTHORITIES.
EARTHQUAKES OF THIS SIZE ARE KNOWN TO GENERATE TSUNAMIS.
AT 804 PM PACIFIC DAYLIGHT TIME ON OCTOBER 27 AN EARTHQUAKE WITH
PRELIMINARY MAGNITUDE 7.7 OCCURRED 25 MILES/40 KM SOUTH OF
SANDSPIT BRITISH COLUMBIA.
EARTHQUAKES OF THIS SIZE ARE KNOWN TO GENERATE TSUNAMIS.
IF A TSUNAMI HAS BEEN GENERATED THE WAVES WILL FIRST REACH
LANGARA ISLAND BRITISH COLUMBIA AT 916 PM PDT ON OCTOBER 27.
ESTIMATED TSUNAMI ARRIVAL TIMES AND MAPS ALONG WITH SAFETY RULES
AND OTHER INFORMATION CAN BE FOUND ON THE WEB SITE
WCATWC.ARH.NOAA.GOV.
TSUNAMIS CAN BE DANGEROUS WAVES THAT ARE NOT SURVIVABLE. WAVE
HEIGHTS ARE AMPLIFIED BY IRREGULAR SHORELINE AND ARE DIFFICULT TO
FORECAST. TSUNAMIS OFTEN APPEAR AS A STRONG SURGE AND MAY BE
PRECEDED BY A RECEDING WATER LEVEL. MARINERS IN WATER DEEPER
THAN 600 FEET SHOULD NOT BE AFFECTED BY A TSUNAMI. WAVE HEIGHTS
WILL INCREASE RAPIDLY AS WATER SHALLOWS. TSUNAMIS ARE A SERIES OF
OCEAN WAVES WHICH CAN BE DANGEROUS FOR SEVERAL HOURS AFTER THE
INITIAL WAVE ARRIVAL. DO NOT RETURN TO EVACUATED AREAS UNTIL AN
ALL CLEAR IS GIVEN BY LOCAL CIVIL AUTHORITIES.
PACIFIC COASTAL REGIONS OUTSIDE CALIFORNIA/ OREGON/ WASHINGTON/
BRITISH COLUMBIA AND ALASKA SHOULD REFER TO THE PACIFIC TSUNAMI
WARNING CENTER MESSAGES FOR INFORMATION ON THIS EVENT AT
PTWC.WEATHER.GOV.
THIS MESSAGE WILL BE UPDATED IN 30 MINUTES OR SOONER IF
THE SITUATION WARRANTS. THE TSUNAMI MESSAGE WILL REMAIN
IN EFFECT UNTIL FURTHER NOTICE. FOR FURTHER INFORMATION STAY TUNED
TO NOAA WEATHER RADIO… YOUR LOCAL TV OR RADIO STATIONS… OR SEE
THE WEB SITE WCATWC.ARH.NOAA.GOV.
$$
Did the media over react to the earthquake and tsunami warning?
There were also numerous Tweets on October 27, accusing the media of over reacting. The Haida Gwaii quake was 7.7 magnitude. Compare that to the Haiti earthquake on January 12, 2010 which was 7.0. The Christ Church, New Zealand earthquake on February 27, 2011 which caused major damage was 6.3 magnitude. So the Haida Gwaii earthquake was a major event. The tsunami warning that eventually reached as far off as Hawaii had to be taken seriously.
Fortunately Haida Gwaii is sparsely populated and there was minimal damage largely because most of the houses and buildings are wood and can absorb some of the shaking from an earthquake.
Given the tsunami damage in Southeast Asia in 2004 and in Japan in 2011, no media organization could ignore the developing story.
If there is justifiable criticism, it is that some media over hyped the story in the beginning, rather acting to reassure the public in a responsible manner. But the media that over hyped the earthquake and tsunami are the kind that would over hype any story. That is generally the result of management listening to “TV doctors” and media consultants who urge over hyping to increase ratings. (It often works). But those who, quite early in the event, who tweeted that the media was overreacting, were themselves guilty of overreaction in their Tweets.
The Northern Gateway Joint Review panel has allowed the Department of Fisheries and Oceans and Natural Resources Canada to delay a report on historic tsunamis and a possible fault line on Douglas Channel until November 16, 2012.
The report was scheduled for release on October 31.
In a ruling released by the JRP on November 1, the panel noted:
In Ruling no. 105 dated 24 September 2012, the Panel stated that the Department of Fisheries and Oceans (DFO) could provide “modelling of the potential wave heights and speeds that may have resulted from two previously unrecognized submarine slope failures in the Douglas Channel” (Modelling) and that it should do so by 31 October 2012. The letter from Justice Canada seeks an extension to 16 November 2012 as DFO “requires additional time to complete the peer review and approval processes related to this additional written evidence.”
The Panel believes the Modelling to be relevant, as noted in Ruling no. 105. The Panel is also ofthe view that there is unlikely to be any undue prejudice to any party by permitting its filing to be delayed to 16 November 2012.
Accordingly, the Federal Government Participants’ motion is granted and DFO is permitted to file the Modelling on or before 16 November 2012
The Department of Justice filed the request with the JRP on Monday Oct. 30, 2012, less than 48 hours after a major earthquake of magnitude 7.7 struck off Haida Gwaii just after 8 p.m. Pacific Daylight Time, on Saturday Oct. 27, shaking much of northern BC. There have been numerous aftershocks since the main quake.
As a 7.7 magnitude earthquake hit off Haida Gwaii shortly after eight o’clock on Saturday, I was at the Haisla Recreation Centre as the Haisla Nation marked the return of the G’ps Golox totem pole. Like a boat being lifted by gentle waves, the Rec Centre began to quietly roll up and down, then the rolling seemed to accelerate just a bit. I realized that it was an earthquake. As I told CBC’s Ian Hanomansing later in the evening, I have been in a number of earthquakes, and for me at least, this quake, at least at Kitamaat Village, the rec centre was not shaking as badly as in some of the others I have felt.
The subsequent events of the evening show that the emergency communication system in Kitimat needs immediate improvement.
Now as a former network producer for both CBC and CTV I have handled a large number of earthquake stories from around the world over the past quarter century (sitting at a desk, I should add). With that experience, I was hoping to get a cell hit at the village so I could bring up Twitter. I already subscribe to the US Geological Survey and Canadian earthquake alert feeds. The US and Canadian computers automatically report earthquakes within seconds of detection and send out a Twitter bulletin as the same time as those computers are alerting their human masters. If I had been able to get cell service I would have known within minutes that the Haida Gwaii earthquake was a major event. (I did follow the alerts from my computer once I got back to Kitimat itself).
Recommendation One. Cell service in Kitimat, Kitamaat Village, the harbour area must be upgraded as soon as possible. Telus has applied to council to erect a new cell tower here. Given the events of the past 24 hours, District Council should make sure that all parts of the District of Kitimat and the Haisla Nation have proper cell coverage no matter what service one subscribes to, not just for the convenience of subscribers but for emergency situations.
Automatic alerts
With experience one knows that in a situation such as Saturday night, the official websites such as the US Geological Survey and the Pacific Tsunami Warning Center as well as Natural Resources Canada are often overwhelmed. That is why the media use RSS feeds, Twitter feeds and e-mail alerts. It is also important to realize that these emergency organizations have their own language and procedures. It appears that a lot of the confusion on Saturday came from misinterpretation of the various Canadian and US warning systems.
Recommendation Two. If Kitimat emergency services are not familiar with how the US based earthquake and tsunami centres work, they should be trained in those systems, simply because the Americans are well ahead of Canada in these areas because the alerts go out by computer automatically and are constantly updated and as Saturday night showed, are often quicker and farther ahead than the Canadian systems.
Once I was back in Kitimat, it was clear that communications were breaking down, and this was at a time the tsunami warning was still active. There were numerous messages on Twitter and Facebook, from residents of Kitimat either trying to find out what was going on or retweeting/reposting rumours including one that the Kildala neighbourhood was being evacuated. I am told that residents were calling the RCMP to ask what was going on. This was another breakdown since North District HQ in Prince George handles all police services in this region and were likely busy with quake calls on Haida Gwaii, so that information calls in Kitimat that should have been handled by an emergency services public communications person were being handled the Mounties.
There were reports that one man was going door to door in Kildala telling people to evacuate. Whether this person was well intentioned but misinformed or a imposter intent on mischief doesn’t matter, there was an information vacuum.
It was clear from Twitter that other districts and municipalities were using that service to spread official information. (I don’t follow other areas on Facebook so it is unclear if information was being posted on Facebook. There was certainly no official presence from Kitimat on Facebook Saturday night.) It appears from reports in the Kitimat Daily and tweets about the Northern Sentinel that Kitimat emergency services was sending information out by fax. While faxing information was an advance in the 1980s, faxes are obsolete in 2012. Many major newsrooms no longer use fax machines after being inundated by junk faxes and after they laid off all the editorial assistants who would have cleared those fax machines (even by the late 90s most faxes were dumped in the garbage unless the EA had been told to look for a specific fax). Also though it is now more than two years since I returned to Kitimat and I regularly freelance for Global, CBC and Canadian Press, I had no contact from anyone in emergency services (also I don’t have a fax machine).
Recommendation Three: The District of Kitimat must immediately bring its emergency communications into the 21st century, with Twitter accounts, a Facebook page and an emergency e-mail or text message plan for media and other officials who can get the messages. ( A number of jurisdictions already use text messages for emergency alerts at various graduated levels, official, media, public). When the main means of communication today is social media, an emergency organization can no longer follow outdated procedures, an organization must be on social media immediately it becomes clear that there is an emergency (as we are seeing with all the official tweets with the Hurricane Sandy crisis on the east coast)
CFTK
In an emergency situation, local radio and television are vital to communications and letting people know what is going on.
The inadequate coverage of the quake was certainly not the fault the of the current CFTK news staff who were working hard (probably on their own time and unpaid) keeping Twitter updated with what they knew. The fault lies with corporate management across the media which these days doesn’t want to spend the money and resources and training to fulfill the public service portion of their broadcast licence mandate.
(There was a similar breakdown in the May 2000, Walkerton, Ontario e-coli crisis where the local medical officer of health was initially unable to alert the public because local radio wasn’t staffed on the weekends–the local stations were taking satellite feeds from their corporate headquarters)
In 1964, long before satellites, when the microwave towers that joined CFTK to the Canadian networks were still being built, the staff of CFTK, then, of course under local management, went to a live special within an hour of the Anchorage quake being felt far off from Alaska in Kitimat. The CFTK anchors were keeping its audience updated with “rip and read” wire copy, a camera on an atlas for a map and phone interviews.
In contrast, on this Saturday night, CFTK was taking the CBC BC network feed which was a hockey rerun (hardly a show that attracts major audience numbers and certainly not a vital broadcast) until the CBC management in Vancouver decided to go to full network news special.
Since CFTK is the station that broadcasts not only to Kitimat, but to Haida Gwaii as well, CFTK should have been ahead of Vancouver on this story, called in its staff and mounted their own live special, joining the CBC feed when it began but, as on an election night, breaking away for local news when justified. CFTK has a responsibility under its licence from the CRTC to provide that service to the northwestern region, not just sending what ad revenue it generates back to Astral.
Rio Tinto Alcan
Another question that must be asked in this situation is where was Rio Tinto Alcan on Saturday night? In all areas that were under a tsunami warning the first scrutiny and clue if there was to be a problem is that region would be found by observing what has happening between the low tide line and the maximum hide tide line. In Prince Rupert, from the Twitter feeds I saw, public officials were monitoring the waterfront and the tide lines and updating the public. RTA has all the advantages of the private port of Kitimat. It appears that monitoring the water level at the tide lines at the port of Kitimat was the responsibility of Plant Protection. Was RTA communicating what was happening with emergency services? Since RTA runs the private port, unlike in other jurisdictions, RTA had a responsibility to the people of Kitimat to report promptly to the public the conditions on the waterfront. Corporate public relations cannot just be sending out news releases with “good news.” That means that RTA public relations should have used its corporate Twitter account which usually sends out a news release every few weeks, to keep Kitimat updated on a minute-by-minute basis. If RTA communications staff in Kitimat do not have access to the RTA corporate Twitter account, they should establish their own local Twitter feed.
Both in 1964 and in 2012, the tsunami that came up Douglas Channel was minimal. But we know that this region does have a record of major quakes and that Douglas Channel has also experienced major landslides that can, in some circumstances, trigger a tsunami without an earthquake. The next few years will be seeing more industrial development along Douglas Channel which can also bring other hazards to the Kitimat region. While there are always communications breakdowns in situations like happened on Saturday, it is clear that the Kitimat emergency communications system needs a major upgrade to make sure the public is informed quickly and accurately of what is going on.
A map from TransCanada’s Coastal GasLink showing the conceptual route of the proposed natural gas pipeline from the shale gas fields in northeastern BC through the mountains to Kitimat and the proposed Shell LNG facility. (TransCanada)
TransCanada plans a rugged over-mountain route for its proposed Coastal Gaslink pipeline to the Shell Canada liquified natural gas project in Kitimat, BC, company officials said Monday, Oct. 15, 2012, in two presentations, one to District of Kitimat Council and a second at a community town hall briefing.
The pipeline would initially carry 1.7 billion cubic feet of natural gas per day from the Montney Formation region of northeastern British Columbia along a 48 inch (1.2 metre) diameter pipe over 700 kilometres from Groundbirch, near Dawson Creek, to Kitimat, site of the proposed Shell Canada LNG Canada project.
Rick Gateman, President of Coastal GasLink Project, a wholly owned TransCanada subsidiary told council that the project is now at a “conceptual route” stage because TransCanada can’t proceed to actual planning until it has done more detailed survey work and community consultations.
At the same council meeting, documents from Shell Canada notified the District that it has formally applied to the National Energy Board for an export licence for the natural gas.
Rick Gateman, president of TransCanada’s Coastal GasLink addresses District of Kitimat Council, Oct. 15, 2012. (Robin Rowland)
Gateman told council that since the pipeline itself will be completely within the province of British Columbia, it comes under the jurisdiction of the British Columbia Environmental Assessment process and the BC Oil and Gas Commission and that the NEB will not be involved in approving the pipeline itself.
At first, the Coastal Gas Link pipeline would be connected to the existing Nova Gas Transmission system now used (and being expanded) in northeastern British Columbia.
From Vanderhoof, BC to west of Burns Lake, the Coastal GasLink pipeline would be somewhat adjacent to existing pipelines and the route of the proposed Enbridge Northern Gateway bitumen pipeline and the proposed Pacific Trails natural gas pipeline.
Somewhat south of Houston, however, the pipeline takes a different route from the either the Northern Gateway or Pacific Trails Pipeline, going southwest, avoiding the controversial Mount Nimbus route.
Howard Backus, an engineering manager with TransCanada told council that the route changes so that Coastal GasLink can avoid “congestion” in the rugged mountain region.
Backus said that the Pacific Trails Pipeline for Apache and its partners in the Kitimat LNG project “is skirting” Nimbus while Enbridge plans to tunnel through the mountain. That tunnel is one of the most controversial aspects to the Northern Gateway project. The local environmental group Douglas Channel Watch has repeatedly warned of the dangers of avalanche and geological instability in the area where the Northern Gateway pipeline emerges from the tunnel. Enbridge has challenged Douglas Channel Watch’s conclusions in papers filed with the Northern Gateway Joint Review panel.
Under TransCanada’s conceptual route, the pipeline heads southwest and then climbs into the mountains, crossing what Backus calls “a saddle” (not a pass) near the headwaters of the Kitimat River. The pipeline then comes down paralleling Hircsh Creek, emerging close to town, crossing the Kitimat River and terminating at the old Methanex plant where Shell plans its liquified natural gas plant. (That means that if the conceptual plans go ahead, the TransCanada pipeline would climb into the mountains, while Pacific Trails finds a way around and Enbridge tunnels).
Backus told council that going north “created more issues,” but did not elaborate.
Backus assured people at the town hall that energy companies have a lot of experience in building pipelines in mountainous areas, including the Andes in South America.
Asked by a local businessman at the town hall if it was possible to build a road along the route of the pipeline, Backus said the mountain areas would be too steep. Any pipeline maintenance would have to be done by tracked vehicle, he said.
Gateman told council that the pipeline would be buried along its entire route. If Shell increases the capacity of its LNG facility in Kitimat, the Coastal Gaslink pipeline could increase to 3.4 billion cubic feet a day or perhaps even more. For the initial capacity, the company will have one compressor station at the eastern end of the line. If capacity increases or if the route requires it, there could be as many as five additional compressor stations. (TransCanada’s long term planning is based on the idea that Shell will soon be adding natural gas from the rich Horn River Formation also in northeastern BC to the Kitimat export terminal.)
TransCanada will begin its field work, including route and environmental planning and “community engagement” in 2013 and file for regulatory approval in 2014. Once the project is approved, construction would begin in 2015.
Gateman said that TransCanada is consulting landowners along the proposed right of way and “on a wide area on either side.” The company also is consulting 30 First Nations along the proposed route. Gateman told council, “We probably have the most experience of any number of companies in working directly with and engaging directly with First Nations because of our pipelines across Canada.”
(Despite Gateman’s statement, the TransCanada maps showed that the Coastal Gaslink Pipeline would cross Wet’suwet’en traditional territory and officials seemed to be unaware of the ongoing problems between Apache and the Pacific Trails Pipeline and some Wet’suwet’en Houses who oppose that pipeline).
Gateman told council that the pipeline would be designed to last at least 60 years. He said that in the final test stages, the pipeline would be pressured “beyond capacity” using water rather than natural gas to try and find if any leaks developed during construction.
He said that the company would restore land disrupted by the construction of the pipeline, but noted that it would only restore “low-level vegetation.” Trees are not permitted too close to the pipeline for safety reasons.
TransCanada made the usual promises the region has heard from other companies of jobs, opportunities for local business and wide consultations. (TransCanada may have learned lessons from the botched public relations by the Enbridge Northern Gateway. A number of Kitimat residents have told Northwest Coast Energy News that TransCanada was polling in the region in mid-summer, with callers asking many specific questions about environment and the spinoffs for communities).
Councillor Phil Germuth questioned Gateman about the differences between a natural gas pipeline and a petroleum pipeline. Gateman replied that the pipelines are pretty much the same with the exception that a natural gas pipeline uses compressor stations while a petroleum pipeline uses pumping stations. Gateman did note that the original part of the controversial Keystone XL pipeline that would carry bitumen through Alberta and US mountain states to Texas was a natural gas pipeline converted to carry the heavier hydrocarbons.
Although the natural gas projects have, so far, enjoyed wide support in northwestern British Columbia, environmental groups and First Nations have raised fears that sometime in the future, especially if there is overcapacity in natural gas lines, that some may converted to bitumen, whether or not Northern Gateway is approved and actually goes ahead.
Shell application to NEB
In a fax to District of Kitimat council, Shell Canada Senior Regulatory Specialist Scot MacKillop said that the Shell had applied to the National Energy Board on September 25, 2012 for a licence to export LNG via Kitimat for the next 25 years.
The Shell proposal, like the previous Kitimat LNG and BC LNG proposals, are export applications, unlike the Enbridge Northern Gateway which is a “facility application.”
In its letter to Shell’s lawyers, the NEB took pains to head off any objections to the project on environmental or other grounds by saying:
the Board will assess whether the LNG proposed to exported does not exceed the surplus reaming after due allowance has been made for the reasonably foreseeable requirements for use in Canada. The Board cannot consider comments that are unrelated…such as those relating to potential environmental effects of the proposed exportation and any social effects that would be directly related to those environmental effects.
A new draft report for the U.S. Congress from the United States Pipeline and Hazardous Materials Safety Administration takes new aim at Enbridge for failures in its pipeline leak detection and response system.
Not that the PHMSA is singling out Enbridge, the report is highly critical of leak detection systems on all petroleum and natural gas pipeline companies, saying as far as the United States is concerned, the current pipeline standards are inadequate.
The release of the “Leak Detection Report” written by Kiefner & Associates, Inc (KAI) a consulting firm based in Worthington, Ohio, comes at a critical time, just as Enbridge was defending how it detects pipeline leaks before the Joint Review Panel questioning hearings in Prince George, where today Enbridge executives were under cross-examination by lawyers for the province of British Columbia on how the leak detection system works.
In testimony on Wednesday, October 12, Enbridge engineers told the Joint Review Panel that the company’s pipelines are world-class and have a many prevention and detection systems.
Northern Gateway president John Carruthers testifed there is no way to eliminate all the risks but the company was looking for the best way of balancing benefits against the risk.
However, the KAI report points out that so far, all pipeline company cost-benefit analysis is limited by a short term, one to five year point of view, rather than looking at the entire lifecycle of a pipeline.
Two Enbridge spills, one the well-known case in Marshall Michigan which saw bitumen go into the Kalamazoo River and a second in North Dakota, both in 2010, are at the top of the list in the study for PHMSA by the consulting firm.
The second spill, in Neche, North Dakota, which, unlike the Marshall spill, has had little attention from the media, is perhaps equally damning, because while Enbridge’s detection systems worked in that case–the KAI report calls it a “text book shutdown”– there was still a spill of 158,928 gallons (601,607 litres) of crude oil, the sixth largest hazardous liquid release reported in the United States [between 2010 and 2012] because Enbridge “did not plan adequately for containment.”
(The KAI report also examines problems with natural gas pipelines, including one by TransCanada Northern Border line at Campbell, Wyoming in February 2011. Northwest Coast Energy News will report on the natural gas aspects of the report in a future posting.)
The highly technical, 270-page draft report was released on September 28, as Enbridge was still under heavy criticism from the US National Transportation Safety Board report on the Marshall, Michigan spill and was facing penalties from the PHMSA for both the Marshall spill and a second in Ohio.
Looking at overall pipeline problem detection, KAI says the two standard industry pipeline Leak Detection Systems or LDS didn’t work very well. Between 2010 and 2012, the report found that Computational Pipeline Monitoring or CPMs caught just 20 per cent of leaks. Another system, Supervisory Control and Data Acquisition or SCADAs caught 28 per cent.
Even within those acronym systems, the KAI report says major problem is a lack of industry standards. Different companies use different detector and computer systems, control room procedures and pipeline management.
The report also concludes that the pipeline industry as a whole depends far too much on internal detectors, both for economic reasons and because that’s what the industry has always done. External detectors, the report says, have a better track record in alerting companies to spills.
A significant number of spills are also first reported by the public or first responders, rather than through the pipeline company system and as KAI says of Enbridge, “Operators should not rely on the public to tell them a pipeline has ruptured.”
The consultants also say there are far too many false alarms in spill detection systems.
Although the KAI report concentrates on the United States, its report on Enbridge does raise serious questions about how the company could detect a pipeline breach or spill in the rugged northern British Columbia wilderness where the Northern Gateway Pipeline would be built, if approved by the federal government.
The report comes after the United States Congress passed The Pipeline Safety, Regulatory Certainty, and Job Creation Act, which was signed into law by President Barack Obama on January 3, 2012. The law called on a new leak detection study to be submitted to Congress that examines the technical limitations of current leak detection systems, including the ability of the systems to detect ruptures and small leaks that are ongoing or intermittent. The act also calls on the US Department of Transportation to find out what can be done to foster development of better technologies and economically feasible ways of detecting pipeline leaks. The final report must be submitted to Congress by January 3, 2013.
(The draft report does note in some ways, Canadian standards for detecting pipeline leaks are better than those in the United States. For example, Canada requires some pipeline testing every year, the United States every five years. It also finds European pipeline monitoring regulations also surpass those in the United States).
The spills studied in the report all found weaknesses in one or more of those three areas: people, company procedures and the technology. It appears that the industry agrees, at least in principle, with executives telling the consultants:
The main identified technology gaps – including those identified by operators – include: reduction or management of false alarms; applicable technical standards and certifications; and value / performance indicators that can be applied across technologies and pipelines.
The report echoes many of the findings of the US National Transportation Safety Board in its examination of the Enbridge Marshall, Michigan spill but it applies to all pipeline companies, noting:
Integration using procedures is optimal when it is recognized that alarms from the technology are rarely black-and-white or on/off situations. Rather, at a minimum, there is a sequence: leak occurrence; followed by first detection; followed by validation or confirmation of a leak; followed by the initiation of a shutdown sequence. The length of time that this sequence should take depends on the reliability of the first detection and the severity of the consequences of the release. Procedures are critical to define this sequence carefully – with regard to the technology used, the personnel involved and the consequences – and carefully trained Personnel are needed who understand the overall system, including technologies and procedures.
We note that there is perhaps an over-emphasis of technology in LDS. A recurring theme is that of false alarms. The implication is that an LDS is expected to perform as an elementary industrial automation alarm, with an on/off state and six-sigma reliability. Any alarm that does not correspond to an actual leak is, with this thinking, an indicator of a failure of the LDS system.
Instead, multiple technical studies confirm that far more thought is required in dealing with leak alarms. Most technologies infer the potential presence of a leak via a secondary physical effect, for example an abnormal pressure or a material imbalance. These can often be due to multiple other causes apart from a leak.
The report takes a critical look at the culture of all pipeline companies which divides problems into leaks, ruptures and small seeps. Under both pipeline practice and the the way problems are reported to the PHMSA in the US a “rupture is a situation where the pipeline becomes inoperable.” While a rupture means that a greater volume of petroleum liquid or natural gas is released, and is a higher priority than a leak or seep, the use of language may mean that there is a lower priority given to those leaks and seeps than the crisis created by a rupture.
(Environmental groups in British Columbia have voiced concerns about the cumulative affect of small seeps from the Enbridge Northern Gateway that would be undetectable under heavy snow pack either by an internal system or by external observation)
Overall, the report finds serious flaws to the way pipeline companies are conducting leak detection systems at the moment, including:
Precisely the same technology, applied to two different pipelines, can have very different results.
Leak Detection Systems do not have performance measures that can be used universally across all pipelines. Compounding the problem are different computer systems where software, program configuration and parameter selection all contribute, in unpredictable ways, to overall performance.
Many performance measures present conflicting objectives. For example, leak detection systems that are highly sensitive to small amounts of lost hydrocarbons are also prone to generating more false alarms.
The performance of a leak detection system depends critically on the quality of the engineering design, care with installation, continuing maintenance and periodic testing.
Even though an internal technology may rely upon simple, basic principles, it is in fact, complex system that requires robust metering, robust SCADA and telecommunications, and a robust computer to perform the calculations. Each of these subsystems is individually complex.
Near the inlet and the outlet of the pipeline a leak leads to little or no change in pressure. Flow rates and pressures near any form of pumping or compression will generally be insensitive to a downstream leak
Differences in any one of these factors can have a dramatic impact on the ultimate value of a leak detection system.
The report goes on to say:
There is no technical reason why several different leak detection methods can not be implemented at the same time. In fact, a basic engineering robustness principle calls for at least two methods that rely on entirely separate physical principles.
The report strongly recommends that pipeline companies take a closer look at external leak detection systems. Even though the US Environmental Protection Agency began recommending the use of external detection as far back as 1988, the companies have resisted due to the cost of retrofitting the legacy pipeline network. (Of course if the pipeline companies had started retrofitting with external detectors in 1988 they would be now 24 years into the process).
KAI says:
External leak detection is both very simple – relying upon routinely installed external sensors that rely upon at most seven physical principles – and also confusing, since there is a wide range of packaging, installation options, and operational choices to be considered.
External leak detection sensors depend critically on the engineering design of their deployment and their installation.
External sensors have the potential to deliver sensitivity and time to detection far ahead of any internal system.
Most technologies can be retrofitted to existing pipelines. In general, the resistance to adopting external technologies is, nevertheless, that fieldwork on a legacy pipeline is relatively expensive.
The report goes on to identify major bureaucratic roadblocks within pipeline companies. Like many other big corporations, walls exist that prevent the system from working well
A particular organizational difficulty with leak detection is identifying who “owns” the leak detection system on a pipeline. A technical manager or engineer in charge is typically appointed, but is rarely empowered with global budgetary, manpower or strategic responsibilities. Actual ownership of this business area falls variously to metering, instrumentation and control, or IT.
The report calls for better internal standards at pipeline companies since with leak detection “one size does not necessarily fit all”.
It also notes that “flow metering is usually a central part of most internal leak detection systems,” but adds “flow meter calibration is by far the most laborious part of an internal system’s maintenance.
Also, the central computer and software technology usually has maintenance requirements far greater than most industrial automation and need special attention.”
While a company may do a cost benefit analysis of its leak detection system and risk reduction system it will generally emphasize the costs of the performance and engineering design of the leak detection system, the companies usually place less emphasis on the benefits of a robust system, especially the long term benefits.
At present the pipeline companies look at the benefit of leak detection as a reduction in risk exposure, or asset liability, “a hard, economic definition… understood by investors.” But the report adds that leak detection systems have a very long lifetime and over that life cycle, the cost-benefit approaches the reduction in asset liability caused by the system, when divided by annual operational costs. However, since pipeline companies budget on a one to five year system the long term benefit of robust, and possibly expensive spill detection is not immediately apparent.
Enbridge
The consultants studied 11 US oil spills, the top two with the greatest volume were from Enbridge pipelines. The others were from TE Products Pipeline, Dixie Pipeline, Sunoco, ExxonMobil, Shell, Amoco, Enterprise Products, Chevron and Magellan Pipeline. Not all US spills were used in the KAI report, the 11 were chosen for availability of data and documentation.
The largest spill in the KAI study was the pipeline rupture in Michigan at 843,444 gallon (3,158,714 litres) which has been the subject of continuing media, investigative and regulatory scrutiny. The second spill in North Dakota, has up to now received very little attention from the media. That will likely change once the US Congress gets the final report. Even though the Neche, North Dakota spill, has been described as “text book case” of a pipeline shutdown, there was still a large volume of oil released.
Marshall, Michigan spill
On the Marshall, Michigan spill that sent bitumen into the Kalamazoo River the report first goes over the facts of the 843,444 gallon spill and the subsequent release of a highly critical report from the US National Transportation Safety Board. It then looks at the failures of Enbridge’s detection system from the point of view mandated for the report to Congress:
The pipeline was shutting down when the ruptured occurred. Documentation indicates that a SCADA alarm did sound coincident with the most likely time of the rupture. It was dismissed. The line was shut down for around 10 hrs and crude oil would have drained from the line during this time.
On pipeline start up, alarms in the control room for the ruptured pipeline sounded. They were dismissed. This was repeated two more times. The pipeline was shut down when the control room was notified of the discharge of the crude oil by a member of the public. The time to shut down the pipeline is not relevant here because of the 17 hours that elapsed after the rupture occurred.
The review identified issues at Enbridge relevant to this Leak Detection Study:
1. Instrumentation on a pipeline that informs a controller what is happening to the pipeline must be definitive in all situations.
2. However, the instrumentation did provide warnings which went unheeded by controllers.
3. Instrumentation could be used to prevent a pump start up.
4. Operators should not rely on the public to tell them when a pipeline has ruptured.
5. Pipeline controllers need to be fully conversant with instrumentation response to different operations performed on the pipeline.
6. If alarms can be cancelled there is something wrong with the instrumentation feedback loop to the controller. This is akin to the low fuel warning on a car being turned off and ignored. The pipeline controller is part of an LDS and failure by a controller means the LDS has failed even if the instrumentation is providing correct alarms.
7. If the first SCADA alarm had been investigated, up to 10 hours of pipeline drainage to the environment might have been avoided. If the second alarm had been investigated, up to 7 hours of pumping oil at almost full capacity into the environment might have been avoided.
8. CPM systems are often either ignored or run at much higher tolerances during pipeline start ups and shutdowns, so it is probable that the CPM was inoperative or unreliable. SCADA alarms, on the other hand, should apply under most operating conditions.
Neche, North Dakota spill
At approximately 11:37 pm. local time, on January 8, 2010, a rupture occurred on Enbridge’s Line 2, resulting in the release of approximately 3000 barrels or 158,928 gallons of crude oil approximately 1.5 miles northeast of the town of Neche, North Dakota, creating the sixth largest spill in the US during the study period.
As the report notes, in this case, Enbridge’s detection system worked:
At 11:38 pm., a low-suction alarm initiated an emergency station cascade shutdown. At 11:40 pm., the Gretna station valve began closing. At 11:44 pm., the Gretna station was isolated. At 11:49 pm., Line 2 was fully isolated from the Gretna to Donaldson pump stations.
Documentation indicates a rapid shut down on a low suction alarm by the pipeline controller. From rupture to shut down is recorded as taking 4 minutes. The length of pipeline isolated by upstream and downstream remotely controlled valves was 220,862 feet. The inventory for this length of line of 26-inch diameter is 799,497 gallons. The release amount was around 20 per cent of the isolated inventory when the pipeline was shut down.
The orientation of the 50-inch long rupture in the pipe seam is not known. The terrain and elevation of the pipeline is not known. The operator took around 2 hours and 40 minutes to arrive on site. It is surmised that the rupture orientation and local terrain along with the very quick reactions by the pipeline controller may have contributed to the loss of around 20 per cent of the isolated inventory.
The controller was alerted by the SCADA. Although a CPM system was functional the time of the incident it did not play a part in detecting the release event. It did provide confirmation.
But the KAI review identified a number of issues, including the fact in item (7) Enbridge did not plan for for containment and that containment systems were “under-designed.”
1. This release is documented as a text book shut down of a pipeline based on a SCADA alarm.
2. The LDS did not play a part in alerting the pipeline controller according to
documentation. However, leak detection using Flow/Pressure Monitoring via SCADA
worked well.
3. Although a textbook shut down in 4 minutes is recorded, a large release volume still occurred.
4. The release volume of 158,928 gallons of crude oil is the sixth largest hazardous liquid release reported between January 1, 2010 and July 7, 2012.
5. The length of pipeline between upstream and downstream isolation valves is long at 41.8 miles.
6. If not already performed, the operator should review potential release volumes based on ruptures taking place at different locations on the isolated section.
7. The success of a leak detection system includes planning for the entire process: detection through shutdown through containment. In this case, the operator did not plan adequately for containment so that although the SCADA leak detection technology, the controller and the procedures worked well, the containment systems (isolation valves) were under-designed and placed to allow a very large spill.”
A map from the Geological Survey of Canada showing the line of a possible seismic fault on Douglas Channel (Geological Survey of Canada)
Updates with statement from Natural Resources Canada, new filings by Enbridge Northern Gateway and the Attorney General of Canada (in box below)
The Geological Survey of Canada has identified a tsunami hazard and a possible seismic fault in Douglas Channel near Kitimat. A scientific paper by the Geological Survey and the Department of Fisheries and Oceans says there were once two giant landslides on Douglas Channel that triggered major tsunamis and that the landslides were possibly caused by an earthquake on the fault line.
Kitimat is the proposed site of the Enbridge Northern Gateway project and at least three liquified natural gas projects.
If the projects go ahead, hundreds of supertankers with either bitumen or LNG will be sailing in the channel for years to come.
A filing by the Attorney General of Canada with the Northern Gateway Joint Review Panel is asking the JRP for leave to file late written evidence long after the original deadline of December 2011. The Attorney General’s motion was filed on August 17, but went unnoticed until the Kitimat environmental group Douglas Channel Watch brought the matter up with District of Kitimat Council tonight (Sept. 17).
Appended to the Attorney General’s motion is a copy of a scientific paper from the Geological Survey “Submarine slope failures and tsunami hazards in coast British Columbia: Douglas Channel and Kitimat Arm” by Kim W Conway, J.V. Barrie of the Geological Survey and Richard E. Thomson of the Department of Fisheries and Oceans.
The report says the scientists discovered “evidence of large submarine slope failures in southern Douglas Channel.”
It goes on to say: “The failures comprise blocks of bedrock and related materials that appear to have been detached directly from the near shore off Hawkesbury Island.” Hawkesbury Island and many of the other islands in Douglas Channel are built up with material left over from the ice age glaciers and thus are vulnerable to displacement and landslides.
The research identified two slides, one estimated at 32 million cubic metres and a second of 31 million cubic metres. The report goes on to say that the discovery of an “apparently active fault presents the possibility that they may have been triggered by ground motion or surface rupture of the fault during past earthquake events.”
The slope failure landslides are covered with thick layers of mud, and that, the scientists say, could mean that the failures could be ancient, possibly occurring 5.000 to 10,000 years ago. Further research is needed to confirm the date of the giant slides.
What is worrying about the discovery is that fact that there were two recent submarine slope failures on the Kitimat Arm of Douglas Channel. both creating tsunamis. The first slope failure occurred on October 17, 1974, triggering a 2.4 metre tsunami at low tide. Then on April 27, 1975 there was a second slope failure near low tide on the northeast slope of the Kitimat Arm that generated an 8.2 metre tsunami. The 1975 tsunami destroyed the Northland Navigation dock near Kitimat and damaged the Haisla First Nation docks at Kitamaat Village.
The paper says that “Additional geological research is required to better delineate the age of the submarine failures, their triggers, and their mechanisms of emplacement.”
Urgent new research is underway and the filing by the Attorney General says when the Department of Justice requested leave to file late evidence says it anticipates that the further research by DFO is expected to be completed by November 1. The Natural Resources Canada Earth Sciences Sector began a national assessment of submarine slope failures in Canada in late 2011 and completion of the Pacific portion of this assessment is targeted for December of 2012.
The Attorney General’s filing says that DFO is now modelling “potential wave heights and speeds that may have resulted from the two previously unrecognized submarine slope failures in the Douglas Channel.” The model will use high resolution scans of the Douglas Channel seafloor to create the models.
The survey of Douglas Channel in 2010 suggests the possible existence of a fault immediately to the south of the second ancient slide on Hawkesbury Island.
The GSC paper says that evidence for a continuous fault was observed by aligned stream beds and fractures on the south end of Hawkesbury Island, about four kilometers from the site of the second ancient slide. The possible fault then appears to terminate far to the south near Aristazabal Island on the Inside Passage. The Geological Survey says that eleven small earthquakes, all less than magnitude three, have appeared with 20 kilometres of the suspected fault over the past 25 years.
The paper says that the scientists conclude that the slides appear to have left very steep slopes at or near the shoreline that could be susceptible to future failure events.
A large potential slope failure has been identified near one of the ancient slides….
in the absence of additional evidence, the fault must be considered a potential trigger for the submarine failure events….the triggers for the failures have not been defined; however, their proximity to a potentially active fault represents one potential source. The failures probably generated tsunamis during emplacement and conditions exist for similar failures and associated tsunamis to occur along this segment of Douglas Channel in the future.
The scientists say that detailed tsunami modelling is underway to
provide an improved understanding of the generation, propagation, attenuation, and likely coastal inundation of tsunami waves that would have been created by slides… or that could be generated from similar future events. Only through the development and application of this type of tsunami modelling will it be possible to gauge the level of hazard posed by the identified submarine slope failures to shore installations and infrastructure, or to devise ways to effectively mitigate the impacts of future such events.
The filing by the Attorney General offers to bring the scientists to the Joint Review Panel to appear as witnesses sometime during the final hearings.
The filing notes that the current evidence tendered to the JRP by Enbridge, and other parties does demonstrate the potential for marine geohazards and associated tsunami events. Enbridge’s design of the proposed Northern Gateway marine terminal and its operational plans took into consideration the current state of knowledge of geohazards including earthquakes and tsunamis at the time of filing. Enbridge has said it would undertake further geological survey during the detailed design phase for the terminal.
At the time Natural Resources Canada noted that the information provided for the Environmental Review was sufficient at that time, now the Attorney General says:
the geographic scope for potential landslide induced tsunami hazards is now better understood to extend beyond the Kitimat Arm. NRCan and DFO seek by this motion to ensure that this Panel, and the Parties before the Panel, have the most up to date information on geohazards in the Douglas Channel.
Updates: DFO report in October will clarify the tsunamis in Douglas Channel.
Statement from Natural Resources Canada
Natural Resources Canada sent this statement to Northwest Coast Energy News on September 20, 2012.
In reference to the opening paragraph of your September 18th editorial entitled Geological Survey of Canada identifies tsunami hazard: Possible fault line on Douglas Channel, we would like to clarify the following. Although the ancient large submarine slope failures which our scientists have identified may have caused tsunamis, this is not a certainty. It is important to note that Fisheries and Oceans Canada is currently studying this information to model potential wave heights and speeds.
As our report states, only through the development and application of this type of tsunami modelling will it be possible to gauge the level of hazard posed by the identified submarine slope failures to shore installations and infrastructure, or to devise ways to effectively mitigate the impacts of future such events.
Northern Gateway response filed on August 31, 2012
Enbridge Northern Gateway filed this response to the Attorney General’s motion on August 31.
This motion of the Federal Government Participants requests permission to file late evidence consisting of a report entitled “Submarine Slope Failures and
Tsunami Hazard in Coastal British Columbia: Douglas Channel and Kitimat Arm” regarding tsunami hazard and additional modelling work based on that report.
Northern Gateway does not object to the filing of this late intervenor evidence.
It may be relevant and Northern Gateway accepts that theevidence could not be filed earlier. However, Northern Gateway would like the opportunity to conductits own additional modelling work which it would be prepared to provide to DFO for comment prior to the filing of any modelling work by DFO in this proceeding.
Attorney General response to Enbridge on September 10, 2012.
The Attorney General of Canada responded to Enbridge by saying:
Attorney General responds DFo is prepared to await filing its subseqent modelling work in these proceedings until such time as it has received, reviewed and commented upon additional modelling work as proposed by NGP Inc.
DFO nots howeverand wishes to alert the JRP that the NGP INc proposed may occasion a delay in the filing of the DFO moedling work which is now proposed for filing on or about October 31, 2012. Delivery of DFO comments as requested will depend on when DFO received the NGP Inc modelling work, the time and resources required by DFO to study and provide comments on the NGP modelling work and unforeseen factors which may have an impact upon completion the commentary. As such,
DFO is prepared to file its modeling work on or about October 31, 2012, but subject to any further direction or request by the panel.
Geological Survey of Canada map of Douglas Channel showing the area surveyed which discovered the landslides and possible fault line. (Geological Survey of Canada)
;
;
Map from the Geological Survey of Canada showing the landslides on the Kitimat Arm which triggered tsunamis in 1974 and 1975 (Geological Survey of Canada)
;
;
Map from the Geological Survey of Canada showing the giant slide on the southern tip of Hawkesbury Island. (Geological Survey of Canada)
;
Map from the Geological Survey of Canada showing the second giant slide on the coast of Hawkesbury Island on Douglas Channel (Geological Survey of Canada)
Map showing the Regional District of Kitimat Stikine (RDKS)
The Regional District of Kitimat-Stikine voted on Sept. 14, 2012, to oppose the Enbridge Northern Gateway pipeline. Eight of the twelve Regional District Directors of Kitimat Stikine voted to both to oppose the Northern Gateway project and to support resolutions of the Union of BC Municipalities (UBCM) on the pipeline.
Telegraph Creek director David Brocklebank, who originally proposed the motion, was supported by Dease Lake alternate director Joey Waite, Terrace municipal directors Dave Pernarowski (mayor) and Bruce Bidgood (councillor), Nass director (and regional district chair) Harry Nyce, Hazelton village mayor Alice Maitland, the Hazeltons and Kispiox/Kitwanga director Linda Pierre and Diana Penner (who was sitting in for the director Doug McLeod) for the rural area around Terrace and Kitimat.
Brocklebank had proposed the motion at the August meeting. It was tabled to allow for the directors who represent the various regions and municipalities time for consultation.
Voting against were Kitimat municipal director Corinne Scott, New Hazelton mayor Gail Lowry, Thornhill’s Ted Ramsey and Stewart municipal director Billie Ann Belcher.
Scott said she was voting against the motion, continuing the Kitimat council’s position that it remain neutral until the report of the Northern Gateway Joint Review panel. Ramsey also said Thornhill wanted to also remain neutral.
Other directors pointed to what they called the politicization of the Joint Review and how they believed it had been influenced by Prime Minister Stephen Harper.
Enbridge is facing a new penalty from the US Pipeline and Hazardous Materials Administration for not inspecting a pipeline branch in Ohio and Michigan. The decision by the PHMSA comes just after a couple of days after the agency acknowledged that Enbridge had paid the civil penalty for the Marshall, Michigan oil spill with a wire transfer to the US Treasury of $3,699,200 on August 12. It was the Marshall pipeline breach and spill that led to bitumen entering the Kalamazoo River.
The new proposed penalty is much lower, just $68,000. It relates to the PHMSA inspection of Enbridge’s Toledo pipeline between July 12 and July 15, 2010.
The PHMSA says it found three alleged violations of federal pipeline safety regulations.
As well as the proposed civil penalty of $68,000, Enbridge Toledo is required to submit past records for inspections of subsequent overpressure safety devices and out-of-service tanks
The agency lists the violations as:
1. Failure to adequately inspect the right-of-way at a mainline valve location in Toledo as required by 49 CFR §195.412.
No proposed penalty — Warning Item.
1. Exceeding the maximum interval for inspection of 12 overpressure safety devices as required by 49 CFR §195.428.
Proposed penalty is $39,000 + PCO.
1. Exceeding the maximum interval for API 653 internal inspections of two breakout tanks located at Stockbridge, MI as required by 49 CFR §195.432.
Proposed penalty is $29,600 + PCO.
Enbridge can, if it wishes, challenge the NOPV (Notice of Possible Violation) in court. In the case of the original Marshall, Michigan, spill NOPV, Enbridge did not challenge the findings of the PHMSA and paid the penalty.
The new document sent to Enbridge by David Barrett, PHMSA Director, Central Region says that the company failed to perform internal inspections or establish a corrosion rate for the bottom plates of its tanks within the 10 year period as required by US regulations. It also says Enbridge failed to demonstrate that they had established a basis for the corrosion rate for the tank bottoms and exceeded the 10 year maximum internal inspection interval for unknown corrosion rates.
Additionally, Enbridge did not have similar service experience, or procedures to apply similar service experience available to make this inspection interval determination.
The PHMSA also says that Enbridge Enbridge failed to inspect its overpressure safety devices at intervals not exceeding 15 months, but at least once each calendar year. The inspection intervals exceeded the maximum 15 month interval by 14-24 days for the overpressure safety devices listed int the order.
The compliance order calls for Enbridge to submit documentation of all inspections performed on
each of the tanks and overpressure devices listed in the PHMSA order from 2010 to present. Enbridge has to internally inspect each of the tanks and to submit to the PHMSA documentation on the “safety improvement costs” needed to comply with the order.
As for the Marshall, Michigan spill, while Enbridge promptly paid the civil penalty, the PHMSA order notes
This Order does not resolve any existing or potential civil or criminal liability that Enbridge may have for any other violations of the federal Pipeline Safety Laws, or any regulations or orders issued thereunder, not specifically enumerated herein. Further, this Order does not resolve any existing or potential civil or criminal liability that Enbridge may have for violations ofany other federal laws arising from or otherwise related to the events or conduct giving rise to this Order or
to the consequences or damages resulting from the Failure.
