On Monday, May 11th, we had a surge of power through our house so great, that it magnified the brightness of our lightbulbs tenfold.  The lights and one of the circuits proceeded to burn out, and the surge fried anything that was plugged in—as a strong burst of magnetic energy would. Even a surge strip did not keep the cable box from being fried. This type of situation has never occurred in our home in over 50 years. The event occurred at a little after 13:00 pm CST, or 18:00 UTC. No source was found for the surge, only a fried wire, which had caused a burning smell in the home. Certainly a malfunctioning wire, more than like fried by the surge as well, would not cause a surge in power, but a reduction in it. Would the Zetas care to comment on whether we are now experiencing  EMPs from PX on a more frequent basis? If so, would it be recommended that all electronics not in use be disconnected from their power source? Space was relatively quiet, but the magnetosphere was fluctuating widely. [and from another] http://www.manchestereveningnews.co.uk/news/greater-manchester-news... The cut was said to have been caused by an electrical surge. People in the area say "Smoke was coming from the electric cupboard from 86 Deansgate when the power surge hit. 4 fire engines responded to the call". Jade Barrow is a receptionist at 86 Deansgate, and said the whole building shook. She said: "The firemen explained to me that an electrical surge is like 2 magnets hitting each other. That's why it all shook because of the force."  [and from another]http://poleshift.ning.com/profiles/blog/show?id=3863141%3ABlogPost%... May 15. After 15 days with approximately 300 hours of missing data, it appears the uninterrupted BATSRUS RCM image feed has resumed.


Air France 447 in 2009 and Malaysia 370 and the recent Germanwings A320 are in the news because they impact the airline industry, and the blame thus placed elsewhere. To date, pilot suicide, storms, and bad pilot judgement have been used, and how is the public to know otherwise? Electric trains such as the Disney Monorail  and DC Metro crash incidents in 2009 and the recent Amtrak 188 go into investigation while talking heads murmur about safety devices or track maintenance or mechanical failure, which ultimately get the blame.  

It is only when the public is broadly affected that the public can get a hint that something else is afoot. Cell phones are regularly having disrupted service but the blame is placed on blocked access to towers or bad weather. The blackberry outage in 2008 was blamed on a software glitch. If the public is frankly being lied to, engineers responsible for maintaining equipment and the grid are not fooled. The talk has spilled over into the press, or into conversations with the public. During the Washington DC blackout, the electrical problem was described at first by the Washington Post as a “surge”. 

This is a key determinant between a failed electrical system, a simple outage, and electro-magnetic pulse. Pulse is a surge, and the sudden increase in the amount of magnetons and their associated electrons, such that equipment controlled by a steady pace of either particle flow goes into a runaway state. When equipment is guarded by surge protection, to guard against lightning strikes, it will shut down, as a brownout situation can damage equipment. But unless a lightning strike was present, there can be no excuse for a pulse or surge other than the presence of the charged tail of Planet X, aka Nibiru.  

What can the public expect? As cell phone service and cable TV via satellite continues to degrade, as airplanes increasingly crash during complete electronics failure or are forced to land with smoke in their cockpits, as electric trains surge off the tracks and brakes fail, as transformers explode at dams and on the grid, and as residential lights flicker and erratic and unexplained and spotty blackouts descend, the public can expect endless inane excuses from the establishment. The truth will be withheld because mankind is so dependent upon his electrical systems and equipment that the thought of being without is unthinkable. It is mass denial. 

Source: ZetaTalk Chat Q&A for May 23, 2015

Views: 47155

Comment

You need to be a member of Earth Changes and the Pole Shift to add comments!

Join Earth Changes and the Pole Shift

Comment by M. Difato on November 24, 2020 at 7:22pm

Alaska Airlines Flight Makes Emergency Landing At Sacramento International Airport

https://sanfrancisco.cbslocal.com/2020/11/23/alaska-airlines-flight...

SACRAMENTO (CBS13) – Following reports of smoke in the cockpit, a plane made an emergency landing at Sacramento International Airport on Monday (Nov 23), the airport said.

SMF said an Alaska Airlines flight from Las Vegas to Seattle was diverted to the area and made a safe landing allowing for passengers to get off.

After being inspected, the plane was cleared to fly and was prepared for takeoff to resume the flight, officials said.

