Metrics Test
CRMDEEN_at_aol.com
Tue, 17 Dec 1996 14:29:32 -0500
Hello CRMers,
Yesterday I was conducting a MOST (military for LOFT) mission and the
conversations of metrics was on my mind. There was an interesting process in
the mission, and it occured to me that if I somehow relayed into this forum,
we could all give an opinion on the event, and that perhaps this would give
us all a common event to relate the metrics discussion to.
The crew consists of a PIC, a co-pilot, a Flight Engineer, and a
Navigator. In our crews, the engineer and navigator are not pilot-qualified,
and the engineer is an enlisted rank. The mission this crew was given was a
short-notice alert to provide airlift of 75 med-evac passengers from a
"near-combat", remote, small (4200ft) airfield. The political tensions
within the host country have motivated the American forces to quickly
withdraw civilians, wounded, and other non-combatants from the "near-combat"
environment.
The crew is on approach to the runway, and they have executed an
approach which is designed to avoid enemy threats. One mile from the runway,
a warning light illuminates, warning of a low fluid level in the propeller
governing system. (The flight manual clearly states the propeller must be
feathered prior to landing) The flight engineer notices the warning light,
and calmly advises the pilot that the light is on. On this first attempt,
the pilot is high and hot on the final approach, and it is for that condition
that he goes around, into a VFR pattern, right turns.
After the low approach, the pilot queries the engineer to repeat the
warning. The engineer tells him the #4 prop light is on, and the propeller
seems to be operating normally.The pilot thinks silently, while turning to
the downwind. The co-pilot and navigator are in the windows and verbally
advising the pilot about the runway location. The engineer asks the pilot if
he is going to shutdown the affected engine. The pilot responds "this is a
combat situation". No more is discussed while the pilot completes his
pattern. The second attempt to the runway is again high and hot; the pilot
goes around. During the low approach the runway controllers suggest the
pilot execute a tear-drop approach and try the other direction over the
flatter terrain. The engineer now reports the propeller is having difficulty
maintaining proper speed, and tells the co-pilot to de-select the electronic
speed governing system. The propeller speed stabilizes. The navigator and
co-pilot advise the pilot they will direct him to fliy a larger pattern, and
give him a longer final. As the pilot turns onto final approach, he asks the
engineer if they have sufficient "three-engine capability" for the take-off.
The engineer calmly says "well, not really, sort of close, yea--maybe. We
really shouldn't do it, it's your decision." The pilot then mumbles "I hate
it when it's my decision." The engineer, after a pause, says "are you asking
for a suggestion?" The pilot then says "yes, what do you suggest?" The
engineer says" the propeller is getting worse, we don't need to get stuck
here, I suggest they find another airplane to do this." The aircraft is
one-half mile on final, and the pilot has a very good final approach this
time. The pilot mumbles "gee, I'm not sure what to do." The navigator,
noticing the aircraft is less that one-quarter mile from threshold, 75 feet
above the ground, says "we'll know your decision shortly." A moment later,
the pilot adds power and announces "crew, we're on the go."
The crew aborted the assigned mission and diverted to repair facility.
So, CRMers of the metrics discussion; how would you apply your metrics
theory to this training event?
Greg Deen,
HTI--C130 ATS