While Bamberg itself does not have an airport, there are three airports around Bamberg that can be reached within three hours.
The closest airport is Nürnberg/Nuremberg.
If you arrive at Nuremberg, you can easily take the underground and the train to Bamberg.
Upon arrival, you need to look for the U-Bahn, the Nuremberg underground. On a workday, trains leave approximately every 10 mins and you need to take a train to Nürnberg Hauptbahnhof (main train station). There, you take any regional train to Bamberg.
Tickets for going to Bamberg can already be purchased at Nurembger airport. At the ticket machines provided by VAG or VGN you can get a ticket to Bamberg and need not buy another one at the main train station. Please note that with such a ticket, you can only use regional trains, no IC or ICE trains. Since the public busses are also operated by this company, you can even get a ticket to the bus stop closest to your hotel and get the ticket already at Nuremberg airport. Please check their website for more information.
In total, you will take approx. 90 mins to get to Bamberg from Nuremberg airport.
The second closest airport is Frankfurt am Main.
If you arrive at Frankfurt, depending on the terminal you arrive at, you need to find the train station "Frankfurt Flughafen", which is serviced by Deutsche Bahn (DB). When you get there, you can take get your ticket for the entire journey from the ticket machines operated by DB. To get to Bamberg, you will have to change at Würzburg and depending on your connection, you either get a train from the airport to Würzburg or you need to change again at Frankfurt main train station. At Würzburg, you will then take a regional train to Bamberg.
Depending on whether or not you have to change at Frankfort main train station, the journey to Bamberg takes between 2h 30 mins and 3h.
The third closest airport is München/Munich.
If you arrive at Munich, you need to take an S-Bahn first to get to Munich main train station. The S-Bahn stop at Munich airport is located in front of the terminals (ca. 5 mins on foot). Trains go approximately every 15 mins. When you arrive at München Hauptbahnhof (main train station), you can either take a direct train to Bamberg or you need to change at Nuremberg, depending on the connection.
Ticktes for going to Bamberg can already be purchased at Munich ariport. At the ticket machines provided by DB (Deutsche Bahn) you can get a ticket for the entire journey.
Depending on the train connection at Munich main train station, you will take between 2h 45mins and 3h 30mins to get to Bamberg from Munich airport.
To get to Bamberg by train, travellers often have to change either at Würzburg or at Nuremberg and take the last hour of their journey on a regional train. To plan your journey by train, please check the website of the German rail company, Deutsche Bahn. Once you arrive at Bamberg train station, you can either walk to your hotel or take a taxi or take one of the public busses operated by VAG/VGN. Please check their website to find out more about bus connections.
If you travel by car coming from the north or the south, you need to follow the autobahn A73 and leave at exit "Bamberg Ost". If you travel from the east or the west, please follow autobahn A70 and leave at exit "Bamberg".
Parking at Bamberg is more difficult. Around the conference venue, there is one garage very close by (Karstadt Parkshaus), and several garages in the vicinity. Please have a look at the position plan of garages (384.3 KB)in Bamberg provided by Stadtwerke Bamberg. Since parking for a whole day can be rather expensive, it is advisable to either walk to the venue or take a bus and leave the car at the hotel.
To travel around in Bamberg, you can either buy day tickets or tickets for individual journeys. The website of the bus company in Bamberg (VAG) helps you plan your journey from one point to another. You could also take a bus tour of Bamberg with bus number 910 (website in German only).


Simple script to perform the steps involved in adding, committing and pushing to a remote git repo. It rewrites the https URL to ssh URL in the process.
a verfy simple github API for PHP with example.
Using inline and anonymous functions with PHP. Some tests and thoughts about function scope.
The best way of writing something. If you get stuck, this Ernest Hemingway quote may help you if you write something - like a novels or a computer programs.
Blog entry showing how to make a very simple CSS compiler with PHP and CSS, without much effort.
This short piece of PHP code generates valid AUTH PLAIN for smtp servers, at least Postfix. Can be used when testing smtp with telnet.


