February 26, 2017

The Complete Beginner's Guide to Helicopters

0 comments
While aircraft played an important role in both the first and second World War, you can't remember any helicopters. It's true that Germany had a reconnaissance helicopter Flettner FI 282, nicknamed the Hummingbird, which was introduced in 1942 and is considered the world's first series production helicopter. But only 24 were built and they didn't play an equally important role as the famous Spitfire or the Messerschmitt.

Why did it take so long before the world could fly around in helicopters? Isn't a helicopter as easy to design and fly as an aircraft? The answer is no! Even today it's more dangerous to be a helicopter pilot than it is to fly a normal plane: the helicopter accident rate is 30 percent higher than the accident rate for fixed-wing aircraft.

Helicopter 101
To understand why a helicopter is more complicated than an aircraft, you have to make sure you understand how an helicopter is working. Basically, a helicopter pilot has to use three controls: collective, cyclic, and pedals - and the pilot has to use all three to stabilize the helicopter.


The collective is always located to the left of the pilot and is looking like a car's handbrake. To move the helicopter up and down, the helicopter pilot is moving the collective up and down. When the collective is moved, the angle of the rotor blades are changing. A helicopter's rotor blade are working in the same way as a wing as they have the characteristic wing profile:


A wing profile is producing lift. If the angle of the wing is changing, the wing will produce more or less lift, which will move the helicopter up or down. So a helicopter is not moving up or down by changing how fast the rotor blades are rotating because that speed is always the same. As the angle is changing, the helicopter needs more or less power to rotate the blades with the same speed. In some helicopters, the pilot also has to control this power from the engine to the rotor blades, and this control is also located on the collective. If the lift from the rotor blades is higher than the mass of the helicopter, the helicopter will hover:


As the helicopter pilot is controlling the up/down movement of the helicopter with the collective, and as the power to the rotor is changing, the rotor will also produce more or less torque. To stop the helicopter from rotating because of this torque, a helicopter has a tail rotor. Some helicopters have two rotor blades, either on the same axis or after one another, to stop the torque, but most helicopters have a tail rotor. To control this torque, the pilot has two pedals, which will control the angle of the rotor blades attached to the tail rotor. In the same way as the angle of the main rotor blades produces more or less lift, if the angle of the tail rotor blades change, the helicopter will rotate around its axis.

But a helicopter can also fly in several directions, such as forward, and not just hover. If you look at a helicopter, you see something that looks like jet engines:


You might think these engines produce forward propulsion, but they are only there to rotate the helicopter blades. To fly in a certain direction, the helicopter pilot has a joystick between the legs called the cyclic. The cyclic will again control the angle of the main rotor blades, but this angle will change depending on where the rotor blades are in relation to the helicopter's body. So a helicopter pilot can control the angle of the main rotor blades by combining the collective together with the cyclic. To make this work, most helicopters have an ingenious construction called swashplate, located on the main rotor axis. This is how the swashplate is working:



From the video you can see that the main rotor is rotating forward. This will produce both a lift force and a forward force, which will make the helicopter move forward. But it will also produce a torque because the lift force is not distributed equally across the circle formed by the rotating blades, so the helicopter itself will get an angle, so it begins to lean forward:


Leaning forward is fine at certain low speeds, but at higher speeds, you want to avoid this angle. To make a helicopter fly forward without an angle, most helicopter have a horizontal stabilizer which will help the helicopter to fly straight forward at certain speeds.


Why is it difficult to fly a helicopter?
A helicopter pilot is controlling the helicopter by using the collective, cyclic, and pedals. So why is it more difficult to fly a helicopter than it is to fly an aircraft? The problem is the forces produced by the different helicopter blades. As the main rotor is rotating in different directions, the wind from the rotor blades will affect the helicopter, so to keep the helicopter in a hover position, the pilot has to make adjustments to the collective, cyclic, and pedals. It's said that a helicopter pilot has to develop a certain "feel" for the helicopter. Small deviations can be felt and seen, so corrections should be made before the helicopter actually moves. And even when flying the same model of helicopter, wind, temperature, humidity, weight, and equipment make it difficult to predict just how the helicopter will perform.

