Ready For Takeoff - Turn Your Aviation Passion Into A Career

The Ready For Takeoff podcast will help you transform your aviation passion into an aviation career. Every week we bring you instruction and interviews with top aviators in their field who reveal their flight path to an exciting career in the skies.
RSS Feed
Ready For Takeoff - Turn Your Aviation Passion Into A Career






All Episodes
Now displaying: July, 2019
Jul 29, 2019

Lisa Marranzino was a therapist in Denver when she realized something was missing in her life. It might have been mid-life crisis. Whatever it was, she decided to explore the world and find what made people happy, both for herself and her patients.

That started a five-year odyssey in which she traveled to over 40 countries, spoke to scores of strangers in intimate conversations, and tried to find a common theme to what brings people happiness in all cultures.

She documented her conversations in her book, Happiness On The Blue Dot.


In this podcast, Lisa shares her experiences as a world traveler, and offers suggestions for interacting with strangers from around the world.

Jul 25, 2019

Operations Specifications (OPSPECS) are the specifications that the FAA assigns to airlines for such things as authorized routes, types of equipment, VFR and IFR operations, and alternate requirements.

OPS Spec C055 discusses the requirement for alternate airports.


One area that  is sometimes difficult for new Part 121 pilots to comprehend is the exclusivity of takeoff minimums from landing minimums. Try to picture each as completely separate from the other. Just because a particular airport is below landing minimums doesn’t (necessarily) mean you can’t depart. Instead, first attempt to consider the takeoff minimums by themselves. If the weather, airport equipment, aircraft capabilities, and FARs/Ops Specs will permit such a takeoff, nothing prevents you from departing. Only after you’ve examined the feasibility of a takeoff should you look at the landing minimums.

What if the airport is below landing mins? Then you’re required to have a takeoff alternate as outlined in 14 CFR 121.617. The exact weather mins for the takeoff alternate will be specified in the Ops Specs. In nearly all cases, your company Ops Specs will state the engine-inop, still-air distance in nautical miles (NMs); thus giving you an idea of the acceptable radius for an appropriate alternate.


121.617b says the takeoff alternate has to meet the alternate minimums in the Ops Specs. Paragraph C55 is the create your own minimums paragraph based on the available approaches. Pretty much for one approach add 400 and 1 to the mins and for 2 approaches, 200 and a half to the higher minimuns. The approaches have to be to different runways unless you're ETOPS, then they have to be to separate runways. If you're good for CAT III and the airport has dual CAT III runways you can get your alternate minimums down to 200/1800RVR. If it was down to that, I'd see about having a second alternate added to the release.

Jul 18, 2019

United Airlines Flight 232 was a regularly scheduled United Airlines flight from Denver to Chicago, continuing to Philadelphia. On July 19, 1989, the DC-10 (registered as N1819U) serving the flight crash-landed at Sioux City, Iowa, after suffering a catastrophic failure of its tail-mounted engine, which led to the loss of many flight controls. At the time, the aircraft was en route from Stapleton International Airport to O'Hare International Airport. Of the 296 passengers and crew on board, 111 died in the accident and 185 survived, making the crash the fifth-deadliest involving the DC-10, behind Turkish Airlines Flight 981, American Airlines Flight 191, Air New Zealand Flight 901, and UTA Flight 772. Despite the deaths, the accident is considered a prime example of successful crew resource management because of the large number of survivors and the manner in which the flight crew handled the emergency and landed the airplane without conventional control.

The airplane, a McDonnell Douglas DC-10-10 (registration N1819U), was delivered in 1973 and had been owned by United Airlines since then. Before departure on the flight from Denver on July 19, 1989, the airplane had been operated for a total of 43,401 hours and 16,997 cycles (a takeoff and subsequent landing is considered an aircraft cycle). The airplane was powered by CF6-6D high-bypass-ratio turbofan engines produced by General Electric Aircraft Engines (GEAE).

Captain Alfred Clair Haynes, 57, was hired by United Airlines in 1956. He had 29,967 hours of total flight time with United Airlines, of which 7,190 were in the DC-10.

First Officer William Roy Records, 48, was hired by National Airlines in 1969. He subsequently worked for Pan American World Airways. He estimated that he had approximately 20,000 hours of total flight time. He had 665 hours as a DC-10 first officer.

