ASRS CALLBACK includes excerpts from ASRS incident reports with supporting commentary. In addition, CALLBACK may contain summaries of ASRS research studies and related aviation safety information. CALLBACK is one of the ASRS's most effective tools for improving the quality of human performance in the National Aviation System (NAS) at the grass roots level.

Wednesday, March 16, 2016

CALLBACK 434 - March 2016


CALLBACK From the NASA Aviation Safety Reporting System
Issue 434
March 2016
Managing Muscle Memory
Muscle memory is an interesting physiological phenomenon involving our muscles and their interaction with the brain. The more often we perform a given physical action, the more likely we are to do it as needed, when needed, without having to think about the specific combination of movements involved. These habits thus become an unconscious process that occurs when triggered by a given circumstance or set of cues.

Practicing a procedure until the process is automatic develops muscle memory that can be crucial when an immediate action emergency (such as an engine failure at V1) occurs. However, as in the incident reports below, muscle memory can be a problem when the cues are right, but the circumstances are wrong. That is when the brain has to be "conscious" enough to stop the automatic response of well-trained muscles.

The following ASRS reports recount a sequence of ground incidents in which muscle memory took over at the wrong time.
Taxi Out, Tow Back
Faced with a distraction and a familiar set of circumstances, a B737 Captain let muscle memory take over just long enough to create an embarrassing situation.
Inoperative APU; second flight of the day; started the number one engine at the gate…; asked for taxi to a remote area for cross-bleed start of the number two engine. Stopping at the designated location, the aircraft began to shimmy slightly under braking. I stopped braking then applied brakes again. The shimmy did not happen again so I set the parking brake. I then grabbed the number one engine start lever and began to shut the number one engine down. Realizing what I was doing, I quickly returned it to the previous position, but the engine had already shut down. We were now on battery power. I told the Flight Attendants to remain seated, then told ATC we would need a tow back to the gate and we had one radio and would need to go off frequency to coordinate with Company Operations. We turned IRS 1 and 2 off and tried to explain to the passengers what had happened. We were back at the gate in approximately 10 minutes. We started the engine and did the procedure properly the second time. The remainder of the flight was uneventful.

I guess I would say it was muscle memory, the same motion as arriving at a gate, number two engine shut down, parking brake set. I should be more deliberate in all of my actions, but it happened so fast that the First Officer did not even have time to react. The brake shimmy was a distraction, but that does not excuse me from my action.
A Bad Match Up
This B737 Captain’s method of checking the start lever position was problem enough, but then muscle memory kicked in and made the situation worse.
It was my leg. Preflight activities had been normal and we were not rushed at all.… We had been instructed to hold short of [the runway] and were almost stopped. I had already called for the Before Takeoff Checklist and the First Officer challenged me with “Start Levers” at the next to last step in that checklist. I reached down to confirm “Idle.” My practice has been to hold the start levers with my thumb and forefinger, confirm the idle detent position with a slight nudge forward and a slight nudge rearward, then to respond, “Idle.” However this time with the slight nudge to the rear, the number one start lever felt like it was not quite fully down in the idle detent. It came up over the edge and I unintentionally shut down the number one engine. I was surprised and stunned.

I announced the situation to the First Officer and set the parking brake. Then instinctively I reached down again to confirm the start lever positions. At that point muscle memory kicked in and I must have “matched” the start lever heights. To my horror, when I nudged the levers rearward again, I unintentionally shut down the number two engine as well. I started the APU and put electrical power back on the aircraft. We told ATC that we had a problem and that it would be a few minutes before we could move. Feeling completely inept and embarrassed, I told the First Officer that we would start over and re-accomplish everything beginning with the Before Start Checklist. The First Officer agreed.