No injuries were reported in the incident.

https://flightaware.com/live/flight/ASA1433/history/20201123/2305Z/...

Aircraft Type - Boeing 737-700 (twin-jet)
Comment by M. Difato on November 20, 2020 at 2:53pm

Austin flight bound for Seattle turns around, makes emergency landing after smoke in cabin

https://www.kxan.com/news/local/austin/austin-flight-bound-for-seat...

AUSTIN (KXAN) — A Delta Airlines flight from Austin Bergstrom International Airport to Seattle had to turn around shortly after takeoff and make an emergency landing Thursday morning (Nov 19), airport officials said.

There was light smoke reported in the cabin. The plane turned around and landed safely though back in Austin.

Delta Flight 1062 was scheduled for takeoff from AUS at 6 a.m. and due for landing at Seattle-Tacoma International Airport at 8:34 a.m. Pacific Time, but it had to come back to AUS shortly after it got in the air.

The plane landed safely at 7:03 a.m.

You can view the plane’s flight plan on FlightAware.com

https://flightaware.com/live/flight/DAL1062/history/20201119/1210Z/...

Aircraft Type - Airbus A319 (twin-jet) 
Comment by M. Difato on November 18, 2020 at 5:48pm

Boeing 737 Max being cleared for flight worldwide, with no responsible open talks of EMP vulnerability responsible for these deadly crashes.

FAA approves Boeing 737 Max to fly again, a milestone for Chicago-based Boeing

https://www.chicagotribune.com/business/ct-biz-boeing-737-max-faa-a...

After nearly two years and a pair of deadly crashes, the U.S. Federal Aviation Administration has cleared Boeing’s 737 Max for flight.

The nation’s air safety agency announced the move early Wednesday, saying it was done after a “comprehensive and methodical” 20-month review process.

Regulators around the world grounded the Max in March 2019, after the crash of an Ethiopian Airlines jet. That happened less than five months after another Max flown by Indonesia’s Lion Air plunged into the Java Sea. A total of 346 passengers and crew members on both planes were killed.

The planes won’t return to the skies for a while. The FAA says it must approve pilot training changes for each U.S. airline and airlines must perform required maintenance on the planes.

The FAA says the move was made in cooperation with air safety regulators worldwide. “Those regulators have indicated that Boeing’s design changes, together with the changes to crew procedures and training enhancements, will give them the confidence to validate the aircraft as safe to fly in their respective countries and regions,” the FAA said in a statement.

The move came after numerous congressional hearings on the crashes that led to criticism of the FAA for lax oversight and Chicago-based Boeing for rushing to implement a new software system that put profits over safety and ultimately led to the firing of its CEO.

Investigators focused on anti-stall software that Boeing had devised to counter the plane’s tendency to tilt nose-up because of the size and placement of the engines. That software pushed the nose down repeatedly on both planes that crashed, overcoming the pilots' struggles to regain control. In each case, a single faulty sensor triggered the nose-down pitch.

The FAA required Boeing to change the software so it doesn’t repeatedly point the nose of the plane down to counteract possible aerodynamic stalling. Boeing says the software also does not override the pilot’s controls like it did in the past. Boeing also must install new display systems for pilots and change the way wires are routed to a tail stabilizer bar.

Boeing’s redemption comes in the middle of a pandemic that has scared away passengers and decimated the aviation industry, limiting the company’s ability to make a comeback. Air travel in the U.S. alone is down about 65% from a year ago.

Boeing sales of new planes have plunged because of the Max crisis and the coronavirus pandemic. Orders for more than 1,000 Max jets have been canceled or removed from Boeing’s backlog this year. Each plane carries a sticker price between $99 million and $135 million, although airlines routinely pay far less than list price.

John Hansman, an aeronautics professor at the Massachusetts Institute of Technology, said that people typically avoid airplanes for a few months after there are problems. But the Max case is unusual, and were it not for the novel coronavirus, Hansman said he would feel safe flying on a Max.

“This whole thing has had more scrutiny than any airplane in the world,” he said. “It’s probably the safest airplane to be on.”

American is the only U.S. airline to put the Max back in its schedule so far, starting with one round trip daily between New York and Miami beginning Dec. 29.

Nearly 400 Max jets were in service worldwide when they were grounded, and Boeing has built and stored about 450 more since then. All have to undergo maintenance and get some modifications before they can fly.