text:
The Long Way Down: The crash of Air France flight 447
Note: this accident was previously featured in episode 10 of the plane crash series on November 11th, 2017, prior to the series' arrival on Medium. This article is written without reference to and supersedes the original.
Searchers recover the tail section of Air France flight 447 from the Atlantic on June 7th, 2009. (The Guardian)
In the early hours of the first of June 2009, Air France flight 447 from Rio de Janeiro to Paris disappeared in a radar dead zone over the mid-Atlantic. The Airbus A330 with 228 people on board had vanished into the night without a distress call, leaving behind little to explain its sudden and dramatic end. What could have brought down a modern passenger jet, flying for a world class airline, during what should have been the safest part of the flight? For two years, the world could only speculate, as search teams scoured a vast area of the ocean floor in search of the elusive black boxes.
When the recorders were finally found in May 2011, they revealed a story at once more prosaic and more inexplicable than anyone had imagined. A brief interruption to their airspeed indications, lasting less than a minute, had thrown two trained Air France pilots into a state of paralyzed agitation. Through a series of increasingly misguided control inputs, they sent flight 447 plummeting towards the ocean, all the while trying desperately to understand what was wrong, only grasping too late that they themselves were the problem. How could such a thing happen? To this day, most people still struggle to understand it. But there is a reason, written between the lines of the cockpit voice recorder transcript, hidden away within the mysterious code that governs human behavior, a key to the secrets of the profoundly irrational. Its lessons could not be more important, even for those who believe themselves above the doomed crew of flight 447, as the boundary between the responsibilities of man and machine grows ever dimmer.
A CGI image of flight 447 in its final hours. (PBS Nova)
It's 1:00 a.m., the middle of the Atlantic Ocean. 35,000 feet above the night-dark waves, dim overhead lights illuminate the cockpit of Air France flight 447. Captain Marc Dubois has headphones on, listening to opera. The pilot flying, First Officer Pierre-Cédric Bonin, stares dully at the instrument panel.
Dubois hands Bonin his headset, and for a few moments they listen together. "All that's missing is the whiskey!" Bonin eventually says, handing the headset back to his captain, one might imagine with a smile. Flight 447 flies on into the night. Red and green lights steady, white lights blinking. No one knows it, but they are passing into that strange realm between life and death, hurtling onward into the void, unaware that they have already walked for the last time among the living.
The pilots of flight 447, probably pictured in their license photos. (Original source unknown)
Three hours earlier in Rio de Janeiro, Brazil, 216 passengers and 12 crew boarded Air France flight 447 for an overnight flight to Paris. The plane was an Airbus A330, a fully fly-by-wire wide body jet with an impeccable safety record; since its introduction in 1994, the type had never had a fatal accident in passenger service. The flight crew consisted of 58-year-old Captain Marc Dubois, a veteran pilot with nearly 11,000 hours; 32-year-old First Officer Pierre-Cédric Bonin, an inexperienced copilot with 2,000 hours who had recently come up through Air France's in-house training program; and 37-year-old Relief First Officer David Robert, who would fill in during the middle of the flight so that Captain Dubois could get his legally mandated rest. Robert had also learned to fly at Air France, but had since graduated to an executive position, and had joined the crew of flight 447 in order to keep his type rating. His landing in Rio de Janeiro during the inbound trip was his first in three months.
The route of flight 447. (Google + own work)
For Air France pilots, the Rio de Janeiro rotation was a coveted trip, complete with a three-day layover at a beachside hotel in Copacabana. Pilots often spent their rest days partying, sightseeing, and restaurant-hopping. First Officer Bonin had brought his wife along for the ride, leaving their kids at home in France; Captain Dubois had also brought his girlfriend, an off-duty flight attendant and opera singer, with whom he had been seen out on the town the night before the flight. Dubois was said to have gotten just one hour of sleep before boarding flight 447.
Although none of the pilots were well-rested, they also knew that their advanced plane could bail them out. Unlike older generations of jets, the A330 was designed to minimize the consequences of crew errors, incorporating flight envelope protections that would make it impossible for the pilots to pitch too steeply up or down, fly too fast or too slow, bank too far to one side, or generate G-loads that could overstress the airframe. Furthermore, thanks to the plane's advanced flight management system, they could enter the entire flight plan before departure, and the plane would all but fly itself from just after takeoff until right before landing. The pilots' job primarily consisted of tactical decision-making and monitoring the instruments.
F-GZCP, the aircraft involved in the accident. (Hansueli Krapf)
Flight 447 took off from Rio de Janeiro at 22:29 UTC, climbed to its cruising altitude of 35,000 feet, and proceeded northeast up the coast of Brazil. Bonin was the pilot flying, although he had little reason to touch the controls, and Dubois monitored the instruments. David Robert hung back in the crew quarters, trying to get some sleep before going on duty.
As the flight passed off Natal and headed out into the Atlantic, the pilots mostly kept to themselves. Dubois pointed out the equator, and Bonin joked about "feeling the bump" as they passed over it. An hour passed. Everything seemed to be going smoothly.
At around 1:30 a.m. UTC, the Brazilian oceanic control center, Atlantico, contacted the crew and instructed them to remain at flight level 350–35,000 feet. "Eh, well there you are," said Captain Dubois. Keying his mic, he replied to the controller, "Okay, will do." It would be flight 447's last communication with the outside world.
First Officer Bonin had been using the cockpit weather radar to observe a growing band of thunderstorms in their path, a region known as the Intertropical Convergence Zone, where thunderstorms are practically a permanent fixture. All the pilots on flight 447 had flown through it many times before, crossing over it twice on every trip to South America. But tonight Bonin seemed more nervous than usual. "We'll soon ask to climb, surely," he said, expressing his dissatisfaction with the controller's order to stay at 35,000 feet, and his desire to get above the worst of the weather.
Satellite weather data from the Intertropical Convergence Zone at around midnight on the night of the accident, with flight 447's designated airway overlaid. (BEA)
But Captain Dubois knew that there was no need to change altitude. In his judgment the weather was unlikely to be any better at 37,000 feet, the highest they could fly at their current weight, nor was it likely to be dangerous at any flight level. At most they could expect some mild turbulence or icing. And if they really needed to, then they could divert around it.
"So we've got a… thing straight ahead," Bonin said, sounding nervous.
"Yes, I saw that," said Dubois.
Eleven minutes later, Bonin said, "It looks like we're entering the cloud cover."
Dubois had no comment.
"It would have been good to climb now, eh?" Bonin said.
"Yeah, if it's turbulence," Dubois said, without the slightest hint of worry.
Now deep in the oceanic sector, the plane was outside the radar range of any airport. Out here, planes were kept apart by keeping northbound traffic on odd flight levels and southbound traffic on even flight levels. But the next highest odd level, 37,000 feet, was close to their maximum altitude — maybe too close. Bonin suggested that they request a non-standard altitude of 36,000 feet.
"We'll wait a little, see if it goes that way," Dubois replied.
Bright flashes of light streaked across the windscreen, the eerie glow of St. Elmo's fire. The sound of ice crystals hitting the plane rose to a dull roar in the background.
St. Elmo's Fire in an aircraft cockpit. (Beyond Clouds)
At this point Captain Dubois decided it was time to turn in for the night. He rang the call button to summon First Officer Robert from the bunk room. To Bonin, he said, "Er, who's doing the landing, is it you? Well, he's going to take my place. You're a PL, right?"
"Yeah," said Bonin.
This was the closest Dubois ever came to deciding who would be in command after he left the flight deck.
Two minutes later, Robert entered the cockpit. "Did you sleep?" Bonin asked.
"So-so," Robert replied.
"You didn't sleep?" Dubois interjected.
"He said so-so, so-so," said Bonin.
"Well, then I'm out of here," said Dubois.
Bonin briefed Robert on the situation: they were cruising at 35,000 feet, there was a storm ahead but they couldn't climb to 37,000. Their attempt to log on with the oceanic control system in Dakar, Senegal had failed, but this was not an uncommon occurrence and Bonin knew it. All around, nothing terribly unusual. Robert settled in for the next leg of the flight.
About six minutes later, noting the storm cell in their path, Robert said, "Don't you maybe want to go to the left a bit?"
"You can possibly go a bit to the left," Robert repeated.
With two first officers in the cockpit, and the less experienced one at the controls, it was unclear who was in charge. Decisions seemed to be taken by mutual agreement. Bonin never replied to Robert's suggestion, so nothing was done.
Now a smell of ozone started to seep into the cockpit, a not unusual phenomenon when flying through highly charged thunder clouds. But Bonin didn't seem to recognize it, and it was making him nervous. The ozone, the Saint Elmo's fire, the storms — none of it was out of the ordinary for a transatlantic crossing, but for some reason it was starting to get to him.
How ice blocks a pitot tube and affects airspeed readings. (boldmethod)
For the past several minutes, they had been flying through a cloud of high-altitude ice crystals within the upper reaches of the thundercloud. Normally this would not be a problem, but if the concentration of crystals is high enough, they can clog the pitot tubes — the airspeed sensors — faster than the built-in heaters can melt them. This is what occurred on flight 447.
The A330 has three pitot tubes, one each for the captain, the first officer, and the standby instruments. Each pitot tube measures the pressure of the oncoming air, which is then compared to the static pressure to derive the plane's airspeed. This data in turn is used to calculate a number of other parameters, including Mach number, vertical speed, and altitude, which are all displayed instantaneously to the pilots. But if ice crystals clog the pitot tubes, air cannot enter them, causing the measured pressure to drop, which in turn causes a decrease in indicated airspeed.
On flight 447, as all three pitot tubes filled up with ice, the airspeed readings quickly became invalid. Sensing a growing discrepancy between the three sources of airspeed data, at 2:10 a.m. and four seconds the autopilot disconnected with a sudden cavalry charge warning. The auto thrust shut off a split second later. Taken completely by surprise, First Officer Bonin announced, "I have the controls!" and reached for his side stick.
The principle of the "flight envelope." (Philippe Goupil)
Behind the scenes, the loss of valid airspeed data had triggered a shift in the Airbus's complex flight control laws. In "normal law," computers interpret pilots' side stick inputs and move the control surfaces in accordance with what is reasonable at that altitude, speed, and configuration. This improves the handling of the airplane to such an extent that no particular skill is required to fly it gracefully. Normal law also comes with full flight envelope protections in roll, pitch, speed, and load factor.
If sensor failures occur, the controls drop down a level to "alternate law." This law contains several sub-laws with slightly different configurations, but in general, alternate law means that some or all computer moderation of control inputs remains, but flight envelope protections are removed. The autopilot and auto thrust cease to function.
In the event of further failures, the controls can enter direct law, in which there are no flight envelope protections and side stick inputs correspond directly to the position of the control surfaces, with no adjustment by the computer. This makes the airplane fly rather like a classic airliner, similar to most older Boeing models.
When the airspeed readings became invalid on flight 447, the control law changed to "alternate 2B," which is specific to loss of speed data. In this law, load factor protection remains, but there is no autopilot, no auto thrust, and no high or low speed protection; furthermore, lateral (roll) control functions as it does in direct law. All of this happened near instantaneously, leaving the pilots completely in control of the airplane with little advance warning.
As soon as the autopilot disconnected, turbulence caused the plane to roll eight degrees to the right; Bonin immediately grabbed the side stick and rolled it back to the left, his inputs rough and jerky. At the same time, he pulled back on the stick, putting the plane into a climb. The A330 began to ascend rapidly from its cruise altitude of 35,000 feet, zooming upward through the impenetrable blackness, as multiple alarms blared over the cockpit speakers.
How a stall works. (NASA)
Climbing while at high altitudes above 30,000 feet is something that requires care and consideration. At these altitudes, a plane's maximum safe speed and minimum safe speed are quite close together (and at a certain height they will in fact meet, a zone that pilots call the "coffin corner"). Fundamentally, as angle of attack — the angle of the plane into the airstream — increases, lift increases, until it reaches the critical point and drops off rapidly, causing the plane to stall. Because the air is thin at high altitude and provides little lift, a higher speed is necessary to keep the plane airborne, and the critical angle of attack is very low. Pitching up even a few degrees could place the plane on the edge of a stall. And in fact, as Bonin pulled back on his stick, the plane's stall warning activated for three seconds, informing him that the angle of attack, for a moment anyway, was dangerously high.
Flight data from the first 20 seconds after the start of the event. (BEA)
But the warning proved transient, and neither pilot recognized it. Robert asked, "What was that?"
Bonin did not directly address the question. "We haven't got a good… we haven't got a good display of speed," he said. A continuous C-chord pinged away in the background, warning that they had left their assigned altitude.
A number of warning messages had appeared on the computer screen, and Robert began to read them off in a disjointed, confused manner. None of them explicitly stated the cause of the failure, only the symptoms, including the disconnection of the autoflight systems and the switch to alternate law. By now, flight 447 was climbing through 37,000 feet, still going up, but decelerating alarmingly.
Robert must have noticed their high pitch angle, because he said to Bonin, "Watch your speed, watch your speed!" But neither pilot had a valid airspeed reading.
"Okay, okay, okay, I'm going back down," said Bonin, lowering the nose. But he didn't lower it enough to stop climbing, and he reduced engine thrust, exacerbating the loss of airspeed even further.
"Go back down! According to that we're going up," Robert said, presumably pointing at their altitude readout. "According to all three you're going up, so go back down."
"You're at… go back down!"
"It's going, we're going back down," Bonin insisted, restoring engine thrust to maximum. But the plane kept climbing.
Robert started switching Bonin's instruments to alternate sources, but in a wholesale manner, indicating that he had not identified what instruments were actually faulty. Having done this, he started trying to summon Captain Dubois, ringing the call button with almost frenetic urgency. Clearly both pilots were in over their heads; only Dubois, it seemed, could help them. By now the airspeed indications had returned to normal, but the pilots had already set in motion a sequence of events which could not be undone.
Flight data from 46 seconds after the start of the event to 106 seconds after the start of the event. (BEA)
At that moment the plane's angle of attack, now rising through ten degrees, again triggered the stall warning, and this time it didn't go away. Accompanied by continuous clicking, an automated voice began to call out, "STALL! STALL!"
Flight 447 reached a peak altitude of 38,000 feet, stalled, and began to descend. Nose high, engines straining, the plane started to accelerate downward, following a long descending arc that grew steeper with every passing second.
"STALL! STALL!"
Bonin was frantically trying to keep the wings level, but the disrupted airflow and his own jerky control inputs made this all but impossible. The plane swayed wildly from side to side, reaching bank angles of up to forty degrees. "Above all, try to touch the lateral controls as little as possible, eh?" Robert suggested.
"I'm in TOGA, eh?" Bonin said, referring to takeoff/go around, the highest normal thrust setting. He didn't seem to understand why, if he had engine power set to TOGA, they were descending.
"Is he coming or not!?" Robert said, searching for some sign of the captain.
"But we've got the engines, what's happening?" Robert exclaimed. "Do you understand what's happening or not?"
"I don't have control of the airplane anymore now!" said Bonin. "I don't have control of the airplane at all!" With the nose pitched up and the engines at max thrust, he simply couldn't fathom why they weren't climbing. Overwhelmed by the noise of the warnings, the terrifying vibrations, and the wildly fluctuating instrument readings, his brain seemed to shut down, paralyzed by confusion and fear.
A very basic diagram like this would have probably helped the pilots understand what the plane was doing. (Flying Magazine)
By now the plane was falling toward the ocean at a rate of 10,000 feet per minute, and accelerating. The angle of attack was more than forty degrees. The only way to recover was to push the nose down, regain airspeed, and then pull out at a lower altitude. But Bonin just kept pulling his side stick back, forcing the nose up.
"Controls to the left," Robert said, still worried about their bank angle. Pressing the priority button on his side stick, he took control and locked out Bonin, but Bonin immediately pressed his own priority button and assumed control again.
Bonin said something which might be best translated as, "I have the impression that we're going crazy fast." His impression couldn't have been further from the truth.
At that moment, Captain Dubois returned to the cockpit to find a scene of chaos. "Er, what are you doing?" he said, glancing around in an attempt to figure out what was going on.
"What's happening?" Robert asked. "I don't know, I don't know what's happening!"
"We're losing control of the airplane," said Bonin.
"We lost all control of the airplane, we don't understand anything, we've tried everything!" Robert said, desperation in his voice. But in fact they had tried nothing at all.
"I have a problem, it's that I don't have vertical speed indication," said Bonin. His vertical speed indicator was working perfectly; he just didn't believe what it said. "I have no more displays!" he opined, although again, all indications were correct and all his instruments were working.
"We have no more displays!" Robert repeated.
"I have the impression that we have some crazy speed, no?" Bonin said. "What do you think?"
"So we're still going down," Bonin said.
"We're pulling," said Robert. "What do you think about it, what do you think — what do we need to do?"
"There — I don't know, it's going down!" said Dubois. He had made no effort to assume control, continuing to look over his first officers' shoulders instead.
As the plane plummeted toward the Atlantic Ocean, the pilots only became more confused and agitated. Recovery was already impossible; the fates of all on board were carved in stone. All that followed was a final, terrible fight to the death.
"The wings to flat horizon, the standby horizon!"
"The horizon!"
"Speed?"
"You're climbing!"
"You're going down, down, down!"
"Am I going down now?"
"Go down!"
"No, you're climbing!"
"I'm climbing, okay, so we're going down!"
"Okay what are we here? On altitude, what do we have here?"
"…It's impossible," Captain Dubois said, completely baffled.
"What do you mean, on altitude?
"Yeah yeah yeah, I'm going down no?"
"You're going down, yes!"
"Hey you, you're in — get the wings horizontal!"
"Get the wings horizontal!"
"That's what I'm trying to do! I'm at the limit with the roll!"
"We lost it all! I've got nothing here!"
"We're there, we're passing level 100!" Flight 447 was falling through 10,000 feet, still deeply stalled, headed straight into the jaws of oblivion.
"Wait, me — I have the controls!" Robert said. But Bonin didn't stop pulling up.
"What is… how come we're continuing to go down right now?" Bonin asked.
"Nine thousand feet!" Bonin cried out.
"Climb, climb, climb, climb…" Robert said, as though trying to will the plane to stop falling.
"But I've been at maximum nose up for a while!" said Bonin.
It was at that point that Captain Dubois finally understood what was happening. "No no no, don't climb!" he shouted. But it was already much too late to intervene. Not even the most skilled pilot on earth could have saved them.
CGI animation of the stall and crash. (Mayday)
These final moments of Air France flight 447 would go down in aviation history as some of the most tragic and the most baffling.
"So go down!" said Robert. "So give me the controls, the controls to me, controls to me!"
"Go ahead, you have the controls!" said Bonin.
"Watch out, you're pitching up there!" said Dubois. Incredibly, both Bonin and Robert were still hauling back on their side sticks.
"I'm pitching up," said Robert.
"You're pitching up!" Dubois shouted.
"Well we need to, we are at four thousand feet!" said Bonin. It was true, it was far too late to recover by pitching down. Not that it would matter anyway.
"PULL UP," said the ground proximity warning system. "PULL UP! PULL UP!"
"Go on, pull," Dubois said. Was this comment a sardonic resignation to fate?
"PULL UP! PULL UP!"
"We're going to crash!" Bonin cried out. "This can't be true! But what's happening?"
"Ten degrees pitch attitude," Dubois drily commented. His would be the last words on the cockpit voice recording. Less than two seconds later, with a forward airspeed of just 107 knots and a descent rate of 11,000 feet per minute, Air France flight 447 slammed belly-first into the Atlantic Ocean. In a fraction of a second, like so many candles, 228 lives flickered and went out.
A map from early in the search on the day of the crash. (BBC News)
It would not be until 4:00 a.m. UTC, nearly two hours after the crash, that controllers in Senegal began to realize that they should have heard from Air France 447, but had not. They tried everything — contacting nearby control centers, asking other planes, asking Air France — but no one had spoken to flight 447 since shortly before 2:00 in the morning. At 4:59, having tried and failed to establish contact with flight 447 via satellite, an Air France dispatcher told the Dakar control center that something must be seriously wrong. 24 minutes later, fearing that the plane had gone down in the Atlantic, Brazil and Senegal issued an alert to rescue services, and the search for the plane began.
The problem was that Air France flight 447 had apparently vanished within an area that had no radar coverage, no possibility of witnesses, and only spotty radio contact. No one knew exactly when or where the plane went down, and with each passing hour, any floating debris would drift farther from its point of origin. By the time the first search planes actually departed, more than ten hours had passed since the crash, and the debris was already scattering.
A Brazilian newspaper front page shows the faces of some of the missing. (Vanderlei Almeida)
Meanwhile, investigators with France's Bureau of Inquiry and Analysis (BEA) set up an elite team to investigate what promised to be the most complicated and most important accident in the history of French aviation. Although they didn't have the airplane, they didn't start with nothing: like all modern aircraft, the Airbus A330 regularly broadcasts data to the airline for diagnostic purposes. This system, known as ACARS, sent a burst of data approximately every ten minutes, with additional messages if certain warning conditions were met. The last regular message, sent at 2:10, indicated that there was a problem with the pitot-static system, the autopilot had disengaged, and the controls were in alternate law. Several additional messages sent between 2:10 and 2:14 indicated faults with the Air Data Reference units, the computers which process airspeed, and an abnormally high rate of descent. It was just enough to prompt speculation, but not enough to explain what had happened, or why.
A map of the surface search and its discoveries. (The New York Times)
One thing that investigators suspected from the very beginning was a problem with the pitot tubes. At the time of its disappearance, flight 447 was flying through storms in the intertropical convergence zone, the perfect conditions for pitot tube icing. This particular model of pitot tube had been shown on several occasions to experience ice accumulation greater than the heaters could remove, leading to a loss of airspeed data. In fact, Air France, Airbus, and the pitot tube manufacturer had been holding meetings on the matter since 2008, and earlier in 2009 a study had shown that a newer model of Thales pitot tube could significantly reduce the frequency of such incidents. Air France quickly ordered the new pitot tubes for all of its Airbus A330s, and the first airplane was retrofitted on May 30th, just hours before Air France flight 447 left Rio de Janeiro. Although the airline had been proactive, their efforts came ever so slightly too late for the 228 passengers and crew now presumed lost at sea.
But to know how exactly frozen pitot tubes, a relatively minor malfunction, could have led to the catastrophic crash of a wide body jet with a flawless record, investigators needed the black boxes. Everyone knew that they would be hard to find — but few could have guessed just how difficult it would turn out to be.
By the afternoon of June 1st, French officials had already acknowledged that there was "no hope for survivors," but the scope of the sea search only continued to increase. On June 2nd, a Brazilian plane spotted an apparent oil slick and light floating debris; on the 6th of June, two bodies were found, along with personal effects, and the plane's vertical stabilizer was located on the 7th. In all, by the end of June searchers had found over 600 pieces of the airplane and the bodies of 50 victims, including Captain Dubois. Engineering analysis of the debris and autopsies of the victims revealed that the plane had impacted the water in a nearly flat pitch attitude with a high rate of descent, but again, investigators couldn't say why. The answers, as ever, lay with the flight recorders.
Another view of the recovery of the tail section. (France24)
The A330's two black boxes were equipped with pingers that could be detected by specialized equipment, but the batteries which powered the pingers were only rated to last 30 days. Although authorities moved quickly to bring in search ships capable of detecting the pingers, their chances of finding the black boxes inside the 30-day window were slim. With the plane likely resting at a depth of up to 4,000 meters, surface vessels would need to get very close to the site of the wreckage in order to pick up the signal, and with no radar record, it was impossible to know with any specificity where the plane had actually entered the water. It was unfortunately no surprise that the 30-day period went by with no sign of the black boxes.
At that point, the search entered its third phase: a methodical sonar examination of an area extending 75 kilometers in all directions from the plane's last known position, as reported by ACARS. Carried out between April and May 2010, this search failed to turn up any sign of the plane. All data indicated that the plane should have been within the search area, but covering every square kilometer in detail was difficult, and a more precise search would be needed.
The fourth phase began in the spring of 2011, focusing on areas not covered by the previous search within a limited 37-kilometer radius around the last known position. This search began on the 25 of March, and had been in progress for just seven days when sonar imagery detected the presence of a large debris field on the ocean floor. On the 3rd of April, a submarine equipped with a camera reached the debris field, returning images that left investigators speechless: after nearly two long years, there lay Air France flight 447, shattered on the barren floor of the abyssal plain, four kilometers beneath the Atlantic.
(BEA)
Examining the debris field inch by inch, searchers managed to find the flight recorders by the beginning of May, followed soon after by several substantial chunks of wreckage and the bodies of a further 104 passengers and crew. Another 74 bodies were never found, having apparently been lost to the sea.
The much-anticipated readout of the black boxes occurred at the BEA headquarters in Paris in May 2011. At long last, investigators listened, transfixed, to the voices of the doomed crew on that fateful night in 2009 — voices that some had doubted they would ever hear. But as those haunting conversations played out over the two hour tape, it became clear that the black boxes would raise just as many questions as they answered.
Photos of various parts of the airplane as they were found on the ocean floor. (BEA)
By integrating the cockpit voice recorder and the flight data recorder, investigators were able to show that at the moment the airspeeds became invalid and the autopilot disconnected, First Officer Pierre-Cédric Bonin began to pull back on his side stick, raising the nose, and that he maintained this input almost continuously until impact. The data was indisputable; Bonin had stalled the airplane, sending it to its doom. But this explanation in fact explained very little. Every airline pilot should know that such inputs will lead to a stall, so why did Bonin seem to be oblivious to the danger?
The tail section of flight 447 is hauled aboard a salvage ship. (NBC News)
Answering this question proved to be by far the most complicated part of the entire investigation. Understanding what went through the minds of the pilots requires a second-by-second analysis of the final four minutes of the flight, considering all of the disparate cues which each pilot was trying to assimilate.
But first, it is critical to understand who Pierre-Cédric Bonin was as a pilot. In the popular consciousness, a pilot is a semi-heroic figure who flies a plane by hand, guiding it through all manner of dangers. Bonin was perhaps living proof that this type of pilot has not existed for decades.
In fact, the job of a modern pilot on a plane like the A330 is far more abstract. The average A330 pilot will hand-fly an airplane for maybe four minutes out of every flight, and will pilot only two or three flights a week, sometimes fewer. The vast majority of their time is spent programming automation, monitoring computer activity, and making broad, tactical decisions about the flight. Physical skill is far less important than emotional intelligence, good memory, and an ability to communicate. And on a highly automated plane like the A330, it's all but impossible to discover who possesses such physical skill in the first place.
Investigators lay out the recovered debris on the floor of a hangar for identification and analysis. (Der Spiegel)
Physical, or traditional, piloting skills are typically developed through extensive experience flying small aircraft which have little or no automation. These aircraft force a pilot to develop an intuitive understanding of how airplanes behave in various regimes of flight, and anyone who cannot develop these skills will wash out at an early stage. Captain Marc Dubois no doubt had these skills: between 1977 and 1987, he obtained type ratings on no less than 17 different light aircraft and accrued thousands of hours flying them. If he had been in the pilot's seat when the airspeed indicators failed on flight 447, there is little doubt that he would have reacted correctly: he surely had an intuitive understanding that, in the absence of any configuration changes, the plane will continue to fly on its previously established trajectory, even if all the instruments are lost — a sort of airman's object permanence. He would have known that all he needed to do was nothing.
The tail section is loaded onto a truck in port for transportation to the evidence hangar. (CNN)
Bonin, on the other hand, had a completely different background. He had followed a fast-track trajectory to the right seat of the Airbus A330, flying small planes just long enough to get his private and air transport pilot's licenses before being inducted into Air France with just a couple hundred flight hours. He was immediately trained to fly the advanced fly-by-wire Airbus A320, before upgrading to the Airbus A340 and finally the A330, all of which were heavily automated. Any rudimentary "traditional" skills which he had gained during his brief time flying light aircraft would have quickly degraded. Although Bonin would have learned about the principles of aircraft dynamics in a classroom setting, such instruction is an order of magnitude less valuable than getting to feel the principles in action while at the controls of a fully mechanical airplane. Instead, he spent the next 2,000 flight hours watching as computers flew the jet on his behalf. His total time actually hand-flying an airliner couldn't have been more than a couple dozen hours, all of them within the bounds of the flight envelope protections, which he knew made it impossible for him to lose control. If you asked him, Bonin probably could have told you what a stall is and how it works, but could he have identified one in real life?
A floating galley section was found, complete with intact drawers. (Reuters)
The extent of his stall-related training leaves room for doubt. Air France did not train its pilots on prevention or recovery from high altitude stalls, even though these have several fundamental differences from low-altitude stalls. If the stall warning activates during the initial climb away from an airport, a scenario which Bonin practiced many times in the A330 simulator, it is possible to avert the stall by applying maximum thrust and maintaining a nose up attitude of about twelve degrees. The denser air closer to sea level ensures that the plane is stable in such a configuration. But at 35,000 feet, this will not work: pitch angles as low as four or five degrees will be sufficient to activate the stall warning, and an actual stall will follow soon after.
However, all of that is hypothetical, because nearly all of the time, Airbus aircraft cannot stall. The flight envelope protections simply will not allow any inputs which raise the angle of attack above the critical point, and with these protections in place, there isn't even a stall warning, because a stall will not and cannot occur. A pilot can haul back on the side stick with all their might, and the plane will rear up to whatever angle the algorithms determine is safe. Nothing the pilot can do will make it pitch up more.
With these facts in mind, consider the scenario actually faced by the crew of flight 447. They were at high altitude where even a mild nose up input could quickly escalate into a stall. Bonin and Robert were probably only vaguely aware of this fact, which was rather esoteric in an environment where the flight envelope was clearly limited (although it was their duty to know it). And then suddenly all the protections vanish, as the loss of airspeed data forces the controls to slip into alternate law. After all, the computer can't protect against a stall if it doesn't know how fast the plane is going. Does Bonin know that the plane is in alternate law? And if he does, does he understand what that means? In theory it's his job to know, but he doesn't.
The complex interrelationship between measured and calculated flight parameters. (BEA)
At the moment that the airspeed data became invalid, a curious quirk of the plane's internal calculations might have set the whole sequence of events in motion. Because of the location of the A330's static ports, which measure the basic outside air pressure, the reading is somewhat affected by the plane's airspeed, due to leakage of rushing air into the ports. Generally this results in a slightly elevated static pressure reading. Because static pressure increases as altitude decreases, this design quirk would cause the sensor to continually underestimate the plane's altitude. To account for this, an algorithm applies a small correction to the static pressure reading based on the airspeed reported by the pitot tubes, in the process correcting the altitude to its true, higher value. But if the pitot tubes suddenly start reporting an erroneously low airspeed — say they're blocked by ice — the size of the applied correction will be smaller, and the plane's indicated altitude will decrease, even though it is in fact flying straight and level.
A recovery worker prepares the galley section for salvage. (The Guardian)
Consequently, at the moment the pitot tubes froze on Air France flight 447, the indicated altitude dropped by about 350 feet, and the vertical speed indicator briefly displayed a descent rate of 600 feet per minute. Bonin didn't comment on these figures, so we can't prove that he saw them. But if he did, it would explain his initial decision to pull the nose up: he probably thought the airplane was descending. And what did he think would happen if he pulled the nose up? Most likely, that the plane would climb at a protected angle, safely below the stall margin, no matter how hard he pulled back on the stick or how long he held it there. There was no need for such an extreme input, but it seems he was caught by the startle effect, feeling compelled to take drastic action, but without understanding what form that action should take, and believing that the computer would bail him out if he did something wrong.
It is somewhat more difficult to explain why Bonin kept pulling on the stick even after his instruments showed the plane passing back through its initial cruise altitude and continuing toward 37,000 feet. But his comments earlier in the flight, in which he repeatedly expressed a desire to climb above the weather, provide a possible reason. If he thought the plane would be out of the clouds at around 37,000 feet, and if he was concerned about the possibility of turbulence or other severe conditions inside the storm, his first instinct upon seeing the cascade of warnings might have been to try to escape from the area of bad weather. Perhaps he wanted to climb as high as the plane would let him, not knowing that all such protections had been withdrawn.
Another part of the galley was used to prove that the plane hit the water in a flat attitude. (BEA)
At the same time, there is considerable evidence that Bonin was more concerned about flying too fast than he was about flying too slow. Pilots in general were aware, to an almost superstitious extent, that exceeding the maximum operating speed could lead to the breakup of the airplane in flight, and that at high altitudes this maximum speed was not that much faster than the normal cruising speed. In fact, on an Airbus operating in normal law, the airspeed indicator in front of each pilot displays markers representing the maximum and minimum allowable speeds (as defined by the flight envelope protections), and the actual speed in cruise is usually much closer to the former than the latter. Many pilots, including Bonin, had probably developed a false belief that overspeed was a more pressing danger than stalling. In fact, it's the other way around: in the 20 years leading up to the crash of flight 447, there had been considerably more crashes involving high-altitude stalls than crashes involving overspeed-related breakup.
In light of these assumptions, when Bonin saw the plane appearing to descend in the first seconds after the failure, his instinctive reaction may have been to protect the plane against entering an overspeed condition. Furthermore, when the max/min speed markers disappeared during the transition to alternate law, his sense of where these boundaries lay became uncertain. This uncertainty, and the irrational fear of flying too fast, may have pre-conditioned him to ignore cues which indicated that he was actually flying too slowly.
It is also worth noting that Bonin and Robert had both undergone training on unreliable airspeed events, during which pilots were instructed to adopt a known power setting and pitch angle which would result in a stable flight path. However, much like the stall training, it was assumed that the most critical unreliable airspeed scenario is one which occurs at low altitude during initial climb. Although procedures for other phases of flight could be found in the manual, the training conditioned pilots to expect unreliable airspeed events during climb, to which they would respond with a steady nose-up pitch and high power setting that would ensure a shallow ascent. Such a response would be completely inappropriate in cruise.
A reconstruction of the warning messages the pilots would have seen during the event. (BEA)
Investigators found that because of this conditioning, in a dozen or so previous cases of unreliable airspeed in cruise on the Airbus A330 and the similar A340, not a single crew had correctly identified the anomaly and applied the stabilization procedure. In one case, the pilot even applied nose-up inputs which triggered a stall warning, although deviation from the flight path was ultimately minimal. Therefore Bonin and Robert were not the exception in failing to initially identify the cause of the malfunctions and apply the known solution. In all of these cases, part of the problem was that in the actual events, the loss of speed data was accompanied by a series of alarms and warning messages which were not present in the simulator scenarios, and none of these messages explicitly stated that there was a problem with the pitot tubes, contributing to pilots' difficulty identifying the root cause.
Debris lies of the floor of the hangar following recovery from the sea surface. (CNN)
Having pitched their plane up to the very brink of a stall, Bonin and Robert could have saved the day by reacting correctly to the stall warning which began to sound as the plane approached 38,000 feet. There are however several possible reasons why they ignored it. One is that their minds were already so saturated with information that they simply never heard it. Instrument indications were seemingly going haywire, nobody knew what instruments they could trust, the pilots were desperately trying to figure out what the plane was doing, the computer screen was covered in warning messages, and a continuous C-chord chime was running in the background. Scientific studies have shown that in such situations, the capacity of the human brain to tune out seemingly obvious auditory cues is considerable.
Another possible reason is that the stall warning had previously activated for three seconds shortly after the disconnection of the autopilot, when Bonin initially pitched up. At that time the stall warning was unexpected and difficult for the pilots to rationalize. Crews involved in similar incidents reported that they assumed the brief stall warnings were generated by the erroneous airspeed readings, a not unreasonable interpretation which breaks down only when one learns that the stall warning calculations are based on angle of attack and do not incorporate any airspeed data. Thus, the stall warnings in all such cases were real. But in a situation where they were not expecting a stall warning, and in which they might have believed the plane could not stall, it's not hard to imagine that Bonin and Robert heard the stall warning but simply didn't believe it.
The tail section lies on the deck of a Brazilian navy ship following its recovery from the sea. (Der Spiegel)
At this point, Robert, despite his greater experience, failed to stop Bonin from stalling the airplane, even though he appeared to recognize that his fellow pilot was pitching up too steeply. Investigators noted that during most of the period between the onset of the event and the stall, Robert was trying to interpret the warning messages and was not directly paying attention to the flight path. Although he did tell Bonin to "go down," Bonin's halfhearted response was apparently enough to satisfy him, as he went right back to analyzing the problem. It is also worth noting that Robert had the same non-traditional piloting background as Bonin; he was likely operating on little sleep; and he had barely flown since being promoted into airline management. All things considered he was just as unprepared for the situation as Bonin was.
Once the airplane actually stalled, the crew of flight 447 found themselves beyond the scope of anything they had learned in training. Training scenarios never allowed the stall to fully develop, in part because the simulators in use at Air France could not faithfully simulate the behavior of the aircraft after exiting the normal flight envelope. The scenarios thus focused on preventing stalls, not recovering from them, and while the pilots likely knew in principle that they would need to pitch down to recover from a fully developed stall, this knowledge would have been purely academic in nature. Neither Bonin nor Robert had ever attempted such a maneuver, not in a simulator and definitely not in real life.
What the flight directors would have displayed during the periods when they were active during initial climb and stall. (BEA)
This lack of practical knowledge combined with several conflicting cues to cement Bonin's pre-established desire to pull up and climb. One of these cues came from the flight director, an overlay on the pilot's attitude indicator which provides command bars that the pilot can follow in order to achieve a desired flight path. Normally the flight directors will disappear if the airspeed data becomes unreliable, and at first they did. But if the pilots don't turn them off, they will come back as soon as two of the three Air Data Reference computers provide it with airspeed readings that are consistent with one another. On flight 447, the pilots never attempted to turn off the flight directors, and they came back as soon as the pitot tubes unfroze and the airspeed data became valid again, which occurred just before the onset of the stall. Not knowing the intentions of the crew, when the flight directors come online, they automatically instruct the pilot to maintain the current trajectory, until the pilot programs them to do otherwise. The result was that the flight directors re-engaged not in cruise mode, but in vertical speed mode with a target climb rate of 1,400 feet per minute — the exact rate at which flight 447 was climbing at that particular moment. From then on the flight directors, whenever they had valid data, instructed the pilots to attain an approximately 12-degree nose up attitude in order to reach this target vertical speed. Flight data indicates that at several points during the stall, Bonin may have been attempting to follow this erroneous flight director instruction.
A BEA investigator sorts wreckage in the hangar. (Eric Cabanis)
In fact, by coincidence the target pitch angle displayed by the flight director was almost exactly equal to the target pitch angle Bonin had learned to use while powering out of a low-altitude stall. This finding raises the question of whether Bonin thought that following the flight director would lead to the stabilization of the flight path. This interpretation is supported by Bonin's comments to the effect that high power and a high pitch angle should cause them to climb. It seems likely that he not only thought he was flying the stall avoidance procedure, but that he believed the flight director was instructing him to do so as well. He apparently never recognized that the plane was already in a fully developed stall, and that this procedure was completely irrelevant to their actual situation.
During flight 447's plunge toward the sea, the flight directors disappeared every time the forward airspeed dropped below 60 knots. This was because an airspeed below 60 knots while in flight is so anomalous that the computers are programmed to reject such a reading as false. Furthermore, at an angle of attack threshold which corresponded quite closely to 60 knots, the stall warning would cease for exactly the same reason. This created an unfortunate correlation, wherein Bonin would pitch up, the angle of attack and airspeed would exceed the rejection thresholds, the flight director would stop telling him to fly up, and the stall warning would cease; then if he attempted to pitch down, the angle of attack data would become valid again, the flight director would tell him to pitch up, and the stall warning would return. This perverse Pavlovian relationship could have subconsciously conditioned Bonin to believe that pitching down was causing the plane to approach the stall envelope, and that by pitching up he was actually protecting the plane against stalling. This violated basic aeronautical common sense, but by this point Bonin and common sense might as well have been on different planets.
BEA investigators present the black boxes. (CNN)
David Robert, had he taken decisive action, could perhaps have saved the plane if he had recognized that Bonin was causing the stall. At times he seemed aware that Bonin was pulling up, at times not; but many experts believe that the very design of the Airbus made it harder for him to understand his copilot's actions. Unlike most other airliners, the control sticks on Airbus models are not mechanically linked and the pilots cannot directly feel what the other pilot is doing. Although this usually doesn't present a problem — in the course of normal flight, pilots rarely touch the side stick —this can become a liability in an emergency situation involving a breakdown in communication. The design of the side stick assumes that the pilots are well-trained in crew resource management and are communicating their actions to one another, but this ideal appears dangerously naive in light of the confusion on the flight deck of Air France 447. Airbus has stuck to its guns, and no change of the side stick design appears imminent, but the debate rages on, and it is widely believed that a linked side stick could have allowed Robert to recognize and correct the situation well before Dubois arrived to bail him out.
Unfortunately, by the time Captain Dubois entered the cockpit, the stall was already well advanced and their chances of survival were slim. Had he immediately recognized the problem, kicked Robert out of his seat, locked out Bonin from the controls, and executed a flawless stall recovery maneuver he might have saved the plane. But despite his expertise, he only seemed to realize what was happening shortly before impact. His difficulty understanding the situation could be explained by the first officers' panic, the large number of extraneous indications and alarms, and the fact that he was operating on one hour of sleep. In theory, he should have seen that they were pitched up with the engines at high power and descending rapidly, a configuration that could only mean they were in a stall; there was no other explanation. But for whatever reason, he didn't make the connection. In the fog of confusion, it took him too long to put two and two together, and by the time he did, he already knew there was no hope of recovery.
A BEA investigator presents the findings of the investigation. (Mehdi Fedouach)
In the end, there is no single interpretation of the situation which fully explains why Bonin did what he did. In all likelihood, his actions were the result of a confused mixture of conflicting ideas, which caused him to make decisions which were based on completely contradictory scenarios. Did he think they were in overspeed, or did he think he was applying a stall recovery procedure? The answer may not be either-or; in such a state of mind, rational thought tends to break down, and moment-by-moment instincts take over. It's entirely possible that he held both opinions during the fatal descent, maybe even at the same time.
Flight attendants mourn their colleagues at a memorial service at the Notre Dame. (The Guardian)
Looking back on this bewildering body of evidence, the loss of Air France flight 447 kind of starts to make sense, in a distorted sort of way, like real life reflected in a funhouse mirror. We can start to see how a pilot who fundamentally does not understand his aircraft could fall into this trap, grasping wildly at trees without seeing the forest. What Bonin and Robert needed was aeronautical common sense, and they didn't have it. It is so easy for those of us who have read about Air France flight 447 and similar accidents to point the finger and say the accident was Bonin's fault, that he alone killed 227 other people. But such an accusation ignores the fact that Bonin was systematically underprepared for the situation in which he found himself. It is easy, from the vantage point of 2021, living in a world where Air France flight 447 has become one of the most studied accidents of all time, to say that he should have known better. And indeed he should have, but that's not the point: the point is that Bonin was only a symptom of a deeper problem.
French Prime Minister Francois Fillion meets with Air France crews at a ceremony for the victims. (Antonio Scorza)
In fact, Air France flight 447 represented a turning point in how the global aviation industry approaches the subject of automation. There is no denying that automation has made flying much safer; the data supporting this conclusion is irrefutable. But amid the swift march of progress, it is important not to lose sight of the foundations on which that progress is built. Just like Alternate Law always lurks beneath Normal Law, underneath a layer of automation there lies the same need for traditional piloting skill that has always existed, and will continue to exist for the foreseeable future. We catch fewer glimpses into that realm than we used to, but it is still there, visible whenever something goes wrong with the automation. The fundamental paradox, one outlined by famed aviation author William Langewiesche, is this: the rarer such moments become, the harder it is to ensure that pilots are ready for them; and yet at the same time, their readiness becomes all the more important. After the crash of flight 447, solving this paradox became the foremost priority of aviation safety experts around the world, and the fruits of their efforts are only now becoming apparent.
A memorial to the victims of flight 447 evokes 228 transparent birds in flight. (Bertrand Langlois)
Today, flying is not the same as it was in 2009, when Dubois, Robert, and Bonin boarded their Airbus A330 for the last time. Training again emphasizes basic piloting skills and aeronautical common sense; high altitude stalls are a major training topic; and increased simulator fidelity has allowed the widespread introduction of Upset and Recovery Training, now mandatory in the United States and Europe, which confronts pilots with extreme situations and forces them to fly their way out. There are some pilots out there who still lack these skills, but there are surely fewer of them now than there were ten or fifteen years ago. A marked decline in the number of major airline accidents in the second half of the 2010s has testified to this fact. But it would be a mistake to believe that the problem is, or even can be, fully solved. As long as humans fly airplanes, some amount of information will always be lost while translating between man and machine, and from these imperfections spring the seeds of catastrophe. The next major crash of a large airliner, wherever it may occur, will almost certainly have something to do with the interaction between pilots and the automation that they oversee. In the meantime, it would be beneficial, even for those of us who are not pilots, to look on the events of Air France flight 447 and accept that we are human, that our capacity to err is unbound by reason, and that the best way to avoid disaster is to learn from the mistakes of others.