Second Officer Dudley Joseph Dvorak, 51, was hired by United Airlines in 1986. He estimated that he had approximately 15,000 hours of total flying time. He had 1,900 hours as a second officer in the Boeing 727 and 33 hours as a second officer in the DC-10.

Training Check Airman Captain Dennis Edward Fitch, 46, was hired by United Airlines in 1968. He estimated that, prior to working for United, he had accrued at least 1,400 hours of flight time with the Air National Guard, with a total flight time of approximately 23,000 hours. His total DC-10 time with United was 3,079 hours, of which 2,000 hours were accrued as a second officer, 1,000 hours as a first officer, and 79 hours as a captain. He had learned of the crash of Japan Airlines Flight 123, caused by a catastrophic loss of hydraulic control, and had wondered if it was possible to control an aircraft using throttles only. He had practiced under similar conditions on a simulator.

Flight 232 took off at 14:09 CDT from Stapleton International Airport, Denver, Colorado, bound for O'Hare International Airport in Chicago with continuing service to Philadelphia International Airport.

At 15:16, while the plane was in a shallow right turn at 37,000 feet, the fan disk of its tail-mounted General Electric CF6-6 engine explosively disintegrated. Debris penetrated the tail in numerous places, including the horizontal stabilizer, puncturing the lines of all three hydraulic systems.

The pilots felt a jolt, and the autopilot disengaged. As Records took hold of his control column, Haynes focused on the tail engine, whose instruments indicated it was malfunctioning; he found its throttle and fuel supply controls jammed. At Dvorak's suggestion, a valve cutting fuel to the tail engine was shut off. This part of the emergency took 14 seconds.

Meanwhile, Records found that the plane did not respond to his control column. Even with the control column turned all the way to the left, commanding maximum left aileron, and pulled all the way back, commanding maximum up elevator – inputs that would never be used together in normal flight – the aircraft was banking to the right with the nose dropping. Haynes attempted to level the aircraft with his own control column, then both Haynes and Records tried using their control columns together, but the aircraft still did not respond. Afraid the aircraft would roll into a completely inverted position (an unrecoverable situation), the crew reduced the left wing-mounted engine to idle and applied maximum power to the right engine. This caused the airplane to slowly level out.

The various gauges for all three hydraulic systems were registering zero. The three hydraulic systems were separate, so that failure of any one of them would leave the crew with full control, but lines for all three systems shared the same narrow passage through the tail where the engine debris had penetrated, and thus control surfaces were inoperative. The crew contacted United maintenance personnel via radio, but were told that, as a total loss of hydraulics on the DC-10 was considered "virtually impossible", there were no established procedures for such an event.

The plane was tending to pull right, and slowly oscillated vertically in a phugoid cycle – characteristic of planes in which control surface command is lost. With each iteration of the cycle, the aircraft lost approximately 1,500 feet (460 m) of altitude. On learning that Fitch, an experienced United Airlines captain and DC-10 flight instructor, was among the passengers, the crew called him into the cockpit for assistance.

Haynes asked Fitch to observe the ailerons through the passenger cabin windows to see if control inputs were having any effect. Fitch reported back that the ailerons were not moving at all. Nonetheless, the crew continued to manipulate their control columns for the remainder of the flight, hoping for at least some effect. Haynes then asked Fitch to take over control of the throttles so that Haynes could concentrate on his control column. With one throttle in each hand, Fitch was able to mitigate the phugoid cycle and make rough steering adjustments.

As the crew began to prepare for arrival at Sioux City, they questioned whether they should deploy the landing gear or belly-land the aircraft with the gear retracted. They decided that having the landing gear down would provide some shock absorption on impact.The complete hydraulic failure left the landing gear lowering mechanism inoperative. Two options were available to the flight crew. The DC-10 is designed so that if hydraulic pressure to the landing gear is lost, the gear will fall down slightly and rest on the landing gear doors. Placing the regular landing gear handle in the down position will unlock the doors mechanically, and the doors and landing gear will then fall down into place and lock due to gravity. An alternative system is also available using a lever in the cockpit floor to cause the landing gear to fall into position. This lever has the added benefit of unlocking the outboard ailerons, which are not used in high-speed flight and are locked in a neutral position. The crew hoped that there might be some trapped hydraulic fluid in the outboard ailerons and that they might regain some use of flight controls by unlocking them. They elected to extend the gear with the alternative system. Although the gear deployed successfully, there was no change in the controllability of the aircraft.