I made a short and embarrassing announcement to the Passengers and apologized for the delay while we dealt with a cockpit issue. We then flew an otherwise uneventful flight. Several suggestions come to mind in order to prevent this from happening again. Primarily, I have changed the way that I check the start levers in the idle detent. No longer will I hold them with my thumb and forefinger. And no longer will I nudge them rearward, but only forward and down.
Houston, We Have “an Issue”
A B737-800 Captain’s prescription for inhibiting muscle memory involves slowing down and thinking before a particular situation triggers your internal automation and results in a dose of humility.
We were told to line up and wait. I brought the aircraft to a stop and, for some strange reason, I reached over and shut down both engines instead of setting the parking brake. We told Tower that we had an “issue” and would be in place for a minute or two and then we would have to taxi clear. We started the right engine and taxied clear of the runway so we could redo checklists and regroup. When the Tower later asked what our issue was, I think we told them that we had to look at a light. Actually, lots of lights.

With the start levers being right next to the parking brake, I guess that once my hand was on the start levers, positioned right next to the parking brake, muscle memory took over and moved them to off. I need to slow down and think about what I am doing before moving any switch or lever. This was definitely the healthiest dose of humility ever in my many years of flying.
The Best Laid Plans…
Even when the need for a non-standard sequence of events is recognized and planned for in advance, strong muscle memory concerning the standard sequence can prevail. This CRJ200 First Officer confirms that slowing down is the best way to engage the brain and disengage muscle memory.
When we received the aircraft, the previous crew had written up the #2 AC Generator. Maintenance came and deferred the generator. Per the MEL operations instructions, we were to keep the APU running for the entire flight. The Captain and I discussed this as part of our pre-departure briefing. When Tower cleared us to line up and wait, I ran the Takeoff Checklist and turned off the APU out of habit. I realized my mistake and informed the Captain. We notified the Tower that we would need to exit the runway and get back in line to restart the APU.

This incident illustrates why it is important to slow down when completing checklists and flows during abnormal operations to ensure they are completed properly. I shutdown the APU due to “muscle memory” during the Takeoff Checklist even though we had discussed the MEL procedures for the deferred AC Generator during the pre-departure briefing.
Rolling in the Snow
A CRJ900 Captain, faced with an oncoming snow plow, went for the brakes and engine reverse, but muscle memory had other ideas.
After landing, we were taxiing to our gate. The taxiways were snow covered with fair braking action. We had shut down our right engine and left the APU shut down. A snow plow was on our right and just ahead of us. I was watching him when he abruptly started to turn left into us. I applied the brakes, with minimal effectiveness, and I was going to apply reverse thrust, but muscle memory kicked in and I mistakenly shut down the left engine. We lost all power and rolled to a stop. The plow never completed his turn, but saw us and turned away. We informed ATC and started the APU to restart an engine. Within two minutes the engine was running again and we taxied to the gate without incident.
Armed and Dangerous
An A320 First Officer got a first-hand lesson in how a busy, rushed environment can cause muscle memory to override a more methodical thought process.
This incident started about 5-10 minutes after the last passenger deplaned. Doors 1L and 2L were both open. There were many cleaners on the aircraft from the front to the back. The situation was busy at best, frantic at worst. I was standing on the front air stairs when a Flight Attendant asked me if I could supervise the opening of Door 2R. The cleaners were beating on the door to have it opened so that the trash could be emptied. I agreed to supervise since no other crewmembers were available. I followed the Flight Attendant to the back of the airplane where various ramp personnel were in the aft galley conducting their work. The Flight Attendant proceeded to arm the door as it had been disarmed from deplaning. It was at this point that I became confused. Before I could intervene, the Flight Attendant pulled up on the handle. The door opened and the slide blew. Luckily, no one was injured.

I should have done a better job confirming what was actually going on and tried to slow the process down.… The overall issue for me was being distracted, rushed and uncertain of my supervision objective. I also believe the Flight Attendant was trying to do the right thing, especially as a new employee. She was rushed and getting pressure from the cleaners. In retrospect, I think she was operating on muscle memory. Since she had already disarmed the door, the next event was to arm it.
ASRS Database Online
The ASRS Database is a rich source of information for policy development, research, training, and more.
 Search ASRS Database »
CALLBACK Issue 434
 Download PDF & Print
 View HTML
ASRS Online Resources
 CALLBACK Previous Issues
 Report to ASRS
 View ASRS Report Sets
 ASRS Homepage