Pilots must also undergo simulator training, which was not required when the aircraft was introduced. Hansman said pilot training for qualified 737 pilots shouldn’t take long because Boeing has fixed problems with the Max’s software. The company posted a summary of changes to the plane.

Relatives of people who died in the crashes remain unconvinced of the Max’s safety. They accused Boeing of hiding critical design features from the FAA and say the company tried to fix the tendency for the plane’s nose to tip up with software that was implicated in both crashes.

“The flying public should avoid the Max,” said Michael Stumo, whose 24-year-old daughter died in the second crash. “Change your flight. This is still a more dangerous aircraft than other modern planes.”

Boeing’s reputation has taken a beating since the crashes. Its then-CEO, Dennis Muilenburg, initially suggested that the foreign pilots were to blame. However, congressional investigators discovered an FAA analysis — conducted after the first Max crash — that predicted there would be 15 more crashes during the plane’s life span if the flight-control software were not fixed.

After an 18-month investigation, the House Transportation Committee heaped blame on Boeing, which was under pressure to develop the Max to compete with a plane from European rival Airbus, and the FAA, which certified the Max and was the last agency in the world to ground it after the crashes. The investigators said Boeing suffered from a “culture of concealment,” and pressured engineers in a rush to get the plane on the market.

Boeing was repeatedly wrong about how quickly it could fix the plane. When those predictions continued to be wrong, and Boeing was perceived as putting undue pressure on the FAA, Muilenburg was fired in December 2019.

Dickson — who flew F-15 fighters in the Air Force before serving as a pilot and an executive at Delta Air Lines — flew the plane personally before it was cleared.

In recent weeks, European regulators also signaled their likely approval of Boeing’s work. Regulators in Canada and China are still conducting their own reviews. Relatives say it’s too soon, and they and their lawyers say Boeing and the FAA are withholding documents.

Naoise Ryan, an Irish citizen whose husband died in the Ethiopian crash, said the Max is “the same airplane that crashed not once but twice because safety was not a priority for this company.”

Anton Sahadi, who lives in Jakarta, Indonesia, and lost two brothers in the Lion Air crash, said he feels it is too early for the Max to fly again.

“I, personally, feel so regretful for the decision to unground the Boeing’s 737 Max,” he said. “The cases from the incidents are not 100% finished yet. There are many of them still in process. I think all the victims' family in Indonesia and Ethiopia will feel the same, so regretful, why it can fly again because we are still in the recovery process for our problems because of the incidents.”

~

Related 

ZetaTalk Insight 3/31/2019:
http://www.zetatalk.com/ning/31mr2019.htm
The Boeing 737 Max 8 has been flying for several years, considered a reliable workhorse worldwide. What has happened that only recently two crashes occurred, both involving the nose of the plane stubbornly pointing down? The charged tail of Nibiru has descended, causing not only the Lomonosov explosions
http://www.zetatalk.com/newsletr/issue648.htm
but also neon clouds
http://www.zetatalk.com/newsletr/issue641.htm
so low they blow transformers, as occurred in New York City. Static electricity is evident, per a Mr MBB333 video,
https://www.youtube.com/watch?v=7pZWBQLanp4
and this all certainly translates to more electro-magnetic pulse affecting mankind’s electronics.

President Trump, who is aware of Nibiru and the EMP problems, is spot on when he says the solution is to allow the pilots to control the plane – manually. When the sensors are affected by EMP, they mis-direct the autopilot, but gaining manual control of the plane has become a wrestling match. The airline industry is loath to admit their problems with EMP, blaming crashes on pilot error, but gradually the public will become reluctant to fly, as they should. Phone or Skype your loved ones, instead. There are also EMP problems with smart cars that will increasingly go rogue.

ZetaTalk Newsletter as of March 24, 2019

https://poleshift.ning.com/profiles/blogs/zetatalk-newsletter-as-of...

Comment by M. Difato on October 26, 2020 at 4:31pm

A DHL cargo plane made an emergency landing at Heathrow Airport on Saturday evening (Oct 24) after the pilot reported smoke in the cockpit.

https://www.airlive.net/incident-dhl-cargo-plane-performed-an-emerg...