Landing was originally planned on the 9,000-foot (2,700 m) Runway 31. Difficulties in controlling the aircraft made lining up almost impossible. While dumping some of the excess fuel, the plane executed a series of mostly right-hand turns (it was easier to turn the plane in this direction) with the intention of lining up with Runway 31. When they came out they were instead lined up with the shorter (6,888 ft) and closed Runway 22, and had little capacity to maneuver. Fire trucks had been placed on Runway 22, anticipating a landing on nearby Runway 31, so all the vehicles were quickly moved out of the way before the plane touched down. Runway 22 had been permanently closed a year earlier.

ATC also advised that I-29 ran North and South just East of the airport which they could land on if they did not think they could make the runway. The pilot opted to try for the runway instead.

The plane landed askew, causing the explosion and fire seen in this still from local news station video.

Fitch continued to control the aircraft's descent by adjusting engine thrust. With the loss of all hydraulics, the flaps could not be extended and since flaps control both the minimum required forward speed and sink rate, the crew were unable to control both airspeed and sink rate. On final descent, the aircraft was going 220 knots and sinking at 1,850 feet per minute (approximately 407 km/h forward and 34 km/h downward speed), while a safe landing would require 140 knots and 300 feet per minute (approximately 260 km/h and 5 km/h respectively). Fitch needed a seat for landing; Dvorak offered up his own, as it could be moved to a position behind the throttles. Dvorak sat in the cockpit's jump seat for landing. Fitch noticed the high sink rate and that the plane started to yaw right again, and pushed the throttles to full power in an attempt to mitigate the high sink rate and level the plane.

There was not enough time for the flight crew to react. The tip of the right wing hit the runway first, spilling fuel, which ignited immediately. The tail section broke off from the force of the impact, and the rest of the aircraft bounced several times, shedding the landing gear and engine nacelles and breaking the fuselage into several main pieces. On the final impact, the right wing was shorn off and the main part of the aircraft skidded sideways, rolled over onto its back, and slid to a stop upside-down in a corn field to the right of Runway 22. Witnesses reported that the aircraft "cartwheeled" end-over-end, but the investigation did not confirm this. The reports were due to misinterpretation of the video of the crash that showed the flaming right wing tumbling end-over-end and the intact left wing, still attached to the fuselage, rolling up and over as the fuselage flipped over.

Jul 15, 2019

Tiffany Behr comes from a long line of military aviators, and was introduced to flying at an early age when she want flying with her father.

She attended Kansas University and then entered Air Force Undergraduate Pilot training at Laughlin Air Force Base in Del Rio, Texas. Her initial flying assignment was to C-130s, where she deployed on combat missions in Afghanistan.

Her next flying assignment was in the RC-135, OC-135 and WC-135. Following that, she was selected to fly Presidential Support missions in the 89th Military Airlift Squadron.

Next, she was selected to be a speech-writer for high-ranking officers in the Middle East.

After Tiffany left active duty she was hired by a major legacy airline, where she currently flies B737 NG aircraft.

Jul 11, 2019

A tail strike can occur during either takeoff or landing. Many air carrier aircraft have tail skids to absorb energy from a tailstrike. On some aircraft, the tail skid is a small bump on the aft underside of the airplane, while on others it is a retractable skid that extends and retracts with the landing gear.

Most tail strikes are the result of pilot error, and in general, landing tail strikes cause more damage than takeoff tail strikes.

In 1978, Japan Airlines flight 115 experienced a tail strike during landing that caused damage to the aft pressure bulkhead. The aircraft was repaired (although the repair was faulty) and returned to service. Seven years later, the aircraft, operating as Japan Airlines Flight 123, crashed as a result of the failure of the improperly-repaired pressure bulkhead.

This Boeing document is an excellent analysis of tailstrikes. A portion of the document is reproduced below:

Takeoff Risk Factors
Any one of these four takeoff risk factors may precede a tail strike:

  • Mistrimmed stabilizer.
  • Rotation at improper speed.
  • Excessive rotation rate.
  • Improper use of the flight director.

A mistrimmed stabilizer occurring during takeoff is not common but is an experience shared at least once by almost every flight crew. It usually results from using erroneous data, the wrong weights, or an incorrect center of gravity (CG). Sometimes the information presented to the flight crew is accurate, but it is entered incorrectly either to the flight management system (FMS) or to the stabilizer itself. In any case, the stabilizer is set in the wrong position. The flight crew can become aware of the error and correct the condition by challenging the reasonableness of the load sheet numbers. A flight crew that has made a few takeoffs in a given weight range knows roughly where the CG usually resides and approximately where the trim should be set. Boeing suggests testing the load sheet numbers against past experience to be sure that the numbers are reasonable.

A stabilizer mistrimmed nosedown can present several problems, but tail strike usually is not one of them. However, a stabilizer mistrimmed noseup can place the tail at risk. This is because the yoke requires less pull force to initiate airplane rotation during takeoff, and the pilot flying (PF) may be surprised at how rapidly the nose comes up. With the Boeing-recommended rotation rate between 2.0 and 3.0 degrees per second (dps), depending on the model, and a normal liftoff attitude, liftoff usually occurs about four seconds after the nose starts to rise. (These figures are fairly standard for all commercial airplanes; exact values are contained in the operations and/or flight-crew training manuals for each model.) However, with the stabilizer mistrimmed noseup, the airplane can rotate 5 dps or more. With the nose rising very rapidly, the airplane does not have enough time to change its flight path before exceeding the critical attitude. Tail strike can then occur within two or three seconds of the time rotation is initiated.

If the stabilizer is substantially mistrimmed noseup, the airplane may even try to fly from the runway without control input from the PF. Before reaching Vr, and possibly as early as approaching V1, the nose begins to ride light on the runway. Two or three light bounces may occur before the nose suddenly goes into the air. A faster-than-normal rotation usually follows and, when the airplane passes through the normal liftoff attitude, it lacks sufficient speed to fly and so stays on the runway. Unless the PF actively intercedes, the nose keeps coming up until the tail strike occurs, either immediately before or after liftoff.

This situation can result in a tail strike and is usually caused by one of two reasons: rotation is begun early because of some unusual situation, or the airplane is rotated at a V
r that has been computed incorrectly and is too low for the weight and flap setting.

An example of an unusual situation discovered during the DPD examination was a twinjet going out at close to the maximum allowable weight. In order to make second segment climb, the crew had selected a lower-than-usual flap setting. The lower flap setting generates V speeds somewhat higher than normal and reduces tail clearance during rotation. In addition, the example situation was a runway length-limited takeoff. The PF began to lighten the nose as the airplane approached V1, which is an understandable impulse when ground speed is high and the end of the runway is near. The nose came off the runway at V1 and, with a rather aggressive rotation, the tail brushed the runway just after the airplane became airborne.

An error in Vr speed recently resulted in a trijet tail strike. The load sheet numbers were accurate, but somehow the takeoff weight was entered into the FMS 100,000 lb lower than it should have been. The resulting Vr was 12 knots indicated air speed (kias) slow. When the airplane passed through a nominal 8-deg liftoff attitude, a lack of sufficient speed prevented takeoff. Rotation was allowed to continue, with takeoff and tail strike occurring at about 11 deg. Verification that the load sheet numbers were correctly entered may have prevented this incident.

Flight crews operating an airplane model that is new to them, especially when transitioning from unpowered flight controls to ones with hydraulic assistance, are most vulnerable to using excessive rotation rate. The amount of control input required to achieve the proper rotation rate varies from one model to another. When transitioning to a new model, flight crews may not consciously realize that it will not respond to pitch input in exactly the same way.

As simulators reproduce airplane responses with remarkable fidelity, simulator training can help flight crews learn the appropriate response. A concentrated period of takeoff practice allows students to develop a sure sense of how the new airplane feels and responds to pitch inputs. On some models, this is particularly important when the CG is loaded toward its aft limits, because an airplane in this condition is more sensitive in pitch, especially during takeoff. A normal amount of noseup elevator in an aft CG condition is likely to cause the nose to lift off the runway more rapidly and put the tail at risk.