This might be confusing, so maybe a real helicopter pilot can explain it. Someone who really knows how it was to learn how to fly a helicopter is Robert Mason, who was a helicopter pilot in the Vietnam War. He has written about his experiences in the book Chickenhawk, and it includes a chapter on how he first learned to fly a helicopter:
"Next thing to do, now that you've got the cyclic down, is to let you try all the controls at once. Think you're up to that kid?"
"Yes, sir."
"Okay, you got it."
"I got it." The cyclic tugged, the collective pushed, and the pedals slapped my feet, but for a brief moment I was in complete control. I was three feet off the ground hovering in a real helicopter. A grin was forming on my sweaty face. Whoops. The illusion of control ended abruptly. As I concentrated on keeping us over one spot with the cyclic, we climbed. When I pushed the collective back down to correct, I noticed we were drifting backward, fast. I corrected by pushing forward. Now I noticed we were facing ninety degrees away from where we started. I corrected with the pedals. Each control fought me independently. I forgot about having to push the left pedal when I raised the collective. I forgot the cyclic-control lag. We whirled and grumbled in a variety of confusing directions, attitues and altitudes all at once. There were absolutely too many things to control. The IP [instructor], brave man that he was, let the ship lurch and roar and spin all over that field while I pushed the pedals, pumped the collective, and swept the cyclic around, with little effect. I felt like I had a handful of severed reins and a runaway team of horses heading for a cliff. I could not keep the machine anywhere near where I wanted it. 

February 23, 2017

How to become the MacGyver of surviving terrorist attacks

0 comments
It's true you're more likely to be fatally crushed by furniture than killed by a terrorist, but preparing for unexpected events is always a good idea. So how can you prepare for a terrorist attack? The government tells you to:
  • Be prepared by observing the emergency exits
  • React quickly and not freeze from panic
  • Make yourself a small target by hiding
  • And if everything else fails you have to fight for your life

But I don't think reading a 4-point bullet list is enough. The list says you shouldn't freeze from panic, but who's voluntarily freezing from panic? Isn't that an involuntarily decision made by your brain? Anyway, last year I read the book The Unthinkable - who survives when disaster strikes - and why by Amanda Ripley. The reason I read it was because a guy on a radio show talked about zombie attacks and he said the book would really help you prepare for the zombies. I'm not a big believer in zombie attacks, but the book doesn't mention the word zombie, and it was actually one of the best books I read during the year. 

The Unthinkable mentions several disasters, including 9/11, the sinking of the Estonia ferry, and a huge explosion in Canada. It's true you can't survive all disasters. If you were caught in one of the floors above the floors where the aircraft hit the Twin Towers, then this book will not help you. But you can maximize the probability to survive if you know what's going on in your brain when you are in the middle of a disaster.

In an emergency situation, your brain will not always help you survive. It can begin to make stupid decisions:
  • You will not accept this is happening to you. It's common to laugh, which in these situations is a form of denial: "This can't be happening to me!" Then you might get angry and then you may become quite, so mood swings are normal. But you will most likely not panic. Most people who die in disasters die from doing nothing at all and not from running around like a wet hen. In hindsight, they might think they panicked, but they only felt afraid and that is not the same thing as panic. So what you have do is to go from the denial phase to the do-something phase while remaining positive. Studies have shown that people perform better under stress if they think they can handle the situation.   
  • You will begin to gather stuff you want to take with you but you will not need. 
  • Your memory and senses will be switched on and off. This is happening at certain key points, so you may lose your vision or hearing. Remember the soldier in the reality-based Band of Brothers series who became blind during combat, but would later regain his vision when things calmed down.
  • You will forget your obligations. One person who survived 9/11 was actually in charge of evacuating the floor, but the person forgot all about it only remembered it several weeks later.
  • You will observe what other people around you are doing. This is the reason why you won't react quickly because you don't always know if you are in a terrorist attack. For example, it's easy to confuse firing guns with fireworks. If you begin to flee and it turns out to just be fireworks, then you will be laughed at and perhaps your fleeing will end up on YouTube. So you will observe what other people around you are doing, and if no-one else is doing something then neither will you. In the past, people have died because they followed the crowd, while ignoring closer exits. 
  • Your brain will freeze. The reason is you have never before been in this situation so your brain freeze while trying to figure out what to do. One person in the book who was under fire began thinking about the The Naked and the Dead, a book about soldiers in combat, because his brain was searching though its archive of experiences. This also happened when Estonia sank. One of the survivors could see how people on the top deck just sat down in chairs and where doing nothing at all instead of trying to reach the life boats, which were very close. 
  • You will come up with stupid ideas. One woman almost died from a fire because the person outside didn't want to crush the window out of fear of getting in trouble for crushing a nice window. 
  • You will follow the wrong leaders. One of the companies with most 9/11 survivors was a company with a security chief who made sure everyone knew where the emergency stairs were, and when the attacks happened everyone listened to him. But following leaders can also be the wrong decision. Firemen have seen people moving along their fire trucks towards the fire, instead of moving away from the fire because firemen are seen as leaders in a disaster.       

