DON'T ASSUME

By CHIEF WARRANT OFFICER 4 KEVIN J. RIESEFebruary 23, 2011

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

After one landing, I decided to exit the runway to talk over the previous maneuver and give the new IP trainee a break. We taxied back to the runway hold short line, set the brakes and talked about the previous maneuvers. As we watched the other aircraft complete a pattern, we waited to sequence back into the flow of the traffic pattern. As the other aircraft turned on base and then on final, we noticed their landing gear was not down.

I knew the IP in the other aircraft was an experienced aviator and good instructor, so I assumed he was aware of the situation. I believed he was using this event as a training point, so we both continued to watch the approach. As they were on final to the runway, I commented they were getting a little too low for comfort and should be receiving a gear-up warning in the cockpit. I didn't say anything because I didn't 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 called them over the radio to check the landing gear and go around. The aircraft 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 avert disaster.

After completing the training flight and debrief, I questioned the other crew as to what was happening during the situation described above. As expected, the pilot in progression was behind the aircraft and unaware of the problem due to task overload. The IP assured me he was aware of the situation and wanted to use the event as a training point. The one thing he did convey to me was they had an inoperative navigation component. The ground proximity warning system never forewarned the crew of "too low, gear."

The bottom line in this story is this: What if I had not said anything and the other crew had an accident while I watched. I assumed just because the other IP was good, he had the situation under control and the aircraft systems should have alerted him of the problem. Wrong! Don't ever hesitate to say something. This could have been a disastrous accident.

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. It's our obligation as Leaders and officers to remove the break in the chain. Speak up and never assume others are aware if you see something that is wrong or not to standard.