As shown in figure 1, the flight director (FD) is designed to provide accurate pitch guidance only after the airplane is airborne, nominally passing through 35 ft (10.7 m). With the proper rotation rate, the airplane reaches 35 ft with the desired pitch attitude of about 15 deg and a speed of V
2 + 10 (V2 + 15 on some models). However, an aggressive rotation into the pitch bar at takeoff is not appropriate and may rotate the tail onto the ground.

Landing Risk Factors
Any one of these four landing risk factors may precede a tail strike:

  • Unstabilized approach.
  • Holding off in the flare.
  • Mishandling of crosswinds.
  • Over-rotation during go-around.

A tail strike on landing tends to cause more serious damage than the same event during takeoff and is more expensive and time consuming to repair. In the worst case, the tail can strike the runway before the landing gear touches down, thus absorbing large amounts of energy for which it is not designed. The aft pressure bulkhead is often damaged as a result.

An unstabilized approach appears in one form or another in virtually every landing tail strike event. When an airplane turns on to final approach with excessive airspeed, excessive altitude, or both, the situation may not be under the control of the flight crew. The most common cause of this scenario is the sequencing of traffic in the terminal area as determined by air traffic control.

Digital flight recorder data show that flight crews who continue through an unstabilized condition below 500 ft will likely never get the approach stabilized. When the airplane arrives in the flare, it invariably has either excessive or insufficient airspeed, and quite often is also long on the runway. The result is a tendency toward large power and pitch corrections in the flare, often culminating in a vigorous noseup pull at touchdown and tail strike shortly thereafter. If the nose is coming up rapidly when touchdown occurs and the ground spoilers deploy, the spoilers themselves add an additional noseup pitching force. Also, if the airplane is slow, pulling up the nose in the flare does not materially reduce the sink rate and in fact may increase it. A firm touchdown on the main gear is often preferable to a soft touchdown with the nose rising rapidly.

The second most common cause of a landing tail strike is a long flare to a drop-in touchdown, a condition often precipitated by a desire to achieve an extremely smooth landing. A very soft touchdown is not essential, nor even desired, particularly if the runway is wet.

Trimming the stabilizer in the flare may contribute to a tail strike. The PF may easily lose the feel of the elevator while the trim is running; too much trim can raise the nose, even when this reaction is not desired. The pitchup can cause a balloon, followed either by dropping in or pitching over and landing flat. Flight crews should trim the airplane in the approach, but not in the flare itself, and avoid "squeakers," as they waste runway and may predispose the airplane to a tail strike.

A crosswind approach and landing contains many elements that may increase the risk of tail strike, particularly in the presence of gusty conditions. Wind directions near 90 deg to the runway heading are often strong at pattern altitude, and with little headwind component, the airplane flies the final approach with a rapid rate of closure on the runway. To stay on the glidepath at that high groundspeed, descent rates of 700 to 900 ft (214 to 274 m) per minute may be required. Engine power is likely to be well back, approaching idle in some cases, to avoid accelerating the airplane. If the airplane is placed in a forward slip attitude to compensate for the wind effects, this cross-control maneuver reduces lift, increases drag, and may increase the rate of descent. If the airplane then descends into a turbulent surface layer, particularly if the wind is shifting toward the tail, the stage is set for tail strike.

The combined effects of high closure rate, shifting winds with the potential for a quartering tail wind, the sudden drop in wind velocity commonly found below 100 ft (31 m), and turbulence can make the timing of the flare very difficult. The PF can best handle the situation by exercising active control of the sink rate and making sure that additional thrust is available if needed. Flight crews should clearly understand the criteria for initiating a go-around and plan to use this time-honored avoidance maneuver when needed.