But your brain will also make smart decisions. Opposite from what you may first think, you will be more kind than you would have been on a normal day and you will behave orderly. During the evacuation of the towers during 9/11, people were calm and didn't run over each other on the stars on the way down. Your brain can also toughen up itself. Research shows that special forces soldiers tend to have more traumatic backgrounds, so their brains have learned something from the trauma, which makes them more capable of handling stress.   
   
So what can you do? How can you help you brain not to freeze? Remember that your brain is freezing because it doesn't have any experience from the situation. So the solution is to prepare to get experience. One police office from the book explained how his subconscious mind made better decisions than his conscious mind, so he always trusted his subconscious mind when the bullets were flying above his head. When I was in the army I recall how we had to disassemble and assemble our rifles hundreds of times until the process became unconscious. I've luckily never had to perform this process while the bullets are flying, but if you listen to the book it wasn't a waste of time.

But preparing for disasters is easier said than done. The author of the book suggests we should build amusement parks where you can prepare for disasters. Someone in Britain had the idea to install aircraft cabin simulators in airports, so passengers who are waiting for their flight could practice open emergency doors, but they idea went nowhere...

The government bullet list says you should prepare by observing where the emergency exits are. You now know why this is helpful: it will give your brain experience and it will not freeze if something is happening. This is also true when flying. Disaster experts always read the "useless" safety briefing cards because they know each aircraft is different and they know their brain will use this information if a disaster happens. They also test to exit the hotels they are visiting by using the stairs because they don't trust that someone will show them how to escape. This is important: everyone has to know what to do if a disaster happens. Remember the person who survived 9/11 and was in charge of evacuating the floor, but the person forgot all about it? So if you just have key employees in charge of the evacuation, it is not good enough.

You need to forget your experience of what has happened before. This might sound contrary to what I said above: you need experience to survive a disaster. But experience from disasters can also harm you. You may believe that many of those who died in Hurricane Katrina were poor and couldn't escape the city. But the truth is that many of those who died because they had survived previous hurricanes and thought they also would survive Katrina. So many of those who died were not poor, but old. There's also a story about a tsunami that killed people because they had locked themselves in their house because they thought the sound of the tsunami was gun shots because that's what their experience told them.  

You have to learn not only that you should do something, but also why you should do it. For example, we have all listened to flight attendants explaining what to do if the oxygen masks drop down from the ceiling of the plane. They always say you should put on your own mask before helping others. But why is it important to always put on your own mask before helping others? The answer is that in the event of a rapid decompression, your have not more than 15 seconds before you pass out. Now you understand why you have to prioritize putting on your own mask before helping others!

You have to learn how to breathe. Both FBI agents and special forces are taught how to breathe correctly to master their fear. This is how you should do it: breathe in for four counts, hold for four counts, breathe out for for counts, hold for four counts, and repeat all over again. This will help you from hyperventilating or panicking. One police office was playing a tape recording of a police siren while breathing to make it an automatic response to the siren.   

February 13, 2017

Can you design structures that last forever?

0 comments
Structures: Or Why Things Don't Fall Down by J. E. Gordon is a book about how you can design machines, buildings, boats, aircraft so they don't fall down. But the sentence "falling down" is not telling the entire story as the book will also tell you how to design structures so they don't explode. The reason I decided to read it was because Elon Musk, who is famous for building electric cars and rockets, recommended it. When he founded his rocket company SpaceX, he didn't have any experience from designing rockets, and since it's important that rockets "don't fall down," this is one of the books he read to learn how to design rockets: "It is really, really good if you want a primer on structural design."

As Elon Musk said, the book will give you a primer on structural design, so it's not a book you should read if you want to learn how to actual design so things don't fall apart. The author has included a few formulas you can use, but no examples of how to actual use the formulas. But the book is filled with interesting examples of how structures have failed and it will also give you a brief history of the area, so it's a good read in connection with a university course covering then calculation part. I would have really enjoyed reading it when I took a class on the subject a few years ago.