Subscribe to CALLBACK for FREE!
Contact the Editor
Special Studies
Meteorlogical and Aeronautical Information Services Data Link and Application Study
ASRS, in cooperation with the FAA, is gathering reports of incidents that occurred while pilots were utilizing weather or AIS information in the cockpit obtained via data link on the ground or in the air. Learn more » Read the Interim Report »
Wake Vortex Encounter Study
In cooperation with the FAA, ASRS is conducting an ongoing study on wake vortex incidents, enroute and terminal, that occurred within the United States. Learn more »
January 2016
Report Intake:
Air Carrier/Air Taxi Pilots 4,214
General Aviation Pilots 867
Flight Attendants 512
Controllers 356
Military/Other 317
Dispatchers 172
Mechanics 156
TOTAL 6,594
2015
ASRS Alerts Issued:
Subject of Alert No. of Alerts
Airport Facility or Procedure 54
Aircraft or Aircraft Equipment 53
ATC Equipment or Procedure 33
Hazard to Flight 6
Other 3
Company Policy 2
Maintenance Procedure 1
TOTAL 152
Subscribe to CALLBACK for FREE!
Contact the Editor
NOTE TO READERS:     Indicates an ASRS report narrative    [   ]  Indicates clarification made by ASRS
A Monthly Safety Newsletter from The Office of the NASA Aviation Safety Reporting System
Issue 434



NASA Aviation Safety Reporting System | P.O. Box 189 | Moffett Field | CA | 94035-0189

CALLBACK 433 - February 2016


CALLBACK From the NASA Aviation Safety Reporting System
Issue 433
February 2016
What Would You Have Done?
The “What would you have done?” issues of CALLBACK offer the reader a chance to “interact” with the information given in a selection of ASRS reports. In “The First Half of the Story” you will find report excerpts describing the event up to the decision point. You may then use your own judgment to determine the possible courses of action and make a decision regarding the best way to resolve the situation.

The selected ASRS reports may not give all the information you want and you may not be experienced in the type of aircraft involved, but each incident should give you a chance to exercise your aviation decision-making skills. In “The Rest of the Story…” you will find the actions actually taken by reporters in response to each situation. Bear in mind that their decisions may not necessarily represent the best course of action. Our intent is to stimulate thought, discussion and training related to the type of incidents that were reported.
The First Half of the Story
Situation # 1  C172 Pilot’s Report
After exiting Class B, I requested a descent to maintain VMC as the cloud deck was getting denser. ATC approved a VFR descent. As I began my descent, I noticed that the broken layer was quickly closing. To avoid IMC, I climbed back to 5,000 feet. I informed ATC that I was on a VFR flight plan and was not instrument rated. I flew for another five minutes and then saw that what had been a broken layer had totally closed up.
I climbed without incident to 6,000 feet where I was in and out of the cloud tops. About fifteen minutes into the flight, I noticed that the ammeter was discharging. I could not reestablish operation of the alternator. I contacted Center. I was given vectors to [an airport], cleared to descend to 2,100 feet, and cleared for a GPS approach. While making the procedure turn inbound, I began to experience icing, abandoned the approach, and climbed back to 6,000 feet. I requested to fly to [my original destination] where, hopefully, I would be able to do an ILS or surveillance approach. I informed Center that I would shut off all my electrical equipment to maintain as much battery power as possible. I continued to fly in the general direction of [my destination].... I turned the radio on and found that I had experienced a complete electrical failure.
During the approach we had visual contact with the airport. At about four miles the runway was in sight. There was no turbulence or rain. Tower advised that there was a microburst on Runway 27. About one mile out, we encountered moderate rain for about 15 seconds. I thought the previous aircraft had landed, so I continued as no turbulence or windshear conditions were being experienced.... I elected to leave flaps at 15 degrees in case a go around was conducted (normal landing is 30 degrees flaps). Just as I flared for landing, we began to experience a strong crosswind from the right.
I turned off the autopilot/throttles as we intercepted LOC/glideslope and hand flew the aircraft. I called, “Gear down, Flaps 15.” Under 170 knots, on glideslope and LOC, I called for Flaps 25. At approximately 1,500 feet and 163 knots I called, “Flaps 30, Landing checklist,” but at the same time we experienced a gust and the First Officer hesitated due to our proximity to flap limit speed. He verbalized this and I acknowledged that I was slowing the aircraft. At this time there was a bright lightning strike just north of the field and several other flashes on both sides of the aircraft. There was also a radio transmission that interrupted us.

