37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1386891 |
Time | |
Date | 201609 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | Mixed |
Aircraft 1 | |
Make Model Name | B737-700 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Due to thunderstorms in the area; the pushback was delayed and performed without headsets. During pushback; ground control told us to contact clearance delivery for possible routing change. We completed the pushback/engine start and cleared off the ground crew. We contacted clearance delivery and they informed us of a new controller pilot data link communications (cpdlc) clearance we needed to acknowledge. Due to weather on the departure corridor; we spent approximately five minutes and multiple different clearance changes before we received our final clearance and sorted out the cpdlc confusion. We then performed a waypoint by waypoint review of the clearance to ensure we had all proper points. We were satisfied we had the correct routing and called for taxi. During taxi out we realized we had not performed the before taxi flows or done the before taxi checklist; flaps were not set. I stopped the aircraft; we performed the flows and checklist and confirmed the aircraft was properly configured. The rest of the flight was uneventful.the complexity and confusion of the multiple clearance changes put us out of the normal flow of operation. We just need to be more vigilant to checklist discipline when our normal triggers are interrupted.
Original NASA ASRS Text
Title: B737-700 flight crew reported taxiing without completing the Before Taxi checklist; due in part to distraction and confusion with the CPDLC Pre-Departure Clearance procedure.
Narrative: Due to thunderstorms in the area; the pushback was delayed and performed without headsets. During pushback; Ground Control told us to contact Clearance Delivery for possible routing change. We completed the pushback/engine start and cleared off the Ground Crew. We contacted Clearance Delivery and they informed us of a new Controller Pilot Data Link Communications (CPDLC) clearance we needed to acknowledge. Due to weather on the departure corridor; we spent approximately five minutes and multiple different clearance changes before we received our final clearance and sorted out the CPDLC confusion. We then performed a waypoint by waypoint review of the clearance to ensure we had all proper points. We were satisfied we had the correct routing and called for taxi. During taxi out we realized we had not performed the Before Taxi flows or done the Before Taxi Checklist; flaps were not set. I stopped the aircraft; we performed the flows and checklist and confirmed the aircraft was properly configured. The rest of the flight was uneventful.The complexity and confusion of the multiple clearance changes put us out of the normal flow of operation. We just need to be more vigilant to checklist discipline when our normal triggers are interrupted.
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.