redpajama_set_name: RedPajamaCommonCrawl


...The question was: What happened to the Greeks that lived in Asia minor and occupied Constantinople from time immemorial?
And there are more Irish living in the US than in all of Ireland so what is your point?
And what does the fact that more Greeks live in the US, Canada or Australia than even in Greece itself have anything to do with any thing except in ther mind of an insecure Turk like you? And could it there are more Greeks all over the world because the Turks and their imperialism took Asia minor away from the Greeks and then expelled the rest of them in 1922 and killed thousands of them in 1963? And you would agree with me that if the Turks would not have left miserable central Asia and invaded the Byzantine Empire all those Greeks in the US and Australia and Canada might be still living in Asia Minor and your likes will be living in miserable central Asia? What do you think ya ayuha al-faylasoof al-kabeer?


text:
Exclusive insight: Concept study ŠKODA VISION iV features new, innovative interior concept
New interior concept with various levels and a seemingly floating monitor
New layout of instrument panel and centre console
ŠKODA VISION iV combines high utility value in everyday life with functional ergonomics
World premiere of the all-electric concept study at the Geneva Motor Show
Mladá Boleslav, 20 February 2019 – An interior sketch of the ŠKODA VISION iV provides an outlook on surprising solutions in ŠKODA's first all-electric vehicle based on MEB (Modular Electric Drive Kit). The innovative, user-friendly arrangement of the instrument panel and centre console creates new accents. There is also a seemingly free-floating central screen and a newly designed two-spoke steering wheel.
The all-electric concept study VISION iV offers an outlook on the interior of the first ŠKODA based on the Volkswagen Group's Modular Electric Drive Kit (MEB). The traditional centre tunnel is not used – so the ŠKODA designers used the possibilities of the new MEB platform to create a spacious and innovative interior. For example, they reconfigured the layout of the instrument panel and centre console. Between the driver and the passenger seat, the VISION iV offers plenty of storage space on the lowest level, above which there is a centre console that is particularly easy to reach for the driver and front passenger. Two mobile phones, which can be wirelessly integrated into the infotainment and operating system, can be placed in the console while they charge inductively.
The instrument panel consists of two levels whose lines and decorative stitching draw inspiration from the front of the vehicle. The large free-standing screen appears to hover centrally above the instrument panel, in front of which there is a ledge for the hand that operates the touch screen. The steering wheel has also been redesigned, now featuring two spokes and 'ŠKODA' in block capitals in place of the familiar ŠKODA logo.
ŠKODA is taking another step towards electromobility with the VISION iV. Over the next four years, the Czech carmaker will be investing around two billion euros in alternative drive systems and new mobility services. The brand will have introduced ten electrified models by the end of 2022.
The world premiere of the ŠKODA VISION iV concept study takes place at the Geneva Motor Show from 5 to 17 March.
Follow us on Twitter https://twitter.com/skodaautonews, for all the latest news. All content on the ŠKODA VISION iV study can be found using the hashtag #VISIONiV.


