37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1414512 |
Time | |
Date | 201701 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LGA.Airport |
State Reference | NY |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Flight Phase | Taxi |
Route In Use | SID LGA 5 |
Person 1 | |
Function | First Officer |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Arrived at cockpit to start preflighting. Was in an aircraft equipped with controller pilot data link communication (cpdlc). Logged in; and requested clearance. Clearance came and it was depart runway 13 lga 5 coney climb / climb via SID / expect rv to white. I went to the departure/arrival page and selected lga 5. It did not show any transitions; and it did not offer runway 13 as one of the available runways associated with this SID. I showed this to the captain (ca) and we tried to figure out how to input this into the FMC. The ca was of the impression that we when we contacted ground control for taxi; and give them our assigned SID; that they would then clarify the departure for us. I was okay with that; so we continued to prepare the aircraft for departure.after we pushed off the gate and were ready for taxi; I contacted ground control for taxi instructions. The controller was very busy and told us to hold position; that we were #10 or so for departure; and that he would get back to us. About 10-15 minutes later the controller gave us taxi instructions to runway 13. There was no mention of SID departure instructions. We taxied out to runway 13 and was holding short of the runway. Tower then cleared us for takeoff; again with no mention of any heading or SID instructions. As we taxied into position we briefly discussed our departure; both agreeing that in the absence of any new instructions from ATC; we were supposed to fly runway heading and expect vectors to white. So we did just that.about a minute after takeoff; ATC inquired if we were turning to a 180* heading? We replied 'negative; we are on runway heading.' ATC then asked what climb we had been given and we replied that we had been given the LGA5 dep; no climb. ATC then vectored us around until we were on course to white. No further comments were made by ATC regarding the departure; and we were handed off to the center controller. After climbing thru 10;000' we tried to figure out what had happened. We pulled up the cpdlc clearance again; and it was at this time that we noticed the coney climb part of the clearance. We had just missed it while trying to figure out how to link up runway 13 to the lga 5 SID in the FMC. The rest of the flight was completed without incident.[suggestions]1. Figure out some way to print out the cpdlc clearance so that it could be visibly referred to during all phases prior to takeoff.2. Figure out why the lga 5 SID does not offer runway 13 as an available runway for takeoff.3. Delay taxi and/or takeoff until clarification is received from ATC on any part of the clearance that is in question.
Original NASA ASRS Text
Title: B737 First Officer reported a track deviation resulted when the flight crew missed part of a Controller Pilot Data Link Communication (CPDLC) clearance.
Narrative: Arrived at cockpit to start preflighting. Was in an aircraft equipped with Controller Pilot Data Link Communication (CPDLC). Logged in; and requested clearance. Clearance came and it was Depart Runway 13 LGA 5 Coney Climb / Climb Via SID / Expect RV to WHITE. I went to the DEP/ARR page and selected LGA 5. It did not show any Transitions; and it did not offer Runway 13 as one of the available runways associated with this SID. I showed this to the Captain (CA) and we tried to figure out how to input this into the FMC. The CA was of the impression that we when we contacted Ground Control for taxi; and give them our assigned SID; that they would then clarify the departure for us. I was okay with that; so we continued to prepare the aircraft for departure.After we pushed off the gate and were ready for taxi; I contacted Ground Control for taxi instructions. The controller was very busy and told us to hold position; that we were #10 or so for departure; and that he would get back to us. About 10-15 minutes later the controller gave us taxi instructions to Runway 13. There was no mention of SID departure instructions. We taxied out to Runway 13 and was holding short of the runway. Tower then cleared us for takeoff; again with no mention of any heading or SID instructions. As we taxied into position we briefly discussed our departure; both agreeing that in the absence of any new instructions from ATC; we were supposed to fly runway heading and expect vectors to WHITE. So we did just that.About a minute after takeoff; ATC inquired if we were turning to a 180* heading? We replied 'negative; we are on runway heading.' ATC then asked what climb we had been given and we replied that we had been given the LGA5 Dep; no climb. ATC then vectored us around until we were on course to WHITE. No further comments were made by ATC regarding the departure; and we were handed off to the Center controller. After climbing thru 10;000' we tried to figure out what had happened. We pulled up the CPDLC clearance again; and it was at this time that we noticed the Coney Climb part of the Clearance. We had just missed it while trying to figure out how to link up Runway 13 to the LGA 5 SID in the FMC. The rest of the flight was completed without incident.[Suggestions]1. Figure out some way to print out the CPDLC Clearance so that it could be VISIBLY referred to during all phases prior to Takeoff.2. Figure out why the LGA 5 SID does not offer Runway 13 as an available Runway for Takeoff.3. Delay taxi and/or takeoff until clarification is received from ATC on ANY part of the clearance that is in question.
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.