Go-arounds initiated very late in the approach, such as during flare or after a bounce, are a common cause of tail strike. When the go-around mode is initiated, the FD immediately commands a go-around pitch attitude. If the PF abruptly rotates into the command bars, tail strike can occur before a change to the flight path is possible. Both pitch attitude and thrust are required for go-around, so if the engines are just spooling up when the PF vigorously pulls the nose up, the thrust may not yet be adequate to support the effort. The nose comes up, and the tail goes down. A contributing factor may be a strong desire of the flight crew to avoid wheel contact after initiating a late go-around, when the airplane is still over the runway. In general, the concern is not warranted because a brief contact with the tires during a late go-around does not produce adverse consequences. Airframe manufacturers have executed literally hundreds of late go-arounds during autoland certification programs with dozens of runway contacts, and no problem has ever resulted. The airplane simply flies away from the touchdown.

Jul 8, 2019

Lt. Commander Dominique (Nikki) Selby was a Critical Care, Trauma and Enroute Care Nurse for the US Navy. She deployed to various regions to include Haiti, Afghanistan and various countries in the Middle East as an in-flight critical care nurse, ICU, trauma and Fleet Surgical Team nurse operating in austere conditions (Role II and Role III facilities). She is currently a Course Coordinator for the Advanced Trauma Course for Nurses and a Training Site Facilitator for ACLS, and teaches classes to all military and civilian providers for the Naval Medical Center San Diego.
Her current certifications are BLS-I, ACLS-I/TSF, ATCN Instructor and Course Coordinator, PALS-P, TCCC-P and TNCC-P. With 22 years in the Navy and 12 years of experience as an RN, she is certified in Emergency Nursing (CEN) and currently licensed in the states of Nevada and California. 


Jul 4, 2019

There are four types of Hypoxia:
Hypoxia means “reduced oxygen” or “not enough oxygen.”
Although any tissue will die if deprived of oxygen long
enough, the greatest concern regarding hypoxia during
flight is lack of oxygen to the brain, since it is particularly
vulnerable to oxygen deprivation. Any reduction in mental
function while flying can result in life-threatening errors.
Hypoxia can be caused by several factors, including an
insufficient supply of oxygen, inadequate transportation of
oxygen, or the inability of the body tissues to use oxygen.
The forms of hypoxia are based on their causes:
• Hypoxic hypoxia
• Hypemic hypoxia
• Stagnant hypoxia
• Histotoxic hypoxia
Hypoxic Hypoxia
Hypoxic hypoxia is a result of insufficient oxygen available
to the body as a whole. A blocked airway and drowning
are obvious examples of how the lungs can be deprived of
oxygen, but the reduction in partial pressure of oxygen at high
altitude is an appropriate example for pilots. Although the
percentage of oxygen in the atmosphere is constant, its partial
pressure decreases proportionately as atmospheric pressure
decreases. As an aircraft ascends during flight, the percentage
of each gas in the atmosphere remains the same, but there are
fewer molecules available at the pressure required for them
to pass between the membranes in the respiratory system.
This decrease in number of oxygen molecules at sufficient
pressure can lead to hypoxic hypoxia.

Hypemic Hypoxia
Hypemic hypoxia occurs when the blood is not able to take
up and transport a sufficient amount of oxygen to the cells
in the body. Hypemic means “not enough blood.” This type
of hypoxia is a result of oxygen deficiency in the blood,
rather than a lack of inhaled oxygen, and can be caused by
a variety of factors. It may be due to reduced blood volume
(from severe bleeding), or it may result from certain blood
diseases, such as anemia. More often, hypemic hypoxia
occurs because hemoglobin, the actual blood molecule that
transports oxygen, is chemically unable to bind oxygen
molecules. The most common form of hypemic hypoxia is
CO poisoning. This is explained in greater detail later in this
chapter. Hypemic hypoxia can also be caused by the loss
of blood due to blood donation. Blood volume can require
several weeks to return to normal following a donation.
Although the effects of the blood loss are slight at ground
level, there are risks when flying during this time.

Stagnant Hypoxia
Stagnant means “not flowing,” and stagnant hypoxia or
ischemia results when the oxygen-rich blood in the lungs
is not moving, for one reason or another, to the tissues that need it. An arm or leg “going to sleep” because the blood
flow has accidentally been shut off is one form of stagnant
hypoxia. This kind of hypoxia can also result from shock,
the heart failing to pump blood effectively, or a constricted
artery. During flight, stagnant hypoxia can occur with
excessive acceleration of gravity (Gs). Cold temperatures
can also reduce circulation and decrease the blood supplied
to extremities.