text:
using Microsoft.VisualStudio.Debugger.Evaluation;
using Microsoft.VisualStudio.Debugger.Evaluation.ClrCompilation;
using System.Diagnostics;

namespace Microsoft.CodeAnalysis.ExpressionEvaluator
{
    internal static class ValueHelpers
    {
        internal static string IncludeObjectId(this DkmClrValue value, string valueStr)
        {
            Debug.Assert(valueStr != null);
            if (value.EvalFlags.Includes(DkmEvaluationResultFlags.HasObjectId))
            {
                string alias = value.Alias;
                if (!string.IsNullOrEmpty(alias))
                {
                    return string.Format("{0} {{${1}}}", valueStr, alias);
                }
            }
            return valueStr;
        }

        internal static bool HasExceptionThrown(this DkmClrValue value)
        {
            return value.EvalFlags.Includes(DkmEvaluationResultFlags.ExceptionThrown);
        }

        internal static string GetExceptionMessage(this DkmClrValue value, string fullNameWithoutFormatSpecifiers, Formatter formatter)
        {
            return string.Format(
                Resources.ExceptionThrown,
                fullNameWithoutFormatSpecifiers,
                formatter.GetTypeName(new TypeAndCustomInfo(value.Type)));
        }

        internal static DkmClrValue GetMemberValue(this DkmClrValue value, MemberAndDeclarationInfo member, DkmInspectionContext inspectionContext)
        {
            // Note: GetMemberValue() may return special value when func-eval of properties is disabled.
            return value.GetMemberValue(member.Name, (int)member.MemberType, member.DeclaringType.FullName, inspectionContext);
        }
    }
}

