http://www.goldstandardaviation.com/

Gold Standard Aviation, 14933 NW 41st Avenue Suite 51-8, Opa-locka, FL (2026)

08/26/2026

Was deploying the Cirrus Airframe Parachute System (CAPS) good ADM during an in-flight engine fire?

This week, the pilot of a Cirrus SR22 detected smoke in the cockpit and immediately initiated an emergency descent to approximately 2,000 feet AGL. Recognizing that there was no suitable runway within reach, the pilot deployed CAPS, bringing the Cirrus down safely in a residential area.

The pilot walked away unharmed. The Cirrus was subsequently destroyed by fire.

The Cirrus POH procedure for an Engine Fire in Flight calls for securing the engine and landing as soon as possible. The decision to glide to a safe landing or deploy CAPS depends largely on whether a suitable runway is within gliding distance.

If no suitable runway or landing area is available, CAPS becomes an important option. Cirrus guidance calls for considering CAPS at approximately 2,000 feet AGL—or, if necessary, at much lower altitude (as low as 600 feet AGL). The actual deployment altitude is ultimately the pilot’s decision based on the circumstances and severity of the emergency.

With an active and potentially worsening fire, time becomes critical. Fire and/or smoke threatening to breach the cabin could justify deploying CAPS sooner rather than continuing a glide in search of a landing site.

Takeaway: This appears to be an excellent example of sound aeronautical decision-making. The pilot recognized the emergency, descended promptly, evaluated the available options, and used CAPS when a conventional landing was no longer the best choice.

More importantly, the pilot survived without a scratch. In-flight fires and dead-stick landings can quickly become catastrophic, and incidents like this can easily end in tragedy.

Know the procedures. Know your options. Make the decision while you still have options.

Fly safe, friends ✈️

08/22/2026

One of the most common private pilot mistakes ruined this applicant’s checkride

A private pilot applicant was on his checkride when the DPE instructed him to divert to a nearby airport.

Following good diversion procedures, he turned his Cessna toward the general direction of the airport, entered the airport identifier into his GPS and selected Direct-To, then tuned the appropriate communication frequencies.

As he approached the airport, ATC instructed him:

“Report midfield right downwind, Runway 27R.”

This is where things went wrong.

The pilot should have turned east and flown parallel to the airport, keeping the airport on his right to establish himself for right traffic.

Instead, he flew south, intending to position his airplane on the right side of the airport. In his mind, “right traffic” meant he needed to be physically to the right of the airport.

The examiner recognized the mistake and instructed him to turn left and fly east. At that moment, the tower controller transmitted:

“Cessna, what are you doing? You’re about to cross the departure corridor!”

After returning to base, the applicant admitted that he hadn’t used the west runways in months and had forgotten how to properly enter the pattern.

A Notice of Disapproval was issued.

Takeaway: Confusing a left traffic pattern with a right traffic pattern is an easy—and potentially serious—mistake when approaching an airport.

A helpful way to think about pattern-entry instructions is to position the airplane with respect to the airport first.

If instructed to “report right downwind,” maneuver so the airport is on your right. Once established, locate the assigned runway and adjust your flight path as necessary.

The same concept can help with base entries. If instructed to “report right base,” initially orient yourself with the airport on your right, then identify the assigned runway and refine your flight path for the proper base leg.

The key is not to think, “I need to be on the right side of the airport.”

Think:

Right traffic → airport on my right.
Left traffic → airport on my left.

It’s a simple tip that can prevent a surprisingly common—and costly—mistake.

Fly safe, friends ✈️

08/18/2026

One missed NOTAM last week ended in disaster

Investigators say the pilot of a Cirrus Vision Jet SF50 taxied onto a closed section of the runway at Driggs-Reed Memorial Airport (KDIJ) in Idaho and began his takeoff roll.

Likely unbeknownst to the pilot, a NOTAM issued weeks earlier had closed approximately half of the 7,300-foot runway because of construction equipment on the surface. During the takeoff roll, the jet struck a piece of construction equipment and departed the runway. One passenger was seriously injured.

Takeaway: The NTSB and FAA have long emphasized the importance of reviewing NOTAMs as part of preflight planning. Unfortunately, NOTAMs have also been criticized for being difficult to decipher, which can make critical information easy to overlook.

Recently, ForeFlight began presenting NOTAMs in plain English rather than the often-confusing format traditionally published by the FAA. It is now easy to read NOTAMs!

A quick check of ForeFlight may have made this pilot think twice before departing.

Fly safe, friends ✈️

08/12/2026

What Could Happen if You Take Command of a New Make and Model Without Proper Training

While returning to KIAH in Houston, Texas last week, a Cirrus SR20 G7+ equipped with Safe Return™ Emergency Autoland experienced an inadvertent activation of the Safe Return system by a passenger.