We had 12 knots of tailwind from 1,500 feet down to 800 feet and I was completely “outside” flying the aircraft, thinking windshear was possible and mentally prepping to execute a windshear recovery maneuver. I was focused on flying and landing on Runway 28. We started with light rain and as we approached the runway, rain increased to moderate, but the runway was in sight throughout. At approximately 400 feet AGL we got the caution, “Too low flaps,” which startled us and I immediately looked at the flap indicator (at 25), then the gear (Down, three Green), and brakes (Armed, Green light).
The Rest of the Story

The Reporter's Action
I circled back to find VFR conditions and discovered that the broken layer behind me had also closed up. I talked with ATC to get an update for field conditions at any airport close to my route of flight. I was advised that my best bet would be [a nearby airport]... and...I received vectors toward the airport. I was in solid IMC conditions and under ATC control. Less than a mile from [the airport], while still in IMC conditions, Approach informed me that the airport was now reporting an 800-foot overcast. I...asked if there was a better alternative and then flew under ATC control...to [another airport]....

I informed ATC that I had some IFR training. I did not have my approach plates in my flight bag. Approach gave me a frequency to talk with the Controller who tracked my approach and descent. I broke out at approximately 1,400 feet and safely landed in significant crosswinds.

The weather was significantly worse than reported... and conditions worsened rapidly.

The Reporter's Action
I contacted Flight Service on my cell phone and then was given a number to contact Approach Control. The Controller informed me that I was 20 miles east of [an alternate airport] and suggested...that he could permit me to descend to 1,800 feet MSL. [The airport] was reporting a 1,800 foot overcast at that time. He gave me a vector to [the airport] and cleared me to descend to 1,800 feet. I broke out into the clear and, with the vector assistance, was able to land without incident.

The Reporter's Action
The aircraft wanted to drift left during rollout. As we slowed, control was regained and we taxied off the runway to the ramp. Later, another company pilot (who was waiting for takeoff) told me that the preceding and following aircraft had gone around. As mentioned, I believed the preceding aircraft had landed. In hindsight, I should have gone around and waited for better weather conditions.... This incident (although turning out OK) could have been serious.... The safer course would have been to go around. I will not hesitate performing a go-around next time.
ASRS Database Online
The ASRS Database is a rich source of information for policy development, research, training, and more.
 Search ASRS Database »
CALLBACK Issue 433
 Download PDF & Print
 View HTML
ASRS Online Resources
 CALLBACK Previous Issues
 Report to ASRS
 View ASRS Report Sets
 ASRS Homepage
Subscribe to CALLBACK for FREE!
Contact the Editor
Special Studies
Meteorlogical and Aeronautical Information Services Data Link and Application Study
ASRS, in cooperation with the FAA, is gathering reports of incidents that occurred while pilots were utilizing weather or AIS information in the cockpit obtained via data link on the ground or in the air. Learn more » Read the Interim Report »
Wake Vortex Encounter Study
In cooperation with the FAA, ASRS is conducting an ongoing study on wake vortex incidents, enroute and terminal, that occurred within the United States. Learn more »
December 2015
Report Intake:
Air Carrier/Air Taxi Pilots 5,013
General Aviation Pilots 1,032
Flight Attendants 549
Controllers 450
Military/Other 391
Dispatchers 188
Mechanics 176
TOTAL 7,799
ASRS Alerts Issued:
Subject No. of Alerts
Aircraft or Aircraft Equipment 19
Airport Facility or Procedure 9
ATC Equipment or Procedure 7
Hazard to Flight 3
Other 1
TOTAL 39
Subscribe to CALLBACK for FREE!
Contact the Editor
NOTE TO READERS or  Indicates an ASRS report narrative    [   ]  Indicates clarification made by ASRS
A Monthly Safety Newsletter from The Office of the NASA Aviation Safety Reporting System
Issue 433



NASA Aviation Safety Reporting System | P.O. Box 189 | Moffett Field | CA | 94035-0189

Blog Archive