redpajama_set_name: RedPajamaGithub


text:
Q: Strategies for workflow use case I have a shopping cart kind of use case  where in the user performs a sequence of steps across several pages
Below are the alternatives that I considered for storing the conversation state

*

*Httpsession

*Http request parameters

*Store the intermediate state of each page in data base table

I am planning to use the third approach due to the below reasons

*

*Our architecture is to avoid usage of httpsession and sticky session cofig so that all services are completely stateless

*Handling too much data in request parameters is messy

Please revert if you have ay concerns with the third approach.
Is spring web flow a viable option . Is that using httpsession internally ?

redpajama_set_name: RedPajamaStackExchange


text:
You'll read abu pn o h-rtrfsalrout o, renovations and much more.
Easter Sunday Sunrise Service
Photographs by Julia Qualizza
Church Camp 2017
August 21st to 25th
Article and photos by Terry MacHardy
Energy filled St. Andrew's United Church August 21st to 25th, 2017 as twenty local youth and eight camp leaders participated in a multi-denominational children's summer camp. The camp was sponsored by the congregations of St. Andrew's (Pakenham) and Zion (Cedar Hill) United; St. Mark's (Pakenham) and St. John's (Antrim) Anglican; and St. Peter Celestine Catholic (Pakenham) churches and was open to any child age 5 to 12. It was a busy action-packed week with special guests, games, singing, art and crafts, learning and eating.
Our thanks to the many people who worked very hard to make it all a success.
Special thanks to Terry MacHardy, Official Photographer and Reporter
Front row left to right
Smartie (Jennifer Smart), Keith Bristol, Jacob Smart, Ashton Barron (behind),
Declan Needham, Hudson Carron, Bryan Barr, Hollie Fotherby, Makenna Wing
Middle row behind Hollie
Dawson Brisco, Craig Villeneuve, Mason McLeod, Jazz (Laurie Boon)
Back row left to right: Bee Bee (Bev Higginson), Grandma Bear (Bronwen Harman), Ben Smart, Noah Reid, Analiesa Reid, Ava McLeod, Olivia Fotherby,
Owen Coe, Cole Currie, Braxton Barr, Rider (Jeff de Jonge).
Missing from photo
Marigold (Marilyn Snedden), Peppermint (Peggy Kuzmicz),
Cocoa (Terry MacHardy), Daria Sullivan
Day One: Getting to Know You
Campers made name tags for the week and played a scavenger hunt to find new friends. Old camp songs were sung and new ones learned. Music was lead by Jazz (Laurie Boon) our camp music co-ordinator.
Name tags help us get to know each other
Day Two: Indigenous Peoples' Day
Gramma Bear (Bronwen Harman) camp co-ordinator and storyteller, introduced special guests Irvin and Carrie Sarazin from Pickwocknagon (Golden Lake) who shared stories, songs and traditions of the Algonquin Peoples. Everyone experienced a Smudging Ceremony, learned about Sacred Circles and how to make a drum. Campers made medicine pouches to take home. The children were intrigued by the intricate beading on the Peppermint's (Peggy Kuzmicz) Cree stole and they tried on Jazz's red Inuit parka which has been in her family for generations.
Day Three: Pioneer Day
Campers were excited to learn about the early fur trade and to touch and feel the many furs (wolf, bear, fox, muskrat, beaver, skunk and others) shared by our special guest and local trapper, Lyle Cavanagh. Marigold (Marilyn Snedden) and Cocoa dressed up in historic costume and Marigold told the campers about the one room school house experience. Campers had a "shaking" good time learning to make butter a sample of which they got to take home. Jazz, our games co-ordinator burned off some of the camper's energy with pioneer games like three-legged and potato sack races and in her music co-ordinator role, played her guitar and taught us the Log Driver's Waltz dressed as a log driver.
Day Four: Multicultural Day
Rider (Rev. Jeff de Jonge) wore his wooden shoes and shared his Dutch family history. Marigold shared her Scottish family history. Campers shared their knowledge about their own family heritage. Everyone learned that most families in this area originated in Ireland, Scotland and England, but that we also have lots of friends and neighbours from many other countries all over the world who enrich our country with traditions and dress that is different than ours. Campers and leaders connected their family's originating country with Canada using string and pins on a big world map and made a multi-cultural collage. Snacks for the day were Salsa, Pita, Hummus and Taco Chips thanks to Bee Bee (Bev Higginson) our camp snack co-ordinator.
Day Five: Canada 150 Celebrations
The singing of O Canada followed our opening prayer. There were lots of games, laughing, singing and eating. Campers decorated their own cupcakes and loot bags with the help of Smartie (Jennifer Smart) and Cocoa (Terry MacHardy) our craft co-ordinators. Gramma Bear read us a story about places across Canada and we were encouraged to take the opportunity to travel, visit and explore, and to remember how privileged we are to live in this beautiful country. Everyone signed a big poster card to thank all the parishes that contributed to making this year's Canada 150 Summer Church Camp – "A Camp to Remember".
On September 1st, 2017 St. Andrew's was again filled with community spirit, hospitality and fun. The annual Fish Fry, which served 314 folks, was another huge success thanks to the team led by Lisa Gillan.
Diners enjoyed fish and fries supplied by Mundell's Surf and Turf and corn very generously donated by Hudson Farms. Homemade coleslaw and pies (all 60 of them) were a big hit.
Our numbers were down slightly, a reality attributed to having the event on the Labour Day long weekend, but we still made a healthy $2,657.40.
Our sincere thanks to:
the Hudson family for donating all of the very yummy corn and their time to husk and cook it;
the Centennial Restaurant for generously donating butter packets;
Marilyn Snedden for offering space in her freezer for leftover items; and
our volunteers who cheerfully helped with all of the jobs that need doing for a big event like this.
Special thanks go out to the kids of St. Andrew's who, with their best manners, enthusiastically helped by doing anything and everything they were asked to do. We have the best kids!
There were lots of positives this year. We were able to get people seated more efficiently so there was less time waiting upstairs, there was enough food left at the end of the event for the volunteers on the second shift to sit down and eat instead of going home hungry (our volunteers are the AWESOME!), despite the long weekend lots of folks stepped up to help, and those who couldn't help in person donated food items or made donations.
St. Andrew's is still and always about community, hospitality and fun.
Book Store in Stewart Hall
We have children's books, cook books, works of fiction, gardening books.
If you like to read it we have it.
You are invited to donate lightly used, current books as well as purchasing something to take home.
Sales go to operating expenses. We need a large bookcase & bookends.
Rosie and the Riveters
The Festival of Small Halls (FOSH) made its second appearance in Pakenham on September 23rd bringing Rosie and the Riveters to the St. Andrew's stage. The concert began with Arnprior native Vicki Brittle as the warm up act. Vickie performed a half-hour of original music.
Rosie and the Riveters then performed a show of sassy, upbeat, rockin' music as the main event. What a fabulous show! They were perfection. Their voices were superb, the harmonies tight, the original songs poignant, funny, topical and relevant. The audience showed its appreciation with a loud, sustained standing ovation – very well earned!
We're hoping they'll be back in the area soon!
Our thanks to the FOSHs staff and the ladies of St. Andrew's who cooked a delicious meal for the performers and FOSH workers.
Visit Rosie and the Riveters at: https://www.facebook.com/rosieandtherivetersband/
Caring for our Beautiful Church
2017 Maintenance & Repair of the building is complete. The work, done in September, was mostly on the tower and south side of the building and included repointing and painting.
Tutti in Concert
"With Glowing Hearts
Photograph by Lorne Reuckwald
Tutti sang up a storm for Canada 150 with a concert series entitled "With Glowing Hearts". They performed their final concert in this series at St. Andrew's on Sunday, October 1, 2017.
Tutti, (pronounced too-tee) is a female vocal ensemble formed in 2014. The ensemble is directed by Lisa Webber, a well-known mezzo soprano soloist, private voice teacher and choral conductor. Tutti's accompanist is the incomparable Elizabeth Brumm.
Depending on the season Tutti presents an eclectic program of sacred music, old favourites, spirituals, carols, folk songs and well known Broadway tunes. Tutti makes its concerts fun by creating a relaxed atmosphere and presenting a mix of ensemble pieces, duets, solos and sing-along numbers.
The With Glowing Hearts concert was filled with gems by Canadian artists such as Joni Mitchell, Gordon Lightfoot and Leonard Cohen, songs that celebrate Canada from the Maritimes to the Rockies and even songs about the weather – a favourite topic of conversation for Canadians.
We hope this great group of ladies will consider a return engagement!
177th Anniversary Service
Photograph by Marilyn Snedden
St. Andrew's was pleased to welcome The Honourable Peter Milliken,
former Liberal MP of Kingston & the Islands (1988-2011); Former Speaker of the House (2001-2011); and Grand-nephew to Art & Elsa Stewart as guest speaker for its 177th anniversary service. Mr. Milliken's talk was entertaining, informative and humourous. All who attended had an opportunity to speak to Mr, Milliken after service at a luncheon where Mr. Milliken was happy to catch up with some of his Stewart relatives (see photograph below).
Our sincere thanks to the following people for working to make this happen:
Rob McCann for suggesting and contacting Mr. Milliken;
the Worship and Life Committee, led by Chair Joan Gillan, along with Jeff who prepared the service;
Marilyn Snedden who led the service;
Rhonda Tees who wrote the introduction for Mr. Milliken;
Cathy Lacroix who purchased locally made gifts for a thank you basket, read the introduction and thanked Mr. Milliken; and
the Special Events Committee, led by Shirleen Duncan, who prepared and hosted the luncheon.
On Saturday, November 25, 2017, our guests were treated to the glorious sounds of harp and voice.
Directed by Mary Muckle the Ottawa Youth Harp Ensemble including: Noelle Aldous, Ashley Behrens, Erin Dallaire (guest harpist), Sarah Dolan, Sofia El Chaar, Lydia Enzinas, Alexia McNamer, Jacinta Ponesse, entertained us with Christmas and seasonal music.
The highlight of the concert was six year old Sofia El Chaar who stole the show.
Sophie sang and played " Sofia's Song". The words are "Sofie, Sofie, that's my name Sofie, I can play on the strings of my big harp".
A Christmas Celebration
A Christmas Celebration has become a favourite annual concert for those wishing to be filled with the holiday spirit. We were delighted this year to host LMJ at St. Andrew's and hope for a return engagement.
A Christmas Celebration in Story and Song featured seasonal favourites and stories about the songs performed by Lisa Webber, Mike McCormick and James Hrkach.
They delighted the audience with a widely varied program, exceptional a capella harmonies and beautiful guitar and piano accompaniment.
They were rewarded with a loud, sustained standing ovation.
Truly a night to remember!
In November we set up a permanent Food Bank containers. St. Andrew's members have been generously filling the bundles each week to help meet our monthly challenges. For more information on what you can bring this month and how we have done in previous months click here.
If you'd even like to volunteer to occasionally drop off the food and donations contact Cathy Lacroix or Joan Gillan.
St. Andrew's glowed with candlelight both inside and out on Christmas Eve 2017.
Photos by Cathy Lacroix
Photos by Julia Qualizza