Cirrus provides a 10-second activation period during which the PIC can cancel Safe Return by pressing and holding the autopilot disconnect button for one second. If it is not canceled, the Emergency Autoland sequence activates. Among other actions, the system will squawk 7700, transmit emergency communications, take control of the aircraft, divert to a suitable airport, land, stop, and shut down the engine—all without pilot input.

In this case, the 10 seconds elapsed and Safe Return activated. The system squawked 7700, transmitted an emergency message, assumed control, and began maneuvering the Cirrus for a landing at KIAH.

The PIC attempted to contact the tower controller but was initially unable to reach him. Meanwhile, the pilot of a nearby aircraft advised ATC that he was concerned about the Cirrus maneuvering toward his position. Eventually, communication was established on 121.5, and the inadvertent activation was explained. The PIC regained control of the Cirrus and landed uneventfully.

Takeaway: This is exactly why proper transition training and systems knowledge matter when taking command of a new make, model, or avionics configuration. Cirrus training materials emphasize being thoroughly familiar with onboard systems—including knowing how to respond to an inadvertent Safe Return activation.

Advanced automation is an extraordinary safety tool, but pilots still need to know what the airplane is going to do, when it is going to do it, and how to stop it when necessary. Additionally, passengers must be briefed on its proper use.

Know your airplane. Know your systems. Practice the unexpected.

Fly safe, friends. ✈️

08/09/2026

Not knowing the aircraft’s Va may have killed this pilot last week

A Piper PA-24-250 Comanche departed Peoria-Greater Peoria Airport (KPIA) last week and encountered severe convective weather conditions while on a day VFR cross country flight. The PIC was operating at 12500 feet in an area experiencing moderate to extreme precipitation, with a Convective SIGMET for thunderstorms in effect.

The Comanche likely encountered moderate to severe turbulence and initiated a climb to 18000 feet in an apparent attempt to out climb it. ADS-B data shows it begin a 180-degree turn and appears to accelerate well above the recommended maneuvering speed (Va) of approximately 129 MPH as calculated by applying modern formulas. It should be noted that the original POH did not publish a Va as was customary back in the day. It basically instructed the PIC to remain below Vne which is contrary to modern day maneuvering speed basics.

Several minutes later, the Piper probably encountered extreme precipitation and turbulence (while likely flying well above Va) and began breaking up (structural failure). The pilot was fatally injured.

Takeaway: Request vectors from ATC to avoid extreme precipitation (thunderstorms) by at least 20 nautical miles. Additionally, reduce power and maintain level flight (shiny side up-dirty side down) when entering areas of moderate or greater precipitation and slow to Va to mitigate the risk of loss of control and structural damage.

Fly safe, friends. ✈️

08/05/2026

This flight instructor’s skill and good aeronautical decision-making just saved several lives this week

Minutes after departing Pensacola Airport (PNS), the instructor radioed ATC: “We may have an engine problem. We’ll keep it high for now, but we have a burning oil smell in the cockpit.” Seconds later, she transmitted: “We would like to go ahead and declare an emergency. I think we are losing our engine.” The controller immediately acknowledged the emergency and advised that help was being sent.

Shortly afterward, the instructor transmitted: “We are completely props up and will probably go down on I-10,” referring to a seized propeller caused by catastrophic engine failure.

As the Piper Cherokee glided toward the interstate, it became clear she would have to thread the airplane over a large truck and under an overhead sign gantry. Dashboard camera footage from the truck shows the Piper doing exactly that with remarkable precision—barely clearing the truck below and the sign structure above. The aircraft touched down safely on the highway and came to a stop. Amazingly, no injuries were reported.

Takeaway: In an engine-out emergency, altitude is life insurance. Stay high if you can, immediately select the best available landing area, fly to it, establish best glide speed, and keep your focus on the landing. Fly the airplane all the way to the ground.

None of us truly knows how we’ll react the day the propeller stops turning. For some, training takes over—and that’s exactly what happened here. This flight instructor remained calm, made excellent decisions, and executed an extraordinary forced landing under intense pressure.

Our hats are off to her!

Fly safe, friends ✈️

08/03/2026

Was the float plane crash last weekend a case of “get-there-itis”?

Local news stations are playing a passenger video showing that the required SIC of a chartered Cessna Caravan on floats may have been coming forward from the cabin as the takeoff started on a flight from the Bahamas to the US. Shortly after that the PIC aborted the takeoff and crashed into a sea wall. Apparently he was attempting to avoid a pleasure boat in his path. All ten passengers and crew evacuated unharmed. This may be a reminder that there is no reason to begin a takeoff until passengers and crew are seated with seat belts fastened.

The FAA Airplane Flying Handbook says takeoff is not the time to be getting settled, buckling in, or moving to your seat. Taxi and takeoff are considered critical phases of flight and the busiest and least forgiving parts of the flight. If something goes wrong, you need every required crewmember ready to respond immediately.

This is exactly why we have SOPs. They aren’t there to slow us down—they’re there because somebody learned the hard way what happens when we skip the basics.