The area the book covers is also known as the strength of materials, and it's not the easiest of areas you can study. I would say that the area is abstract, which is why it's difficult to design structures so they don't fall down. You can't always make calculations to understand what's going on in the material until the structure has collapsed and this can take several years before it happens. This is actually one of the reasons Tesla Motor's first car, the Roadster, was delayed. The Roadster used a transmission that fell apart, not immediately, but after driving many miles. When Tesla Motors thought they had come up with a solution to the failing transmission, they had to drive it many miles to see if it really worked, so it was really time consuming to test new solutions.

I thought the most interesting parts of the book was the examples of how old structures has failed and why some didn't fail. This is an area I've had in the back of my head: if it today is difficult to design a structure so it doesn't fall down, then how difficult was it 500 years ago when they didn't have the computers engineers have today? For example, the Notre Dame Cathedral was completed in 1345 and is still in 2017 standing in Paris:

Notre Dame Cathedral by Matthew F 

The book's answer to the question what engineers back in the days knew and didn't knew is that while it might seem obvious that the medieval masons knew how to build churches, they were actually more priests and chefs than engineers. A medieval mason trusted God and a cookbook with rules of thumb when constructing buildings. The medieval castles were built with rules inherited from the Roman empire: thick walls, rounded arches, and small windows. Following rules of thumb is the way to go when you design buildings because these rules scale, so it's as easy to build a small church as it is to build a large cathedral. But trusting God didn't always work, and this is another reason why we overestimate the medieval masons. While we admire the great buildings that seem to last forever, those buildings that fell down are long forgotten, although the combination exists:

The Leaning Tower of Pisa by Saffron Blaze

So the medieval masons trusted God and rules of thumb, but what about the medieval shipbuilders? While the medieval engineers could build larger and larger churches, the ships had the same size. The reason is that you can't use the same rule of thumbs you did when you designed a small ship as you do when you build a larger ship. They probably tried to build larger ships, but they failed and are now long forgotten. But one of the failed ships that we remember is Vasa, which was a Swedish warship completed in 1628. Vasa sank on her maiden voyage because the shipbuilders deviated from the rules of thumb and their failure is now a major tourist attraction in Stockholm.

Vasa by JavierKohen

Following rules of thumb continued during the Industrial Revolution. The theory engineers use today to design structures that don't (always) fall down were developed at the same time, but rules of thumb was apparently more important than "theory." The result was: more human lives lost. In the 19th century, steamboats were racing up and down the Mississippi river. To win the race, the engineers used an "optimistic" approach to boiler design to save weight. As a result, and in one year only, 27 ships were lost as a result of boiler explosion. The author argues that the idea to ignore theory is to some extend true also today, and that "nine out of ten accidents are caused, not by more or less abstruse technical effects, but by old-fashioned human sin - often verging on plain wickedness."

Historically, we have seen that structures have fallen down because the engineers didn't use the theories we have today. So can we today design a structure that will last forever? The answer is no! The problem is that you can't take everything into account when designing a structure. Some structures are likely to be broken only by an unusual combination of events. A bridge may collapse if on a windy day, there's an unusually amount of traffic on the bridge. It may take years before one of these events happen. A structure that might seem it will last forever, is actually dangerous simply because it has never been fully tried. According to the author:
"It it is impossible, in practice, to plan for a safe life of exactly so many hours or years. We can only consider the problem in statistical terms and in the light of accumulated data and experience. We then build in whatever margin of safety seems reasonable. All the time we are working on a basis of probabilities and estimates. If we make the structure too weak we may save weight and money, but the chance of the thing breaking too soon will become unacceptable high. Contrariwise, if we make a structure so strong that, in human terms, it is likely to last forever - which is what the public would like - then it will probably be too heavy and expensive. Because we are necessarily working on an statistical basis, when we design a practical structure for a realistic life we have to accept that there is always some finite risk, however small, of premature failure."

So remember the next time you are sitting in a plane high above the sea, driving your car on the highway, or riding in an elevator, the engineer has most likely done his or her best to design the structure, but there is always some finite risk, however small, of premature failure.

February 12, 2017

3 books you must read if you want to learn more about helicopters

0 comments
I've spent some time reading books about helicopters to research a project I'm working on. This is a list of the books I thought were the best.