The Airbus A300 touched down safely after 11pm with emergency vehicles on standby it then taxied to the terminal. Airport firefighters were supported by fire crews from London Fire brigade The incident was declared as a full emergency response.

Heathrow fire crews investigated the issue but were unable to determine the cause.

~

London Heathrow emergency landing: Emergency services surround British Airways flight

A BRITISH AIRWAYS flight was forced to abort its journey to Verona and return to London Heathrow Airport, sparking an emergency services response.

https://www.express.co.uk/news/uk/1350354/london-heathrow-british-a...

One passenger shared a video of fire engines greeting the plane's arrival in Heathrow yesterday (October 21, 2020), adding: "That was a long 10-minute emergency landing." Passengers safely disembarked and were placed onto a new plane, which took them to Verona. 

In a message posted on Twitter to a passenger, British Airways said: "We apologise for the delay to your flight today.

"We had to return back to London Heathrow due to a technical issue." 

"Safety is our number one priority and we would never continue a flight unless it was safe to do so.

"We are currently in the process of arranging a new aircraft so that we are able to get you to your destination."

 British Airways flight 2596 returned to London Heathrow this morning

 (Image: TWITTER / SHELBOURNEFILMS)

BA said changed its departure time to 12:20 pm local time.

They continued: "Please make your way to Gate C55 where your flight will be boarding from."

BA says there was a technical issue forcing the flight to be diverted back to the UK.

A BA spokesman said: "The safety of our customers and crew is always our priority and the flight returned to Heathrow as a precaution due to a minor technical issue. 

"We've apologised to our customers and have organised a replacement aircraft so that we can get them on their way again as quickly as possible.”

A spokesperson from Heathrow Airport said the plane landed safely and all passengers were disembarked. 

A passenger onboard the flight claimed there was a smell of burning and that a crew member fell ill.

FlightRadar data shows the flight taking off from Heathrow and travelling over South London shortly after 7am yesterday morning. 

 The flight path (Image: FlightRadar24)

Aircraft Type : Airbus A320 (twin-jet)
Comment by M. Difato on October 23, 2020 at 9:55pm

Smoky Odor Prompts Delta Flight Bound For Mpls. To Make Emergency Landing At Rochester Airport

https://minnesota.cbslocal.com/2020/10/22/delta-flight-bound-for-mi...

MINNEAPOLIS (WCCO) — A Delta Air Lines flight bound for Minneapolis made an emergency landing at Rochester Airport Thursday morning (Oct. 22) due to a smoky odor in the cabin of the plane.

According to Rochester Airport officials, the SkyWest CRJ900 aircraft, operating for Delta, was traveling from St. Louis, Missouri to Minneapolis when it declared an emergency and requested to land in Rochester.

The flight landed safely at around 7:20 a.m. with emergency responders standing by. No medical treatment was required for the 39 passengers and four crew members onboard.

SkyWest Airlines later confirmed that the emergency landing for Skywest Flight 3757 was due to a smoky odor in the cabin.

As of 10:52 a.m., the passengers were being transported to Minneapolis on a bus.

~

https://flightaware.com/live/flight/SKW3757/history/20201022/1100Z/...

Aircraft Type
Canadair Regional Jet CRJ-900 (twin-jet) (CRJ9)
Comment by M. Difato on October 19, 2020 at 4:27am

Air France Boeing 777 Diverts To Goose Bay

https://simpleflying.com/air-france-777-goose-bay/

The aircraft involved in the diversion is a 15.8-year-old Boeing 777-300ER, with registration F-GSQH, delivered to Air France in 2005, according to Planespotters.net. The plane was scheduled to fly from Montrèal to Paris Charles De Gaulle on Friday (October 16th) when the incident occurred.

The aircraft took off from Montrèal at 19:35 local time as AF347, flying eastbound toward Newfoundland, according to FlightAware. Around an hour and 45 minutes into the flight, shortly after entering the Atlantic at 38,000 feet, the crew received a forward cargo smoke indication.

 The aircraft involved in the incident (pictured here) was a 15-year-old 777-300ER. Photo: Eric Salard via Wikimedia Commons

The indication forced the crew to make a turn back towards Canada and diverting to the nearest airport of Goose Bay (YYR). The aircraft declared an emergency and requested that emergency services be deployed. The aircraft successfully landed at 23:21 local time, 2 hours and 45 minutes after takeoff. Incident information is sourced from The Aviation Herald.