If this video is ultimately confirmed by the investigation, It’s possible the hazardous attitude involved is probably Invulnerability: “It won’t happen to me.” Maybe after hundreds of uneventful departures, it’s easy to convince yourself that starting a few seconds early isn’t a big deal.

Takeaway: Don’t move the airplane for taxi or takeoff until everyone who needs to be in their seat is in their seat, belted in, and ready. Those extra 10 or 15 seconds are insignificant compared to the consequences of getting it wrong. Get-there-itis describes the tendency to continue a flight or press on toward a destination despite increasing risks because of a strong desire to “get there.”

The investigators will determine exactly what happened, but we can use this as a reminder to never rush a departure.

Fly safe, friends ✈️

07/30/2026

No one enjoys practicing power-on stalls—but this week’s fatal accident is a reminder of why we must.

This accident sequence shows a Piper Cherokee entering a power-on stall shortly after takeoff from Chandler Airport in Arizona. The aircraft appears to pitch up excessively during the departure climb, exceed the critical angle of attack, stall, and enter a spin. Witnesses say there was no apparent attempt at recovery. The hot temperatures likely contributed to high-density altitude conditions, reducing aircraft performance. The pilot was fatally injured.

Takeaway: The FAA Airplane Flying Handbook emphasizes recognizing the earliest signs of an impending stall during departure—including an increasing angle of attack, airframe buffeting, and stall warnings—and immediately lowering the nose to reduce the angle of attack. It also stresses the importance of keeping the ball centered to prevent an inadvertent spin.

The handbook is clear: recovery should begin at the first indication of a stall—not after the stall is fully developed.

Regular training and proficiency in recognizing, preventing, and recovering from power-on stalls can make the difference when seconds count.

Fly safe, friends ✈️

07/18/2026

Can ATC punish you for disregarding their instructions?

Last week, the crew of an Airbus A340 departing John F. Kennedy International Airport (JFK) was instructed to fly a heading of 350°—a course that would have taken them toward an area of extreme precipitation and severe thunderstorms.

The captain acknowledged the instruction but responded:

“We need further left, maybe a heading of 240. Everything is red in front of us.”

He was referring to the intense convective weather displayed on the aircraft’s weather radar.

The controller replied:

“Sir, why do you need that heading? Everyone is going that way. What is the problem?”

Seconds later, the captain turned the Airbus away from the weather without waiting for further clearance.

The controller responded:

“Sir, this could be a possible pilot deviation. You turned your airplane without telling me. There is an aircraft right in front of you.”

The flight continued without further incident.

Takeaway: FAR 91.3 states that “the pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of the aircraft.”

In other words, if you believe complying with an ATC instruction would compromise the safety of the flight, you have both the authority—and the responsibility—to take whatever action is necessary to ensure the safety of your aircraft.

That authority isn’t unlimited, however. The pilot should advise ATC of the deviation as soon as practicable, and ATC will then work to maintain separation between aircraft.

Weather avoidance is one of the best examples of where the PIC’s judgment takes precedence.

Fly safe, friends ✈️

07/15/2026

Relying on ‘NEXRAD’ to avoid thunderstorms likely killed this pilot and his son last week

A Beechcraft Baron 55 departed St. Louis Regional Airport (KALN) last week and encountered severe convective weather conditions while on a night VFR cross country flight. Onboard was a father (the PIC) and his young son returning home from a baseball game. They were operating in an area experiencing moderate to extreme precipitation, with a Convective SIGMET for thunderstorms in effect.

The pilot’s daughter later stated to investigators that the Baron was equipped with “weather-tracking equipment that was 30 minutes behind real weather”, likely NEXRAD. The PIC’s mistake might have been to assume that NEXRAD was equivalent to onboard radar and could be used to avoid the worst weather. It’s important to understand that NEXRAD is not radar; it displays precipitation patterns that may be up to 20 minutes old—not real-time data.

Several minutes later, the Baron encountered extreme precipitation and turbulence (while flying well above Va) that caused the aircraft to rapidly gain and lose over 5000 feet of altitude. The propeller RPM likely surged past redline and the Baron began breaking up because the PIC may have failed to reduce power and airspeed below maneuvering speed (Va) during the turbulence and uncontrolled descent. The two souls onboard were fatally injured.

Takeaway: NEXRAD is a valuable tool for situational awareness, especially in identifying large areas of extreme precipitation. However, it should not be relied upon to navigate through gaps in convective weather. Request vectors from ATC to avoid extreme precipitation (thunderstorms) by at least 20 nautical miles, and do not depend solely on NEXRAD. Additionally, reduce power when entering areas of moderate or greater precipitation and slow to Va to mitigate the risk of loss of control and structural damage.

Fly safe, friends. ✈️

Gold Standard Aviation

08/26/2026

08/22/2026

08/18/2026

08/12/2026

08/09/2026

08/05/2026

08/03/2026

07/30/2026

07/18/2026

07/15/2026

Address

Telephone

Website

Alerts

Contact The School

Shortcuts

Share

Category

Listing takedown request