Chickenhawk. This book is considered a must-read for all helicopter pilots. It's written by Robert Mason, who was a helicopter pilot in the Vietnam war, which was the first conflict that really used helicopters. Yes, helicopters were used in both the Second World War and in the Korean War, but in the Vietnam war, US realized that they could transport battalions of soldiers across the battlefield to surprise the enemy. The book includes a lot of information on how to operate a helicopter in a war zone, but it's not a technical manual, so if you are not interested in helicopter technology you will also enjoy reading it.

Deadliest Sea - The Untold Story Behind the Greatest Rescue in Coast Guard History. This books tells the story of a sinking fishing ship in the middle of an Alaskan cold sea and how the US Coast Guard did its best to rescue the fishers. While the book Chickenhawk told the story of how helicopters operate in a war zone, this book will tell the story of how helicopters operate from a coast guard perspective: what equipment does a coast guard helicopter carry, how does the rescue swimmer operate, how can a helicopter refuel at sea, and much more?

Helicopter flying handbook. Is a free book written by the US Department of Transportation and is a handbook written mainly for students who want to become helicopter pilots. While Chickenhawk and Deadliest Sea will give you some technical details, this book will tell you all about aerodynamics, flight controls, systems, performance, flight maneuvers, emergencies, how to operate a helicopter in different weather conditions, and so on.

If you still want to read more about helicopters, you can also read We Were Soldiers Once...and Young: Ia Drang - The Battle That Changed the War in Vietnam, which tells the story of a battle in Vietnam famous from the movie with the same name. Robert Mason, who wrote Chickenhawk, participated in the same battle, so some of it is repetition if you read that book. Neither is the book focused on helicopters, but there are some helicopter facts in it.

Another book you can read is Black Hawk Down: A Story of Modern War, which is another book famous from a movie. It will tell you the story of what happens when a helicopter is shot down in the middle of a conflict. While many helicopters were shot down in the book Chickenhawk, the Black Hawk Down battle took place in Somalia in the 1990s.

February 5, 2017

Why Drawing Cats Will Make You Question Everything

0 comments
A few weeks ago I read the book The art of game design. Game design is more than how a game should look like, but the book's chapter on aesthetics said that "the key to creating great artwork is in your ability to see." Well, how hard can it be to see? The answer is that it's actually difficult to really see. One good example of where your brain is fooling you is Shepard's famous table image:


Your brain is telling you that the tables don't have the same shape. But if you measure them, you will see that they have the same shape even though one of them is rotated 90 degrees.

If you look at an object, like your phone, you see a phone. But to really see the phone you have to learn to see the its shapes, colors, proportions, shadows, reflections, textures, and its relationship to the environment. Why is it so difficult to actually see the phone? The answer is that our brain is programmed to take shortcuts to avoid being overloaded. If you each time you saw an object, you would notice its shapes, colors, proportions, and all the other things, then your poor brain would become overloaded. So it's easier for the brain to just add labels to the objects you are seeing and then move on to the next object.

The brain's habit to add labels to objects you are seeing is a problem if you want to draw images. This is the topic of the book Drawing on the rights side of the brain. The idea behind the book's title is that your brain consists of two sides: left and right. It's the left side that add labels to objects and it's the right side that can see all the details, such as shapes, colors, proportions, shadows, etc. So you need to use the right side of your brain if you want to draw an image of whatever you are seeing. Switching from the left to the right side is not an easy task as there's no switch you can use to just deactivate the left brain. What you need to do to make the switch is to fool the left side.

If you want to draw this cat, your left brain will bring up its memories of what a cat looks like and you will draw these memories instead of what you are actually seeing.


One of the tricks you can use to be able to draw the cat with the right side of the brain is to turn it upside down:


Why should you turn the cat upside down? The answer is that it will be much more difficult for your left brain to attach memories of cats to the cat, making your right brain take over so you can actually see the cat's shapes and colors. So when you draw the cat you need to avoid words like eyes, because it will bring up memories of eyes that you will draw instead of the green shapes you should draw. This is actually a technique forgers use to copy signatures: they have learned that it's easier to copy the signature if they turn the original signature upside down.

You also need to avoid cat characteristics like that it's soft because it will not help you to draw the cat and the visual information you see may not be the same as what you remember. So you should draw what you see and not what you know. You should draw what you see without questioning why whatever you are drawing is looking like what you see. But when you are finished with you drawing, you should use your left brain to judge the result. Is what you drew looking like a cat?