X

Risk Management Magazine

Search for Articles

Don't Assume

Don't Assume

[EasyDNNnews:Title]


CHIEF WARRANT OFFICER 4 KEVIN RIESE

Looking up the word assume in the dictionary, I found the definition to be “to take for granted.” In the aviation business, there is never a time we should take something for granted. The story I am about to tell could have potentially ended in significant damage to an airframe, or worse, as injury or death of a fellow aviator.

The mission was to continue training a new instructor pilot. The weather was perfect, and we were sharing the traffic pattern with another aircraft doing readiness level progression, both doing emergency procedure and touch-and-go training. Things were working well. Sequencing and timing was coordinated via internal frequency so each aircraft could complete the required maneuvers and not be rushed by the other aircraft.

After one particular landing, I decided to exit the runway and taxi back to talk over the previous maneuver and give the new instructor pilot trainee a break. So we taxied back to the runway hold-short line, set the brakes and talked about the maneuvers. As we watched the other airplane do a pattern, we waited to sequence back into the flow of the traffic pattern. We saw the other aircraft turn base, then final, and we both commented that their landing gear was not down. Knowing the instructor pilot in the other aircraft was an outstanding aviator and incredible instructor, I assumed he was aware of the situation.

I believed the instructor was using this event as a training point, and we both continued to watch the approach. As they were on final to the runway, I commented they are getting a little too low for comfort and should be receiving a gear warning in the cockpit, but I did not want to get into the other pilot’s training.

As they approached the threshold, I’d had enough and wanted to ensure they were aware of the situation. I transmitted over the radio to check gear and go-around. As I was keying the mike talking, the airplane began the go-around and all seemed well. I was curious if they were aware of the gear not being down prior to my call, or if I indeed helped them advert disaster.

After completing the training flight and debrief, I questioned the other crew as to what was happening during the situation. As expected, the pilot in progression was behind the aircraft and unaware due to task overload. The instructor pilot assured me he was aware of the situation and wanted to use the event as a training point. The one thing he conveyed to me was that due to an inoperative navigation component, they did not receive GPWS warning of, “Too low, gear.”

So what if I did not say anything and the other crew had an accident while I watched. It’s such a simple thing to do; it’s our obligation as leaders and officers. Assuming because the other instructor pilot was good and had it under control, or aircraft systems would alert him of the problem is wrong. I hesitated saying anything because I was confident in the other IP’s ability. That could have been disastrous.

How many accidents could we avoid if someone said something when others deviated from the standard? I may be stating the obvious, but the importance cannot be overstated. Let’s not assume anything. Always speak up if you see something wrong or not to standard.

  • 12 March 2017
  • Author: Army Safety
  • Number of views: 987
  • Comments: 0
Print