No smoke

The aircraft has 100 passengers onboard, a relatively light load for the premium-heavy 296 seat 777. All passengers safely disembarked and no injuries of any kind were reported. Upon inspection after landing, the ground crew found no indication of smoke or fire near the forward cargo hold. The indication was later ruled as false.

For the passengers stuck in Goose Bay, Air France found a quick resolution. Air France 349 was scheduled to also leave from Montrèal to Paris the same night at 22:25 local time. AF349 made a stop at Goose Bay to pick up passengers from AF347, allowing them to return just 7.5 hours later than planned.

Safety first

While the indication did turn out to be false, and the crew did not report any odor or smoke except for the indication, safety remains paramount. Pilots are trained to divert at the first sign of possible trouble, especially on intercontinental flights where could be few or no nearby diversionary airports.

The plane will likely now undergo maintenance in Paris to understand what went wrong with the smoke sensor. Issues with the smoke sensor can cause crews to miss fires, resulting in a possible catastrophe.

Luckily the passengers on AF347 were able to quickly return to Paris thanks to another flight soon after. Air France has been slowly increasing its international capacity in the last few months, especially between Canada and the EU since the latter allows for travel without quarantine for Canadian travelers.

Comment by Starr DiGiacomo on September 26, 2020 at 8:48am

https://www.upi.com/Defense-News/2020/09/24/Super-Hornet-makes-emer...

Super Hornet makes emergency landing after engine fire in Virginia

Sept 24 2020

Sept. 24 (UPI) -- A Navy F/A-18 Super Hornet experienced an engine fire Monday, forcing it to make an emergency landing at Naval Air Station Oceana in Virginia.

The incident took place while a Super Hornet from Strike Fighter Squadron 11 was training over the Virginia Capes, with the emergency landing happening at noon, according to Cmdr. Jennifer Cragg, a Naval Air Force Atlantic spokeswoman.

"The aircraft landed safely at NAS Oceana without incident. An aviation mishap investigation has been initiated to determine the cause of the incident," Cragg said. "There were no injuries."

A nearly identical mishap took place at the same installation earlier this month.

Cragg declined to say whether officials think the incidents share a similar cause.

Comment by M. Difato on September 11, 2020 at 3:32pm

Transformer Fire Knocks Out Power to Thousands in Bronx

The FDNY said the transformer near in Pelham Gardens may have exploded around 8 p.m., and was then seen engulfed in flames along the street

https://www.nbcnewyork.com/news/local/transformer-fire-knocks-out-p...

A transformer fire in the Bronx knocked out power to nearly 3,000 customers Thursday night (Sept 10), as crews worked quickly to get electricity back up.

The FDNY said the transformer near Eastchester Road and East Gun Hill Road in Pelham Gardens may have exploded around 8 p.m., and then was seen engulfed in flames along the street. It was not clear was may have sparked the possible explosion and resulting fire, but according to Con Edison, 2,931 customers were left in the dark as a result.

No injuries were reported, although police had to respond to the scene to direct traffic throughout the neighborhood as all streetlights had gone out.

~

Fire at Hydro One station knocks out power to over 1,500

https://kitchener.ctvnews.ca/fire-at-hydro-one-station-knocks-out-p...

 (Photo/Brad Patton @CWFireChief)

KITCHENER -- A fire at a Hydro One substation between Elora and Fergus knocked out power for residents living in the area, said fire officials in Centre Wellington.

Centre Wellington Fire Chief Brad Patton tweeted that firefighters were on scene of the fire on County Road 18 at 3:42 a.m.

Deputy Fire Chief Jonathan Karn responded that the fire had been extinguished just before 6 a.m., but power had been affected for areas of Salem, Fergus and Elora serviced by Hydro One..."

~

Fire at M’singh sub-station again

https://www.thedailystar.net/city/news/fire-msingh-sub-station-agai...

Power supply in Mymensingh district was disrupted for nearly eight hours after a fire broke out at a sub-station of Kewatkhali Power Grid yesterday morning (Sept 9).

The fire started around 10am from a circuit breaker and spread to the nearby control room, said Rafiqul Islam, chief engineer of Power Development Board in Mymensingh.

