37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1700016 |
Time | |
Date | 201911 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 136 |
Events | |
Anomaly | Deviation - Procedural Other / Unknown |
Narrative:
Reverse all nighter; early morning takeoff on runway xx ZZZ. As we were advancing takeoff power; the first officer calls 'lights; clocks; fuel' which I didn't clearly understand. This caused confusion because I didn't completely hear what he said. I thought he was calling out some type of issue in regard to the takeoff; or the aircraft; or a traffic conflict. This is a time when the flight deck should be quiet and not cluttered with random non-SOP call outs. I have previously had another first officer make this random call on the takeoff of which it almost caused a rejected takeoff because of the timing and once again not clearly hearing this random; sporadic non-SOP call out. In each case I questioned the first officer where they are coming up with this random non-SOP call; and each one said that they were taught this in the training center or on initial oe (operating experience). I cannot find any reference to this random; ill-timed call out in the FM (flight manual) normals. I believe it is some old carry over call out. It's very distracting to have the co-pilot calling out random non-SOP calls at the start of the takeoff and I feel it poses a safety threat.I had to query the co-pilot on what he was saying as the auto throttles were advancing power to takeoff thrust. Definitely not an optimal time to be having to ask; 'what did you just say?' as it turns out; we aborted takeoff in ZZZ on runway xx for a pop up predictive wind shear warning; and the confusion that the first officer created with the random non-SOP call; 'lights; clocks; fuel' and the conversation we had to have as we were accelerating to clarify what he had said definitely set the stage for further confusion when we got the pws (predictive wind shear) warning on takeoff. 'Lights; clocks; fuel' is not in the FM normals and is a disruptive non-SOP call that is a threat to aircraft safety at a critical point when the flight deck should be totally quiet and void of any non-SOP call outs. It is being taught as SOP; when in fact it is not SOP and the timing of this random; lowest common denominator type of call out is a threat.
Original NASA ASRS Text
Title: B737 Captain reported non-standard call-outs used by First Officer caused a distraction during takeoff roll.
Narrative: Reverse all nighter; early morning takeoff on Runway XX ZZZ. As we were advancing takeoff power; the First Officer calls 'Lights; Clocks; Fuel' which I didn't clearly understand. This caused confusion because I didn't completely hear what he said. I thought he was calling out some type of issue in regard to the takeoff; or the aircraft; or a traffic conflict. This is a time when the flight deck should be quiet and not cluttered with random non-SOP call outs. I have previously had another First Officer make this random call on the takeoff of which it almost caused a rejected takeoff because of the timing and once again not clearly hearing this random; sporadic non-SOP call out. In each case I questioned the First Officer where they are coming up with this random non-SOP call; and each one said that they were taught this in the training center or on initial OE (Operating Experience). I cannot find any reference to this random; ill-timed call out in the FM (Flight Manual) Normals. I believe it is some old carry over call out. It's very distracting to have the co-pilot calling out random non-SOP calls at the start of the takeoff and I feel it poses a safety threat.I had to query the co-pilot on what he was saying as the auto throttles were advancing power to takeoff thrust. Definitely not an optimal time to be having to ask; 'What did you just say?' As it turns out; we aborted takeoff in ZZZ on Runway XX for a pop up Predictive Wind shear Warning; and the confusion that the First Officer created with the random NON-SOP call; 'Lights; Clocks; Fuel' and the conversation we had to have as we were accelerating to clarify what he had said definitely set the stage for further confusion when we got the PWS (Predictive Wind shear) warning on takeoff. 'Lights; Clocks; Fuel' is not in the FM Normals and is a disruptive NON-SOP call that is a threat to aircraft safety at a critical point when the flight deck should be totally quiet and void of any NON-SOP call outs. It is being taught as SOP; when in fact it is not SOP and the timing of this random; lowest common denominator type of call out is a threat.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.