Histotoxic Hypoxia
The inability of the cells to effectively use oxygen is defined
as histotoxic hypoxia. “Histo” refers to tissues or cells, and
“toxic” means poisonous. In this case, enough oxygen is being
transported to the cells that need it, but they are unable to make
use of it. This impairment of cellular respiration can be caused
by alcohol and other drugs, such as narcotics and poisons.
Research has shown that drinking one ounce of alcohol can
equate to an additional 2,000 feet of physiological altitude.

Symptoms of Hypoxia
High-altitude flying can place a pilot in danger of becoming
hypoxic. Oxygen starvation causes the brain and other vital
organs to become impaired. The first symptoms of hypoxia
can include euphoria and a carefree feeling. With increased
oxygen starvation, the extremities become less responsive and
flying becomes less coordinated. The symptoms of hypoxia
vary with the individual, but common symptoms include:
• Cyanosis (blue fingernails and lips)
• Headache
• Decreased response to stimuli and increased reaction
• Impaired judgment
• Euphoria
• Visual impairment
• Drowsiness
• Lightheaded or dizzy sensation
• Tingling in fingers and toes
• Numbness
As hypoxia worsens, the field of vision begins to narrow and
instrument interpretation can become difficult. Even with all
these symptoms, the effects of hypoxia can cause a pilot to
have a false sense of security and be deceived into believing
everything is normal.

Treatment of Hypoxia
Treatment for hypoxia includes flying at lower altitudes and/
or using supplemental oxygen. All pilots are susceptible
to the effects of oxygen starvation, regardless of physical
endurance or acclimatization. When flying at high altitudes,
it is paramount that oxygen be used to avoid the effects of
hypoxia. The term “time of useful consciousness” describes
the maximum time the pilot has to make rational, life-saving
decisions and carry them out at a given altitude without
supplemental oxygen. As altitude increases above 10,000
feet, the symptoms of hypoxia increase in severity, and the
time of useful consciousness rapidly decreases. [Figure 17-1]
Since symptoms of hypoxia can be different for each
individual, the ability to recognize hypoxia can be greatly
improved by experiencing and witnessing the effects of it
during an altitude chamber “flight.” The Federal Aviation
Administration (FAA) provides this opportunity through
aviation physiology training, which is conducted at the FAA
CAMI in Oklahoma City, Oklahoma, and at many military
facilities across the United States. For information about the
FAA’s one-day physiological training course with altitude
chamber and vertigo demonstrations, visit the FAA website

Jul 1, 2019

Morri Leland is the Chief Executive Officer of Patriot Mobile.  He assumed the role of CEO in 2017.  

As CEO, Morri is focused on helping conservative consumers and businesses throughout the United States protect and defend their rights and liberty and ensure these freedoms remain for generations to come.

For more than 30 years, Morri has led global teams to excel and exceed growth expectations.  Prior to joining Patriot Mobile, he served as Deputy Vice President for International Business at Lockheed Martin Missiles and Fire Control, headquartered in Dallas, Texas. Morri was responsible for global sales and marketing for the aerospace, defense and energy sectors that included numerous competitive global pursuits that resulted in significant international growth.  Prior to that Morri served as the Program Director for F-35 / CVF Integration with Lockheed Martin Aeronautics.  As the senior representative for the Joint Strike Fighter program in the United Kingdom (UK), he was responsible for the successful development and management of the program to integrate the F-35 air system into the design and construction of the UK Future Aircraft Carrier (CVF).  

From 1983 to 2003, Morri served on active duty in the United States Navy.  After tours at NASA and as a flight instructor, he accumulated over 5,000 hours in various types of military aircraft.  With significant time in various models of the F/A-18 Hornet, he served multiple combat tours in Afghanistan, Iraq and the Balkans and commanded a squadron that garnered honors as the top Strike-Fighter squadron in the U.S. Navy.  He also served on a NATO exchange flying tour and in the Pentagon on the staff of the Chairman of the Joint Chiefs of Staff.

A native of South Carolina, Morri holds a BS in Systems Engineering from the U.S. Naval Academy and a Master of Science in International Security Affairs from the U.S. Naval War College.

Morri and his wife Sheila reside in Southlake, TX with their two sons.