Glacier Vehicles wants to provide you with a comprehensive, added-value service, and not just to sell you a vehicle By understanding the way you operation works, and the daily activities that your staff will do, we provide the best vehicle to match the exact operational requirements of your business. Glacier Vehicles has helped many businesses grow, and want you to grow too, so that you come back again and again whenever you need to increase your fleet of refrigerated transportation vehicles. Avoid delivery disappointments by working with a company that understands bespoke refrigerated van services.
Do you want to save money on a new vehicle by buying a used refrigerated vehicle in Kilmarnock? When it comes to used fridge vans our dealership is the premier place to go. Transport and logistics industries are diverse and require temperature control vans to meet lots of different needs. Your business will be different from all the other companies out there, even those that do the same types of things. The process you go through when you choose a used refrigerated van, or a whole fleet of them, has to be comprehensive and appropriate to your business. Refrigerated vehicle experts in Kilmarnock ready to help you Very few companies can beat the 20 years of experience the Glacier Vehicles has of producing quality reports and providing the right vehicles to businesses. The experience of Glacier Vehicles, stemming from two decades of operation in the industry, has made us the leading name to count on for businesses looking for the very best solutions in the refrigerated van industry. Understanding your business is key to getting the right vehicle, and Glacier Vehicles has so much experience looking at operational requirements that we know what to do. The consequences of making the wrong decision with your van can be very expensive. When something is overlooked in the decision making process when buying your refrigerated van it could prove costly in the long run, so avoid the mistakes by working with trusted professionals.
Very few companies in the UK marketplace are able to rival Glacier Vehicles when it comes to our reputation for value for money, quality and service. The skilled and experienced transportation sales consultants at Glacier can help you get exactly what you need from a conversion, or exactly what you need from an existing model on the forecourt. At Glacier Vehicles we make sure that our conversions are well thought out and strategic so they match your operational requirements. If you are looking for bespoke conversion, a used van, or a new van, Glacier can show you examples to help you make the right decision, and can even provide you with a demo. Every vehicle that is sold by Glacier Vehicles is performance tested by specialist engineers, HPI cleared and ready to roll into the business operation.
We strive at all times to stock all of the different refrigerated van brands so you have as much choice as possible. Our brand list includes Vauxhall, Nissan, Peugeot, Volkswagen, Iveco, Renault, Mercedes, Toyota, Fiat, Citroen and Ford refrigerated transportation vehicles. We also have multiple different models of different brand bands, and frequently have over 20 Ford, Mercedes and Volkswagen vans. With so many options available it can be confusing knowing how to choose the right van, but we guide you to the right vehicle every time. Make the right decision today and choose glacier vehicles as your next provider of refrigerated transportation.
By providing excellent service we strive to retain customers rather than just make individual sales. Our goal is always to offer the best possible sales and after sales service that we can. Our testimonials provide you with a glimpse into the positivity and satisfaction our customers feel towards our service. You will get a lot of peace of mind that we are the company for you when you read what people have to say about us. Whatever your business needs, whether it be a single van or a whole fleet, Glacier Vehicles are on the end of the phone to advise, guide you and get you the right refrigerated van in Kilmarnock.