Two fire-fighting units brought the blaze under control soon, he said, adding that power supply to the entire Mymensingh division was halted following the incident.

However, power supply to Jamalpur, Sherpur and Netrakona districts was restored around 11:30am. "We have replaced the burnt circuit breaker with a new one," the chief engineer said.

Md Masudul Haque, executive engineer of Power Grid Company, said the power supply was restored in Mymensingh district around 7:30pm.

The incident happened two days after a fire broke out at the main station of Kewatkhali Power Grid, leaving the entire division out of electricity for several hours. Restoration work of power lines damaged during Tuesday's incident was going on when yesterday's fire broke out.

A four-member probe committee was formed by the district administration to look into Tuesday's incident.

Comment by M. Difato on September 9, 2020 at 3:22pm

Power outage in Mymensingh division as national grid substation catches fire

https://bdnews24.com/bangladesh/2020/09/08/power-outage-in-mymensin...

The fire broke out at the 132/33 KV grid substation around 1.30 pm on Tuesday (Sept 8), said Panat Shah, deputy director of Mymensingh District Fire Service. The firefighters from six units tamed the blaze after an hour, he added.

Power supply has stopped to Mymensingh, Jamalpur, Sherpur and Netrokona after the fire broke out in the grid substation, said Anwarul Islam, executive engineer of Mymensingh Power Division.

“We’re not sure right now about the time to resume the power supply. The blaze is under control. A probe panel is being formed to determine the amount of loss and also to find out the reason behind it. We can provide the details later,” he said.

“Overheating of marshalling board” could be a reason for the fire, the official said.

Of about one million clients in the four districts of Mymensingh, 650,000 lost electricity supply, said Rafiqul Islam, chief engineer of Power Development Board for Mymensingh region.

Comment by M. Difato on September 9, 2020 at 3:20pm

Transformer fire at Georgia Power plant shakes Cobb County neighborhood

 (A giant cloud of dark smoke can be seen coming from the plant near Atlanta, Georgia. Credit: Twitter & https://www.thesun.co.uk/news/12606621/explosions-georgia-power-pla... )

A transformer fire at a Georgia Power plant led to reports of explosions throughout a Cobb County neighborhood.

https://www.msn.com/en-us/news/us/transformer-fire-at-georgia-power...

Channel 2 Action News received several messages from people who live near Georgia Power’s Plant-McDonough Atinkson saying they heard or felt some kind of explosion Sunday night.

Cobb County Fire and Emergency Services confirmed that crews battled a fire at the plant off South Cobb Drive. Channel 2 received an updated statement from Georgia Power:

“The transformer fire, which started and was contained within the Plant McDonough switchyard last night, has been extinguished. We have confirmed that there were no injuries as a result of the fire. Additionally, our power delivery system functioned as designed and there were no extended customer power outages as a result of this incident. The safety of our facilities and employees is our top priority every day. We are working to determine the exact cause of the fire but we believe it was the result of equipment failure related to the transformer. We appreciate the response, professionalism and hard work of fire personnel and other first responders as well as our employees in safely responding to this event.”

What caused the explosions and fire are still under investigation.

Channel 2 Action News spoke with a number of neighbors who were worried once they saw the fire and plumes of smoke and embers so close, that they voluntarily packed up and evacuated.

“Heard of number of popping noises and all kind of came out right when the big explosion happened over that way… big fireball into the air. Pretty impressive, pretty crazy,” said neighbor Joey Jarrell.

“When we looked outside our back window, the flames were up above the trees here. Before any fire crews got here or anything, it was intense,” said witness Shelby Watson.

A Cobb fire spokesman said they first received 911 calls around 11:28 p.m. Sunday night (Sept 6). Crews arrived on the scene minutes later, where they saw the heavy smoke and flames.

“Explosions are still under investigation. Right now crews are getting the fire knocked down so they can get close enough to further investigate,” Nick Danz said.

Danz said several units battled the two-alarm fire and hazmat crews were also called in.

Georgia Power told Cobb emergency services there were no injuries and everyone who was working was accounted for.

SEARCH PS Ning or Zetatalk

 
Search:

This free script provided by
JavaScript Kit

Donate

Donate to support Pole Shift ning costs. Thank you!

© 2020   Created by 0nin2migqvl32.   Powered by

Badges  |  Report an Issue  |  Terms of Service