FEELING OVERWHELMED OR DISHARMONIOUS WITH YOUR TRUE SELF - Feeling overwhelmed or easily overburdened. You may be looking for services and tools to help achieve deeper relaxation and connection with self.
OVER ABUNDANCE OF "NEGATIVE " PROTECTIVE THINKING FROM UNKNOWN SOURCES - Need help with negative thinking, confusion, and ill thoughts. You may have tried many self-help services and now you are ready for greater commitment and change.
INDECISIVENESS OR EASILY DISTRACTED - Difficulty with overthinking and indecisiveness. You may want a hands-off "accountability" partner or someone to bounce off ideas for clarity.
UNHEALTHY WELLNESS HABITS - Overcoming unhealthy eating habits and lack adequate movement. May have tried everything under the sun. Want to find a more intuitive and respectful way to work with your body.
DISCONNECTION FROM LINEAGE OR GENETIC ANCESTORS - Feeling disconnected from ancestral spiritual tradition and long to immerse yourself in your ancestral spirituality. Looking for a non-dogmatic system to help bridge the gaps.
HAVE A BROKEN SPIRIT OR LACKING IN WILL - Some may feel they have a broken spirit or lack a strong will to achieve heart's desires. You may be seeking deeper connection to your authentic self.
NEED TO OVERCOME FEARS AND REACH GOALS- Some just want to understand, cope with and overcome a nagging feelings or "undertone" of fears or insecurity. You may want to dive deep to uncover the real issues holding you back from a more fulfilling life.
I've worked with people just like you for over two decades to help them overcome these challenges using complimentary and earth honoring services and tools.
Start with a consultation which identifies the 12+1 laws which govern your life. These are based on your unique DNA or genetic codes.
During this session, we will also determine our fit for working together. Sometimes timing is also not right. We consider all options.
Then if we decide to work together, we map out a plan based on where you are now.
I offer integrative healing strategies that are inclusive. I draw on African, indigenous systems, metaphysics and earth-based wisdom traditions from around the world. I use the wellness healing arts and spiritual arts in one-on-one or in community. My clients and students are the "Soulful woman" who is earth-honoring, spiritual, and/or creative. She is sometimes multifaceted and multi-potential which can be both a source of comfort and pain.
As a community, we are a heart-centered, open-minded, compassionate, and loving. We respect the uniqueness of our Soul journey. For the spiritual seeker, I also offer lineage and African-based spiritual system mentoring on an annual basis.
* I also offer a simplified income sensitive option for those who are in need. Send me an email at [email protected] for more information.


text:
SC disallowed Bharti Airtel from seeking Rs. 923 Crore GST refund by rectifying return
Court :
Brief :
The Honorable Supreme Court of India in the matter of Union of India v. Bharti Airtel Ltd. and Others [CIVIL APPEAL NO. OF 2021 (ARISING OUT OF S.L.P. (C) NO. 8654 OF 2020) dated October 28, 2021] barred telecom major Bharti Airtel ("the Respondent") from seeking Goods and Services Tax ("GST") refund of Rs. 923 crore by rectifying retur
ARISING OUT OF S.L.P. (C) NO. 8654 OF 2020
The Honorable Supreme Court of India in the matter of Union of India v. Bharti Airtel Ltd. and Others [CIVIL APPEAL NO. OF 2021 (ARISING OUT OF S.L.P. (C) NO. 8654 OF 2020) dated October 28, 2021] barred telecom major Bharti Airtel ("the Respondent") from seeking Goods and Services Tax ("GST") refund of Rs. 923 crore by rectifying return.
Facts- The brief facts of the case were that the Respondent was facing several problems while their filing of GSTR Form 3B due to the several glitches that were occurring in the Online GST Portal. Amidst these glitches, the Respondent filed their GST returns for the period of July, 2017 to September, 2017 with excess amount of ₹ 923 Crores and therefore, they have sought the refund accordingly.
The Delhi High Court [W.P. (C) No. 6345 of 2018 dated May 05, 2020] – Held that the rectification of the return for that very month to which it relates was imperative and, accordingly, read down para 4 of the Circular No. 26/26/2017-GST dated December 29, 2017 to the extent that it restricts the rectification of Form GSTR-3B in respect of the period in which the error has occurred.
Accordingly, the Delhi HC allowed the present petition and permitted the Respondent to rectify Form GSTR-3B for the period to which the error relates, i.e. the period from July, 2017 to September, 2017. The Delhi HC also directed the Respondents that on filing of the rectified Form GSTR-3B, they shall, within a period of two weeks, verify the claim made therein and give effect to the same once verified.
In July 2020, the Central Government ("the Appellant") moved to the Supreme Court challenging the Delhi HC order of grant of refund. While authorities claimed the Respondent had under-reported Input Tax Credit ("ITC") from July, 2017 to September 2017, the Respondent said it had paid excess tax of ₹ 923 Crore on inputs based on estimates since the Form GSTR-2A was not operational during the error period.
The Supreme Court [CIVIL APPEAL NO. OF 2021 (ARISING OUT OF S.L.P. (C) NO. 8654 OF 2020)]- Allowed the Appellant's plea against the Delhi HC Order that had directed to issue the tax refund to the Respondent by rectifying its GST return for July, 2017 to September 2017 and observed as under:
"despite…an express mechanism provided by Section 39(9) of the Central Goods and Services Tax Act, 2017 ("the CGST Act") read with Rule 61 of the Central Goods and Services Tax Act, 2017 ("the CGST Rules") it was not open to the High Court to proceed on the assumption that the only remedy that can enable the Respondent to enjoy the benefit of the seamless utilization of the ITC is by way of rectification of its return submitted in Form GSTR 3B for the relevant period in which the error had occurred. Any unilateral change in such return as per the present dispensation, would have cascading effect on the recipients and suppliers associated with the concerned transactions".
Published in GST
Other Latest Judgments
IGST and Compensation Cess on goods re-imported after being exported for repairs would be wholly exempt
Under valuation of goods in invoice cannot be a ground for detention of the goods and Vehicle
Delhi HC dismisses conducting of alleged parallel investigation by various jurisdictional authorities
Proceedings u/s 271(1)(c) on account of furnishing inaccurate particulars of income
Can TDS be recovered from the payee in view of settled judicial principle?
Disallowance of interest expenses under the provisions of section 14A of the Income Tax Act
Is the issue of making the addition under clause (f) of section 115 JB debatable?
Penalty levied u/s 271(1)(c) w.r.t capital gain not disclosed in the Income Tax Return
Deduction of employees' contribution to PF and ESI u/s 43B of the Income Tax Act
Is it settled position of law that consent does not confer jurisdiction?
View More Judgments »
Subscribe to Judiciary Feed
Shares & Stock


Your One Stop Tin Shop - Located in Melfort!
Whether you are looking for tin to re-roof, use for siding or to construct an outbuilding. Mel-View can handle your needs! We also sell pre-built sheds and outbuilding packages. Need it set up? No Problem! We can do that as well !
Due to the demand of our sheds we have decided to change up the style and go bigger!! We are now offering all steel pre-engineered sheds in a new, larger design.
Melview Metal can supply you with complete metal siding kits with custom flashing. We also can build you a Portable Shed or Storage Shed of any size.
Products such as; EZ Liner, Gentek, Vinyl Siding, Dektite, TR-36, Low Rib, Snap-Tite, PBR Tuff Rib Closures & Screws, & Custom Flashing are available as well.
Melview Metal: Your One Stop Tin Shop !
Thank you for coming to our web site. I would like to introduce our company, Mel-View Metal. Included on this web site is information on Roofing, siding and many of our projects.
If you have any questions about details, engineering or products, please contact us. Our crew are not just roofers but craftsmen in metal. We have been specializing in metal roofing and custom metal siding since 1999.


text:
Ubisoft, Northern Arena partner for 'Rainbow Six Seige' tournament
The all-Canadian tournament has a $15,000 prize pool
By Jonathan Lamont@Jon_Lamont
Ubisoft Canada is partnering with Northern Arena to host the Rainbow Six Canadian Nationals, the game developer and publisher announced today.
The two season competition will begin this summer. Canadian teams can compete in the popular, Canadian-made Tom Clancy's Rainbow Six Siege for a $15,000 CAD prize.
The seasons will begin with a two-day open qualifier where all-Canadian teams compete for a spot in the league. The season one open qualifier will be held on June 23-24, with season two qualifiers running from September 22 to 23.
Open qualifiers will give way to online league play consisting of eight days of matches held on each weekend of July and October. Additionally, the tournament will use a round robin format, with rankings determined via a point-based system.
Each season will culminate with a live Grand Final between the two top-ranked teams. The season one finale will take place in Montréal on August 4th, 2018. Season two's Grand Final will happen on November 3rd, 2018 in Toronto.
The winning team from the second season will also become the Year 1 National Champion.
Follow Northern Arena and Ubisoft Canada on social media for updates. Additionally, details about spectator opportunities in the Grand Finals will be released closer to the finals.
Northern Arena is Canada's biggest esports organizer. It's helped make a number of esports events possible, including Street Fighter V, Call of Duty: WW2 and Injustice 2 tournaments. Northern Arena was also behind last year's Rainbow Six Canadian Circuit in Montréal.
Ubisoft has developed some of the most well-know game series available today, including the Tom Clancy series, Assassin's Creed and Far Cry. Most recently, Ubisoft Montréal developed For Honor, Assassin's Creed Origins and Far Cry 5.
Canadian players looking to participate in the Rainbow Six Canadian Nationals can register here. Players can also read the full rules here.
Ubisoft Montreal's Transference horror game to launch on September 18
Black Mirror meets Gone Home in Ubisoft Montreal and Elijah Wood's Transference [Reality Bytes]
Ubisoft unveils 'Uplay+' gaming subscription, coming to Google Stadia


text:
Home How To Reboot How to reboot Huawei Mate 40 Pro Phone
How to reboot Huawei Mate 40 Pro Phone
If you observe that your Huawei Mate 40 Pro stays frozen and consumes too much time to open any games on your mobile phone?
Perhaps because your phone is overloaded, and you have thought about restarting quickly to free up its RAM memory. The previous mobile phones come with battery removal options so that users can quickly take out the battery and insert the battery in case the mobile phone hangs. But nowadays, all the latest smartphones come with non-removal battery options. So you may think that rebooting your mobile may be difficult.
This page will help you with three easy steps to restart your Huawei Mate 40 Pro phone.
How to restart your Huawei Mate 40 Pro:
Restarting Huawei Mate 40 Pro does not delete any data from your phone. In case you want to delete all data from your phone, you can get a step by step guide here.
You should keep in mind that you must know your phone's password for Huawei Mate 40 Pro, as it will ask you for it when your device is turned on again.
Press & Hold the Power/Unlock Button on your Huawei Mate 40 Pro until you see your device's screen with a few options.
Choose the Restart or Reboot menu from the shown options on your Huawei Mate 40 Pro's screen. (If it's asking for confirmation, press accept)
Now your smartphone will turn off & on again to perform the restart. Wait for a while, and now it will ask you for your mobile device's unlock pattern or fingerprint.
Once you confirm your mobile phone's unlock pattern on your phone, it's successfully rebooted now.
Troubleshooting guide for restarting the Huawei Mate 40 Pro:
How to restart your Huawei Mate 40 Pro in case it's not responding?
Sometimes, your phone performs slow while playing a game or doing some heavy task on Huawei Mate 40 Pro. You can not continue the current task on your mobile. At that time, you will need to proceed with rebooting your Huawei Mate 40 Pro using physical buttons.
Suppose you want to do a force reboot of your Huawei Mate 40 Pro; press and hold the power button for at least 8 to 10 seconds until you see Android Logo or huawei logo appearing on your screen. Now release the button to let it start again.
Sometimes, your device is not responding even with physical buttons. You can not even force reboot your Huawei Mate 40 Pro. There are chances that your mobile has a low battery. The only solution in that scenario is to plug in your charging cable and try again.
If you still see Huawei Mate 40 Pro not responding even after following the above guidelines and you see it has entered into boot loop mode, it's possible that there is some issue with your device. You should take it to the nearest Huawei service center.
We hope this article posted on this site about how to reboot Huawei Mate 40 Pro has helped you. Please share it to help more Huawei Mate 40 Pro users.
© 2023 TheAndroidPortal is not affiliated with Google or any of the device manufacturers listed on this site. Android is a trademark of Google LLC. Use of this trademark is subject to Google Permissions.